2023年07月11日更新されたAD0-E718トレーニング最新認定問題をゲットAdobe Commerce合格目指せ [Q23-Q42]

2023年07月11日更新されたAD0-E718トレーニング最新認定問題をゲットAdobe Commerce合格目指せ

認定トレーニングAD0-E718試験問題集でテストエンジン

Adobe AD0-E718試験は、Adobe Commerceに関連する特定のトピックをカバーする異なるセクションに分かれています。最初のセクションでは、プラットフォームのアーキテクチャ、データモデル、ビジネスロジックの理解など、Adobe Commerceの基礎がカバーされます。2番目のセクションでは、カスタムモジュール、テーマ、拡張機能の作成など、Adobe Commerceソリューションの設計と開発がカバーされます。3番目のセクションでは、サーバーの設定、データの管理、問題のトラブルシューティングなど、Adobe Commerceソリューションの展開とメンテナンスがカバーされています。

Adobe AD0-E718試験は、Adobe Commerce Architect Masterになりたい個人を対象とした認定です。この試験は、ビジネスがオンラインストアを作成および管理することができるデジタルコマースプラットフォームであるAdobe Commerceの知識とスキルを試験するために設計されています。この認定は、Adobe Commerceソリューションの設計、開発、展開における専門知識を証明したい個人に適しています。

 

質問 # 23
A merchant asks for a new category attribute to allow uploading an additional mobile image against categories. The merchant utilizes the content staging and preview feature in Adobe Commerce and wants to schedule and review changes to this new mobile image field.
A developer creates the attribute via a data patch and adds it to
view/adminhtml/ui_component/category_form.xml. The attribute appears against the category in the main form, but does not appear in the additional form when scheduled updates are made.
To change this attribute when scheduling new category updates, which additional action should the Architect ask the developer to take?

• A. The attribute must have its apply_to field set to "staging" in the data patch file.
• B. The attribute must have<item name=''allow_staging'' xsi:type="boolean''>true<item> set in the
  =category_form.xml file under the attributes config" section.
• C. The attribute must also be added to
  view/adminhtml/ul_component/catalogstaging_category_update_form.xml.

正解：C

解説：
Explanation
This is because, in order to change the attribute when scheduling new category updates, the attribute must be added to the view/adminhtml/ulcomponent/catalogstagingcategoryupdateform.xml file in order to be displayed in the additional form when scheduling updates. This additional form is used to set the values for the category attributes when scheduling updates.

質問 # 24
While reviewing a newly developed pull request that refactors multiple custom payment methods, the Architect notices multiple classes that depend on \Magento\Framework\Encryption\EncryptorInterf ace to decrypt credentials for sensitive data. The code that is commonly repeated is as follows:

In each module, the user_secret config is declared as follows:

The Architect needs to recommend an optimal solution to avoid redundant dependency and duplicate code among the methods. Which solution should the Architect recommend?

• A. Add a plugin after the getvalue method of $sccpeConfig, remove the $encryptor from dependency and use it in the plugin to decrypt the value if the config name is 'user.secret?
• B. Replace all Vendor\PaymentModule\Gateway\Config\Config Classes With virtualTyp- Of Magento\Payxer.t\Gateway\Conflg\Config and Set <user_secret backend_Model="Magento\Config\Model\Config\Backend\Encrypted" /> under ccnfig.xml
• C. Create a common config service class vendor\Payment\Gateway\config\Config under Vendor.Payment and use it as a parent class for all of the Vender \EaymentModule\Gateway\Config\Config Classes and remove $sccpeConfig and $encryptor dependencies

正解：C

