Adobe AD0-E718 Actual PDF : Adobe Commerce Architect Master

An Architect is configuring the preload.keys for Redis on an Adobe Commerce on-premise instance.
The Architect discovers that the following cache keys are loaded on each frontend request: eav_entity_types, GLOBAL_PLUGIN_LIST, DB_IS_UP_TO_DATE , SYSTEM_DEFAULT.
* The id_prefix of the frontend =>page_cache is set to 061_.
* The id_prefix of frontend => default: is not set.
* The Architect has enabled and configured Redis L2 caching.
How should the preload.keys be configured?
A)

B)

C)

D)

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

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

An existing Adobe Commerce website is moving to a headless implementation.
The existing website features an "All Brands" page, as well as individual pages for each brand. All brand-related pages are cached in Varnish using tags in the same manner as products and categories.
Two new GraphQL queries have been created to make this information available to the frontend for the new headless implementation:

During testing, the queries sometimes return out-of-date information.
How should this problem be solved while maintaining performance?

• A. Each GraphQL query's resolver class should inject MagentoGraphQICacheModelCacheableQuery and call setCacheValidity (true) on it as part of the resolver's rescive function
• B. Specify a @cache (cacheIdentity: path\\T\\identityClass) directive for each GraphQL query, corresponding to a class that adds cache tags for relevant brands and associated products
• C. Specify a @cache (cacheable: false directive for each GraphQL query, making sure that the data returned is not cached, and is up to date

An Adobe Commerce Architect needs to customize the workflow of a monthly installments payment extension. The extension is from a partner that is contracted with the default website PSR which has its own legacy extension (a module using deprecated payment method).
The installment payment partner manages only initializing a payment, and then hands the capture to be executed by the PSP. Once the amount is successfully captured, the PSP notifies the website through an IPN. The goal of the IPN is only to create an "invoice" and save the 'capture information' to be used later for refund requests through the PSP itself.
The Architect needs the most simple solution to capture the requested behavior without side effects.
Which solution should the Architect implement?

• A. Add a plugin before the $invoice-> () and changes its input to prevent the call of the $payment-> capture()
• B. Change the can_ capture attribute for the payment method under config.xml to be <can_capture>0</can_capture>
• C. Declare a capture command with type Magento\payment\Gateway\Command\NullCommand for the payment method CommandPool in di.zm1

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 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. 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 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.