Question No. 1

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?

AModify project config.php file, configure 'admin_locales_for_deploy' value, and specify all required locales

BEdit project env.php file, configure 'adminJocales_for_build' value, and specify all required locales

CAdjust the tools build script and specify required locales during *setup:static-content:deploy' command

Show Answer

Correct Answer: C

The issue here is that the site breaks every time the users change interface locale in the Admin Panel. This is because the static content for the different locales is not generated during the deployment process. The solution is to adjust the tools build script and specify required locales during *setup:static-content:deploy' command.This will ensure that the static content for all the needed locales is generated and deployed to the project servers.Reference: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/static-content.html?lang=en#deploy-static-view-files1

Question No. 2

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

* The id_pref ix of frontend => default is set to 762_.

* The Architect has enabled and configured Redis L2 caching.

How should the preload.keys be configured?

A)

B)

C)

D)

AOption A

BOption B

COption C

DOption D

Show Answer

Correct Answer: C

Option C is correct because it configures the preload.keys correctly for Redis L2 caching on an Adobe Commerce on-premise instance. Redis L2 caching is a feature that allows storing the cache data in both Redis and the local file system. This way, the cache data can be loaded faster from the local storage, while Redis acts as a cache invalidation service.To use Redis L2 caching, the backend option for both frontend => page_cache and frontend => default must be set to Magento\Framework\Cache\Backend\RemoteSynchronizedCache1. To enable the preload feature, which reduces the number of requests to Redis, the preload.keys option must be specified with the cache keys that are loaded on each frontend request.However, unlike Redis L1 caching, the preload.keys must include the suffix :hash to indicate that only the hash values of the cache data are stored in Redis2. Therefore, the correct configuration for preload.keys is:

[ '762_EAV_ENTITY_TYPES:hash', '762_GLOBAL_PLUGIN_LIST:hash', '762_DB_IS_UP_TO_DATE:hash', '762_SYSTEM_DEFAULT:hash', ],

Option A is incorrect because it configures the preload.keys incorrectly for Redis L2 caching. It uses the id_prefix of frontend => page_cache (063_) instead of frontend => default (762_) for the cache keys. This will cause a mismatch between the cache keys and the cache data, and result in incorrect or missing cache data.Moreover, it does not include the suffix :hash for the preload.keys, which is required for Redis L2 caching2.

Option B is incorrect because it configures the preload.keys incorrectly for Redis L2 caching.It does not include the suffix :hash for the preload.keys, which is required for Redis L2 caching2. It also uses a wrong cache key (GLOBAL_PLUGIN_LIST) instead of GLOBAL_PLUGIN_LIST.

Option D is incorrect because it configures the preload.keys incorrectly for Redis L2 caching. It uses a wrong id_prefix (162_) instead of frontend => default (762_) for the cache keys. This will cause a mismatch between the cache keys and the cache data, and result in incorrect or missing cache data. It also uses a wrong cache key (EAV_ENTITY_TYPES) instead of EAV_ENTITY_TYPES.

1:Two-level caching | Adobe Commerce Developer Guide

2:Use Redis for default cache | Adobe Commerce Developer Guide

Question No. 3

An Architect is investigating a merchant's Adobe Commerce production environment where all customer session data is randomly being lost. Customer session data has been configured to be persisted using Redis, as are all caches (except full page cache, which is handled via Varnish).

After an initial review, the Architect is able to replicate the loss of customer session data by flushing the Magento cache storage, either via the Adobe Commerce Admin Panel or running bin/magento cache: flush on the command line. Refreshing all the caches in the Adobe Commerce Admin Panel or running bin/magento cache: clean on the command line does not cause session data to be lost.

What should be the next step?

ACheck app/etc/env.php and make sure that the Redis configuration for caches and session data use different database numbers.

BEducate the merchant to not flush cache storage and only refresh the caches in future.

CSet the Stores > Configuration' option for Store Session Data Separately' to 'Yes' in the Adobe Commerce Admin Panel.

Show Answer

Correct Answer: A

The issue here is that the customer session data is randomly being lost when flushing the Magento cache storage. This is because the Redis configuration for caches and session data might be using the same database number, which causes the session data to be deleted along with the caches. The solution is to check the app/etc/env.php file and make sure that the Redis configuration for caches and session data use different database numbers.This will prevent the session data from being affected by the cache operations.Reference: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/redis.html?lang=en#configure-redis1

Question No. 4

An Adobe Commerce Architect notices that queue consumers close TCP connections too often on Adobe Commerce Cloud server leading to delays in processing messages.

The Architect needs to make sure that consumers do not terminate after processing available messages in the queue when CRON job is running these consumers.

How should the Architect meet this requirement?

ASet cohsumers_wait_for_max_MESSAGES variable true in deployment stage.

BIncrease multiple_process limit to spawn more processes for each consumer

CChange max_messages from 10,000 to 1,000 for CRON_CONSUMERS_RUNNER variable.

Show Answer

Correct Answer: A

Option A is correct because setting the consumers_wait_for_max_messages variable true in the deployment stage is the best way to meet the requirement. This variable controls whether the queue consumers should wait for a maximum number of messages to process before terminating. If this variable is set to true, the consumers will not terminate after processing the available messages in the queue, but will wait until they reach the max_messages limit or the cron job timeout.This way, the consumers can keep the TCP connections open and avoid delays in processing messages1.

Option B is incorrect because increasing the multiple_process limit to spawn more processes for each consumer will not solve the issue of queue consumers closing TCP connections too often. The multiple_process limit determines how many parallel processes can be run for each consumer. Increasing this limit may improve the throughput of message processing, but it will also consume more server resources and may cause conflicts or errors.Moreover, it will not prevent the consumers from terminating after processing the available messages in the queue2.

Option C is incorrect because changing the max_messages from 10,000 to 1,000 for CRON_CONSUMERS_RUNNER variable will worsen the issue of queue consumers closing TCP connections too often. The max_messages variable defines how many messages each consumer should process before terminating. Decreasing this variable will make the consumers terminate more frequently, which will result in more TCP connections being closed and reopened.This will increase the delays in processing messages3.

1: Configure message queues | Adobe Commerce Developer Guide

2: Configure message queues | Adobe Commerce Developer Guide

3: Configure message queues | Adobe Commerce Developer Guide

Question No. 5

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

ASet 'Enable B2B Quote' in the B2B Admin to TRUE

BMerchant needs to log out of frontend and then log back in to load new permissions

CSet 'Enable Purchase Orders' in the B2B Admin to TRUE

DSet 'Enable Purchase Orders' on the Company Record to TRUE

EMake sure that the 'Purchase Order' payment method is active

Show Answer

Correct Answer: C, E

The issue here is that 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. This is because the Approval Rules feature requires two settings to be enabled: the Purchase Orders feature and the Purchase Order payment method. The solution is to set 'Enable Purchase Orders' in the B2B Admin to TRUE and make sure that the 'Purchase Order' payment method is active. This will allow the Architect to create and manage Approval Rules for orders.

Adobe AD0-E722 Exam Actual Questions

The questions for AD0-E722 were last updated on Oct 1, 2024.

Unlock All Questions for Adobe AD0-E722 Exam