解説：
To avoid redundant dependency and duplicate code among the methods, you need to use the following solution:
Create a standard controller route and mapping the internal URLs (such as news/article/view/id/1) to rewrites that are generated on save and then stored in the URL rewrites table. This solution will leverage the built-in URL rewrite functionality of Magento to handle the news requests. You can create a standard controller route that handles the internal URLs and loads the news article by its ID. Then, you can generate URL rewrites for each news article based on its date and URL key and store them in the URL rewrites table. This way, you can avoid using a custom router or a plugin and reduce the code complexity.
Reference:
https://devdocs.magento.com/guides/v2.4/extension-dev-guide/routing.html
https://devdocs.magento.com/guides/v2.4/extension-dev-guide/url-rewrite.html

質問 # 25
A third-party company needs to create an application that will integrate the Adobe Commerce system to get orders data for reporting. The integration needs access to the get /vi/orders endpoint. It will call this endpoint automatically every hour around the clock. The merchant wants the ability to restrict or extend access to resources as well as to revoke the access using Admin Panel.
Which type of authentication available in Adobe Commerce should be used and implemented in a third-party system for this integration?

• A. Use token-based authentication to obtain an Integration Token. Integration will be created and activated in the admin panel using default integration token settings to get access to the token, which will be used as the Bearer Token to authorize.
• B. Use OAuth-based authentication to provide access to system resources. Integration will be registered by the merchant in the panel an OAuth handshake during activation. The third-party system should follow OAuth protocol to authorize.
• C. Use token-based authentication to obtain the Admin Token. The third-party system will utilize the REST endpoint using the admin username and password to get the Admin Token, which will be used as the Bearer Token to authorize.

正解：B

解説：
To create an application that will integrate the Adobe Commerce system to get orders data for reporting using the get /v1/orders endpoint, you should use OAuth-based authentication to provide access to system resources. OAuth is a token-passing mechanism that allows a system to control which third-party applications have access to internal data without revealing or storing any user IDs or passwords. The integration will be registered by the merchant in the admin panel and will perform an OAuth handshake during activation. The third-party system should follow OAuth protocol to authorize. The merchant will have the ability to restrict or extend access to resources as well as to revoke the access using Admin Panel. Reference: 1
1: https://devdocs.magento.com/guides/v2.3/get-started/authentication/gs-authentication-oauth.html

質問 # 26
An Architect needs to review a custom product feed export module that a developer created for a merchant. During final testing before the solution is deployed, the product feed output is verified as correct. All unit and integration tests for code pass.
However, once the solution is deployed to production, the product price values in the feed are incorrect for several products. The products with incorrect data are all currently part of a content staging campaign where their prices have been reduced.
What did the developer do incorrectly that caused the feed output to be incorrect for products in the content staging campaign?

• A. The developer did not check for an active content staging campaign and emulates the campaign state when retrieving product data.
• B. The developer forgot to use the getContentStagingValue() method to retrieve the active campaign value of the product data
• C. The developer retrieved product data directly from the database using the entity_id column rather than a collection or repository.

正解：A

解説：
Based on the given scenario, it is likely that option C - "The developer did not check for an active content staging campaign and emulates the campaign state when retrieving product data" - is the correct answer. It appears that the developer did not take into account the active content staging campaign and did not properly adjust the product data when generating the product feed. As a result, the feed output is incorrect for products that are part of the staging campaign and have their prices reduced. The correct solution would be to check for an active content staging campaign and properly adjust the product data to reflect the campaign state.

質問 # 27
An Adobe Commerce Architect designs a data flow that contains a new product type with its own custom pricing logic to meet a merchant requirement.
Which three developments are valid when reviewing the implementation? (Choose three.)

• A. New price model extending \Magento\Catalog\Model\Product\Type\Price
• B. Custom type model extended from the abstract Product Type model
• C. A new class with custom pricing logic, extending the abstract Product model class
• D. Content of the etc/product_types.xml file
• E. Data patch to register the new product type
• F. Hydrator for attributes belonging to the new product type

正解：A、B、D

