Adobe AD0-E718 問題集

質問 1：
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. Implement _setCachedQuotes () and_getCachedQuotes() return the data if the request matches.
B. Override getResponse (), save the response to a variable, check if the response exists, then return.
C. In _doShipmentRequest (), call canCollectRates() before sending request to the API
正解：A
解説: (Topexam メンバーにのみ表示されます)

質問 2：
A merchant notices that product price changes do not update on the storefront.
The index management page in the Adobe Commerce Admin Panel shows the following:
* All indexes are set to 'update by schedule'
* Their status is 'ready'
* There are no items in the backlog
* The indexes were last updated 1 minute ago
A developer verifies that updating and saving product prices adds the relevant product IDs into the catalog_product_price_cl changelog table.
Which two steps should the Architect recommend to the developer to resolve this issue? (Choose two.)
A. Reduce the frequency of the cron job to 5 minutes so the items have more time to process.
B. Invalidate the catalog_product_price indexer in the Adobe Commerce Admin Panel so that it is fully reindexed next time the cron runs.
C. Make sure that the version_id for the price indexer in the mview_state table is not higher than the last entry for the same column in the changelog table and re-synchronize.
D. Manually reindex the catalog_product_price index from the Command line:bin\magentor indexer:reindex catalog_product_price.
E. Make sure that no custom or third-party modules modify the changelog and indexing process.
正解：C,E
解説: (Topexam メンバーにのみ表示されます)

質問 3：
A company has an Adobe Commerce store. An attribute named "my.attribute" (type "text") is created to save each product's global ID that is shared between multiple systems.
Several months after going live, the values of "my.attribute" are all integer. This causes a problem for the other systems when those systems receive this data.
An Adobe Commerce Architect needs to recommend a solution to change the type of "my.attribute" from textXo int Which two steps should the Architect take to achieve this? (Choose two.)
A. Migrate data from table "catalog_product_entity_text" to "catalog.producLentityjnt" for the attribute.id
B. Go to Admin > Stores > Attributes > Product, edit "my.attribute" and update type from "text' to "inf
C. Write a plugin for \Magento\Eav\Model\Entity\Attrlbute\Backend\AbstractBackend::afterLoad() and load data from "catalog_product_entity_int"
D. Create a Data Patch and update 'my.attribute' type from "text" to "inf
E. Run the Command bin/magentc indexer: reset catalog_product_attribute
正解：A,D
解説: (Topexam メンバーにのみ表示されます)

質問 4：
An Adobe Commerce Architect is troubleshooting an issue on an Adobe Commerce Cloud project that is not yet live.
The developers migrate the Staging Database to Production in readiness to Go Live. However, when the developers test their Product Import feature, the new products do not appear on the frontend.
The developers suspect the Varnish Cache is not being cleared. Staging seems to work as expected. Production was working before the database migration.
What is the likely cause?
A. The Fastly credentials in the Production Database are incorrect.
B. A deployment should have been done on Production to initialize Fastly caching.
C. The site URLs in the Production Database are the URLs of the Staging Instance and must be updated.
正解：A
解説: (Topexam メンバーにのみ表示されます)

質問 5：
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 retrieved product data directly from the database using the entity_id column rather than a collection or repository.
C. The developer forgot to use the getContentStagingValue() method to retrieve the active campaign value of the product data
正解：A
解説: (Topexam メンバーにのみ表示されます)