Adobe AD0-E722 Practice Test - Questions Answers, Page 5

Option B is correct because using VCL snippets to offload the redirect to Fastly is the best way to configure the redirects and ensure performance. VCL snippets are custom code segments that can be added to the Fastly configuration to modify the behavior of the caching service. By using VCL snippets, the redirects can be handled at the edge server level, without reaching the Magento application or the database.This reduces the server load and improves the response time for the redirected requests1.

Option A is incorrect because adding each redirect in the magento/routes.yaml file is not a recommended way to configure the redirects. The magento/routes.yaml file is used to define custom routes for Magento Cloud projects, such as mapping domains or subdomains to environments or services.Adding redirects in this file can cause conflicts with the existing routes and affect the routing logic of the project2.

Option C is incorrect because adding each redirect as a URL rewrite via the admin UI is not an optimal way to configure the redirects. The URL rewrite feature in Magento allows creating custom URLs for products, categories, and CMS pages, and redirecting them to their canonical URLs. However, adding a large number of URL rewrites can increase the database size and affect the performance of the Magento application.Moreover, using the admin UI for this task can be tedious and error-prone3.

1: Custom VCL snippets | Adobe Commerce Developer Guide

2: Configure routes | Adobe Commerce Developer Guide

3: URL Rewrites | Adobe Commerce User Guide

The issue here is that the sales totals in Sales Orders report show 0.00 for the new UK website. This is because the currency rates for GBP and USD are not configured, so the system cannot convert the order amounts from GBP to USD. The solution is to configure the currency rates for GBP and USD, so they are not empty.This will allow the system to calculate the sales totals in USD for the report.Reference: https://experienceleague.adobe.com/docs/commerce-admin/stores-sales/site-store/currency/currency-update.html?lang=en1

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

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

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

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

Developer mode is the best option for setting up a development environment for testing functionality, not performance, before being passed to the testing team. In developer mode:

Errors are logged and hidden from the user. This ensures that the user does not see any uncaught exceptions or debugging information, but the developers can still access them from the log files.

Cache mode can only be changed from command line. This prevents any accidental or unauthorized changes to the cache settings from the admin panel or other sources.

Static files are created dynamically and then cached. This allows the developers to see the latest changes to the static files without having to run the static content deployment command every time. The static files are also cached for faster loading.

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.

Developer mode is the best option for setting up a development environment for testing functionality, not performance, before being passed to the testing team. In developer mode:

Errors are logged and hidden from the user. This ensures that the user does not see any uncaught exceptions or debugging information, but the developers can still access them from the log files.

Cache mode can only be changed from command line. This prevents any accidental or unauthorized changes to the cache settings from the admin panel or other sources.

Static files are created dynamically and then cached. This allows the developers to see the latest changes to the static files without having to run the static content deployment command every time. The static files are also cached for faster loading.