解説：
Explanation
According to some tutorials45, creating a custom product type in Adobe Commerce involves several steps, such as:
* Creating a product_types.xml file in etc folder to declare the new product type
* Creating a custom type model that extends from an abstract product type model
* Creating a custom price model that extends from an abstract price model
* Creating a layout file for the new product type
* Creating a data patch to register the new product type
Based on these steps, I would say that three possible developments that are valid when reviewing the implementation are:
* A. Content of the etc/product_types.xml file
* C. Custom type model extended from the abstract Product Type model
* F. New price model extending \Magento\Catalog\Model\Product\Type\Price These developments would allow creating a new product type with its own custom pricing logic and attributes.

質問 # 28
An Architect working on a headless Adobe Commerce project creates a new customer attribute named my_attribure. Based on the attribute value of the customer, the results of GraphQI queries are modified using a plugin. The frontend application is communicating with Adobe Commerce through Varnish by Fastly, which is already caching the queries that will be modified. The Adobe Commerce Fastly extension is installed, and no other modifications are made to the application.
Which steps should the Architect take to make sure the vcl_hash function of Varnish also considers the newly created attribute?
A)

B)

C)

• A. Option B
• B. Option C
• C. Option A

正解：A

解説：
Option B is the correct way to make sure the vcl_hash function of Varnish also considers the newly created attribute. The Architect should create a new module that depends on Magento_Fastly and declare a plugin for \Magento\Fastly\Model\Config::getVclSnippets() method. The plugin should add a new snippet to the result array with the type 'recv' and the content 'set req.http.my_attribute = req.http.X-Magento-Vary;'. This will append the value of the customer attribute to the hash key used by Varnish for caching. Option A is incorrect because it modifies the core file of Magento_Fastly module, which is not recommended and can cause issues during upgrades. Option C is incorrect because it uses the wrong type and content for the snippet, which will not affect the vcl_hash function. Reference: https://devdocs.magento.com/cloud/cdn/fastly-vcl-bypass-to-origin.html According to the Adobe Commerce Developer Guide2, to make sure the vcl_hash function of Varnish also considers the newly created attribute, the Architect should use a plugin for Magento\Customer\Model\Context::getVaryString method and add the attribute value to the vary string. This will ensure that Varnish caches different versions of GraphQL queries based on the attribute value of the customer. Therefore, option B is correct. Option A is not correct because it does not affect the vcl_hash function. Option C is not correct because it does not use a plugin for the getVaryString method.

質問 # 29
An Adobe Commerce Architect notices that the product price index takes too long to execute. The store is configured with multiple websites and dozens of customer groups.
Which two ways can the Architect shorten the full price index execution time? (Choose two.)

• A. Edit customer groups to exclude websites that they are not using
• B. Enable price index customer group merging for products without tier prices
• C. Move catalog price_index indexer to another custom indexer group
• D. Set Customer Share Customer Accounts Option to Global
• E. Set MaGE_INDEXER_THREADS_COUNT environment variable to enable parallel mode

正解：B、E

解説：
Explanation
The two best ways the Architect can shorten the full price index execution time are Option A. Enable price index customer group merging for products without tier prices, and Option D. Set MaGEINDEXERTHREADS_COUNT environment variable to enable parallel mode. Enablingcustomer group merging will help reduce the number of customer groups that need to be processed, while setting the environment variable will allow the indexer to use multiple threads and run in parallel mode, thus reducing the overall execution time.

質問 # 30
A company wants to build an Adobe Commerce website to sell their products to customers in their country.
The taxes in their country are highly complex and require customization to Adobe Commerce. An Architect is trying to solve this problem by creating a custom tax calculator that will handle the calculation of taxes for all orders in Adobe Commerce.
How should the Architect add the taxes for all orders?

• A. Write a before plugin to \Magento\Quote\Model\QuoteManagement::placeOrder() and add the custom tax to the quote
• B. Declare a new total collector in "etc/sales.xml" in a custom module
• C. Add a new observer to the event 'sales_quote_collect_totals_before" and add the custom tax to the quote

正解：B

解説：
you can create tax rules in Magento 2 by going to Stores > Taxes > Tax Rules and choosing or adding tax rates.
However, this may not be enough for complex tax scenarios that require customization.
https://amasty.com/knowledge-base/how-to-configure-tax-calculation-in-magento-2.html
To add a new total to the order, the Architect should declare a new total collector in the "etc/sales.xml" file of a custom module.
This file defines the order of calculation and rendering of totals.
The Architect should also implement a model class that extends \Magento\Quote\Model\Quote\Address\Total\AbstractTotal and overrides the collect() and fetch() methods to handle the logic of adding the custom tax to the quote and order.
Reference: https://devdocs.magento.com/guides/v2.4/howdoi/checkout/checkout_new_total.html

質問 # 31
An external system integrates functionality of a product catalog search using Adobe Commerce GraphQL API.
The Architect creates a new attribute my_attribute in the admin panel with frontend type select.
Later, the Architect sees that Productinterface already has the field my_atcribute, but returns an mc value. The Architect wants this field to be a new type that contains both option id and label.
To meet this requirement, an Adobe Commerce Architect creates a new module and file etc/schema.graphqls that declares as follows:

After calling command setup:upgrade, the introspection of Productlnterface field xy_attribute remains int.
What prevented the value type of field my_attribute from changing?

• A. The fields of Productlnterface are checked during processing schema.graphqls files. If they have a corresponding attribute, then the backendjype of product attribute is set for field type.
• B. The Magento.CatalogGraphQI module occurs later in sequence than the Magento.GraphQI module and merging output of dynamic attributes schema reader overrides types declared in schema.graphqls
• C. The interface Productlnterface is already declared in Magento.CatalogGraphQI module. Extending requires use of the keyword -xceni before a new declaration of Productlnterface.

正解：B

解説：
Explanation
products query is a GraphQL query that returns information about products that match specified search criteria. It also shows how to use ProductInterface fields to retrieve product data.
https://devdocs.magento.com/guides/v2.3/graphql/queries/products.html

質問 # 32
An Architect needs to integrate an Adobe Commerce store with a new Shipping Carrier. Cart data is sent to the Shipping Carrier's API to retrieve the price and display to the customer. After the feature is implemented on the store, the API hits its quota and returns the error "Too many requests". The Shipping Carrier warns the store about sending too many requests with the same content to the API.
In the carrier model, what should the Architect change to fix the problem?

• A. Override getResponse (), save the response to a variable, check if the response exists, then return.
• B. In _doShipmentRequest (), call canCollectRates() before sending request to the API
• C. Implement _setCachedQuotes () and_getCachedQuotes() return the data if the request matches.

正解：C

解説：
Explanation
Implementing setCachedQuotes () andgetCachedQuotes() in the carrier model can allow the store to store the cart data in a cache, so that repeated requests with the same content can be retrieved from the cache instead of sending a new request to the API. This can reduce the number of requests and avoid hitting the quota limit.
References:
[1] https://docs.adobe.com/content/help/en/experience-manager-65/commerce/commerce-payment-shipping-mod

質問 # 33
While reviewing a newly developed pull request that refactors multiple custom payment methods, the Architect notices multiple classes that depend on \Magento\Framework\Encryption\EncryptorInterf ace to decrypt credentials for sensitive dat a. The code that is commonly repeated is as follows:

In each module, the user_secret config is declared as follows:

The Architect needs to recommend an optimal solution to avoid redundant dependency and duplicate code among the methods. Which solution should the Architect recommend?

• A. Replace all Vendor\PaymentModule\Gateway\Config\Config Classes With virtualTyp- Of Magento\Payxer.t\Gateway\Conflg\Config and Set <user_secret backend_Model="Magento\Config\Model\Config\Backend\Encrypted" /> under ccnfig.xml
• B. Add a plugin after the getvalue method of $sccpeConfig, remove the $encryptor from dependency and use it in the plugin to decrypt the value if the config name is 'user.secret?
• C. Create a common config service class vendor\Payment\Gateway\config\Config under Vendor.Payment and use it as a parent class for all of the Vender \EaymentModule\Gateway\Config\Config Classes and remove $sccpeConfig and $encryptor dependencies

正解：A

解説：
To avoid redundant dependency and duplicate code among the methods, the Architect should recommend replacing all Vendor\PaymentModule\Gateway\Config\Config classes with virtualType of Magento\Payment\Gateway\Config\Config and setting <user_secret backend_model="Magento\Config\Model\Config\Backend\Encrypted" /> under config.xml. This will allow using the core config class that already has the scopeConfig dependency and the logic to get the value from the config. The backend_model attribute will ensure that the user_secret value is encrypted and decrypted automatically by the core EncryptorInterface class. Option B is incorrect because it will add unnecessary complexity and overhead to the scopeConfig object. Option C is incorrect because it will still require creating a custom config service class and injecting the encryptor dependency. Reference: https://devdocs.magento.com/guides/v2.4/payments-integrations/base-integration/integration-intro.html https://devdocs.magento.com/guides/v2.4/config-guide/prod/config-reference-encryptor.html

質問 # 34
An Adobe Commerce Architect gets a request to change existing payment gateway functionality by allowing voided transactions only for a certain range of paid amounts.
In the vendor module file etc/config.xml,payment method has an option can,_voidsetto 1.
How should this customization be done?

• A. Add new handler with name can_void to virtualType based on typeMagento payment\Gateway\config\ValueHandlerPool In payment method facade configuration.
• B. Declare a new plugin for class Magento\Payment\ Gateway\Config\ConfigValueHandler and using the afterHandle method, change the result for Subject can_void.
• C. Extend Magento\Payment\Model\\Method\Adapter and reimplement method void. Use this new class as a new type of payment method facade configuration overriding virtualType type for adapter.

正解：C

解説：
Explanation
payment facade is an instance of Payment Adapter configured with virtual types and allows to process payment actions between Magento Sales Management and payment processor. It also says that you can add dependency injection (DI) configuration for payment method facade in your %Vendor_Module%/etc/di.xml file.
https://devdocs.magento.com/guides/v2.3/payments-integrations/base-integration/facade-configuration.html

質問 # 35
A merchant is utilizing an out-of-the-box Adobe Commerce application and asks to add a new reward card functionality for customers. During the code review, the Adobe Commerce Architect notices the reward_card_number attribute setup created for this functionality is causing the customer attribute to be unavailable in the My account/My rewards page template.

What should be added to set the customer attribute correctly?

• A. scope property should be added with a value of global
• B. group property should be added with a value of 1
• C. system property should be added with a value of true

正解：A

質問 # 36
An external system integrates functionality of a product catalog search using Adobe Commerce GraphQL API. The Architect creates a new attribute my_attribute in the admin panel with frontend type select.
Later, the Architect sees that Productinterface already has the field my_atcribute, but returns an mc value. The Architect wants this field to be a new type that contains both option id and label.
To meet this requirement, an Adobe Commerce Architect creates a new module and file etc/schema.graphqls that declares as follows:

After calling command setup:upgrade, the introspection of Productlnterface field xy_attribute remains int. What prevented the value type of field my_attribute from changing?

• A. The fields of Productlnterface are checked during processing schema.graphqls files. If they have a corresponding attribute, then the backendjype of product attribute is set for field type.
• B. The interface Productlnterface is already declared in Magento.CatalogGraphQI module. Extending requires use of the keyword -xceni before a new declaration of Productlnterface.
• C. The Magento.CatalogGraphQI module occurs later in sequence than the Magento.GraphQI module and merging output of dynamic attributes schema reader overrides types declared in schema.graphqls

正解：A

解説：
According to the Adobe Commerce Developer Guide1, the fields of ProductInterface are checked during processing schema.graphqls files. If they have a corresponding attribute, then the backend_type of product attribute is set for field type. Therefore, the value type of field my_attribute remains int because it corresponds to the attribute my_attribute that has a frontend type select and a backend_type int.

質問 # 37
An Adobe Commerce Architect is supporting deployment and building tools for on-premises Adobe Commerce projects. The tool is executing build scripts on a centralized server and using an SSH connection to deploy to project servers.
A client reports that users cannot work with Admin Panel because the site breaks every time they change interface locale.
Considering maintainability, which solution should the Architect implement?

• A. Adjust the tool's build script and specify required locales during 'setup:static-content:deploy' command
• B. Edit project env.php file, configure 'admin_locales_for.build' value, and specify all required locales
• C. Modify project config.php file, configure 'admin_locales_for_deploy' value, and specify all required locales

正解：A

解説：
The 'setup:static-content:deploy' command allows you to generate static view files for specific locales. If you do not specify any locales, the command uses the default locale that is set in the configuration. To avoid breaking the site when changing interface locale in the Admin Panel, you need to generate static view files for all the locales that you want to use. You can do this by adjusting the tool's build script and adding the locales as arguments to the 'setup:static-content:deploy' command. For example:
bin/magento setup:static-content:deploy en_US fr_FR de_DE
This will generate static view files for English, French, and German locales. Reference: https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/setup/static-view.html?lang=en#generate-static-view-files

質問 # 38
An Adobe Commerce Architect is working on a scanner that will pull prices from multiple external product feeds. The Architect has a list of vendors and decides to create new config file marketplacejeeds.xml.
Which three steps can the Architect take to ensure validation of the configuration files with unique validation rules for the individual and merged files? (Choose three.)

• A. Implement validation rules in the Converter class for the Config Reader
• B. Add the Uniform Resource Name to the XSD file in the config XML file.
• C. Provide schema to validate a merged file.
• D. Create a class that implements \Magento\Framework\Config\Datalnterface.
• E. Provide schema to validate an individual file.
• F. Create validation rules in marketplace.schema.xsd.

正解：B、C、E

解説：
To ensure validation of the configuration files with unique validation rules for the individual and merged files, you need to do the following steps:
Add the Uniform Resource Name (URN) to the XSD file in the config XML file. The URN is a unique identifier for a resource that follows a specific syntax. For example:
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Vendor_Module:etc/marketplacefeeds.xsd"> Provide schema to validate a merged file. The schema defines the structure and constraints of the XML document that represents the merged configuration from all modules. The schema file should be named as <config_file_name>.xsd and placed in the etc directory of the module. For example:
marketplacefeeds.xsd
Provide schema to validate an individual file. The schema defines the structure and constraints of the XML document that represents the configuration from a single module. The schema file should be named as <config_file_name>_merged.xsd and placed in the etc directory of the module. For example:
marketplacefeeds_merged.xsd

質問 # 39
An Adobe Commerce Architect needs to set up two websites on a single Adobe Commerce instance with base URLs: example.com and website2.example.com.
How should the Architect configure this project so that both websites can use the same customer base?

• A. Change Session Cookie attribute to "SameSite=None"
• B. Disable Session Validation for "HTTP_X_FORWARDED_FOR" header
• C. Set Cookie Domain for both websites to ".example.com"

正解：C

解説：
By setting the same cookie domain for both websites, the customer base can be shared between both websites, as the customer will be authenticated by the same cookie across both sites. This will ensure that customers don't have to log in twice when switching between the two sites.
Setting Cookie Domain for both websites to ".example.com" will allow both websites to use the same customer base. This is because the cookie domain determines which websites can access the customer information stored in the cookie. By using a common domain, both websites can share the same customer cookie. See Multiple websites or stores in the Adobe Commerce Help Center1. Reference: https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/multi-sites/ms-overview.html?lang=en1

質問 # 40
Due to a marketing campaign, a website is experiencing a very large number of simultaneously placed orders, which is affecting checkout performance. The website is in the production deploy mode.
Which two website settings can an Architect optimize to decrease the impact on checkout performance? (Choose two.)

• A. Asynchronous indexing admin panel Setting (Stores > Settings > Ccr.f iguraticr. > Advanced > developer > Grid Settings > Asynchronous indexing) can be enabled by executing the following CLI command: tm/magento config:set dev/grid/async_ini*xmg 1
• B. Asynchronous email notifications admin panel Setting (stores > Settings > Configuration > Sales > Sales Emails > General Settings > Asynchronous) can be enabled
• C. Multithreaded checkout processing admin panel setting (stores > s ettmgs > Configuration > Sales > Checkout > General Settings > Asynchronous) can be set to a higher value representing the number of PHP threads used exclusively for checkout
• D. A new database can be created and the Split Database feature can be automatically configured with the following command: bin/Magento setup:db-schema:split-sales-sales --host=''<checkout db host or ip>" -dbname="<name>" -username""<checkout db username>'' -password=" <password>"
• E. The website deploy mode can be set to si-g- by executing the following CLI command: bin/magento deploy:mode:set siege. Provided that it will be changed back to production as soon as the number of simultaneously placed orders decreases to acceptable levels

正解：A、D

解説：
Asynchronous indexing allows Magento to process indexers in the background without affecting the storefront performance. Splitting the database allows Magento to use a separate database for checkout-related tables, which reduces the load on the main database and improves checkout performance. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#asynchronous-indexing https://devdocs.magento.com/guides/v2.4/config-guide/multi-master/multi-master.html To decrease the impact on checkout performance, the Architect should do two things:
Enable asynchronous indexing admin panel setting. This will allow Magento to update indexes using cron jobs instead of doing it on the fly during checkout. This option can be found under Stores > Settings > Configuration > Advanced > Developer > Grid Settings > Asynchronous indexing. It can also be enabled by executing the following CLI command: bin/magento config:set dev/grid/async_indexing 1 Create a new database and use the Split Database feature. This will allow Magento to separate the sales data from the main database and reduce the load on the database server. This option can be configured with the following command: bin/magento setup:db-schema:split-sales --host='<checkout db host or ip>' --dbname='<name>' --username='<checkout db username>' --password='<password>' Reference:
https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#m2devgde-asynchronous-indexing
https://devdocs.magento.com/guides/v2.4/config-guide/multi-master/multi-master.html

質問 # 41
An Adobe Commerce Architect is asked by a merchant using B2B features to help with a configuration issue.
The Architect creates a test Company Account and wants to create Approval Rules for orders. The Approval Rules tab does not appear in the Company section in the Customer Account Menu when the Architect logs in using the Company Administrator account.
Which two steps must be taken to fix this issue? (Choose two.)

• A. Make sure that the 'Purchase Order' payment method is active
• B. Merchant needs to log out of frontend and then log back in to load new permissions
• C. Set Enable Purchase Orders' on the Company Record to TRUE
• D. Set 'Enable Purchase Orders' in the B2B Admin to TRUE
• E. Set 'Enable B2B Quote" in the B2B Admin to TRUE

正解：C、D

解説：
Enabling Purchase Orders at both the B2B Admin and the Company Record levels is necessary for Approval Rules to appear in the Company section of the Customer Account Menu. When 'Enable Purchase Orders' is set to TRUE, the system assumes that the company will be making purchases using purchase orders, and the Approval Rules tab becomes visible.
To create Approval Rules for orders, the Architect needs to enable Purchase Orders both in the B2B Admin and on the Company Record. This will allow the Company Administrator to access the Approval Rules tab in the Customer Account Menu and create rules based on various criteria. The Purchase Order payment method and the B2B Quote feature are not required for this functionality. Reference: https://docs.magento.com/user-guide/customers/account-dashboard-approval-rules.html

質問 # 42
......

合格を確定するガイドでAD0-E718試験準備しよう：https://www.goshiken.com/Adobe/AD0-E718-mondaishu.html