AD0-E718 Adobe Commerce Architect Master Questions and Answers

When using multiple backend servers behind a load balancer, the session data must be stored in a shared location that is accessible by all servers. Otherwise, the session data will be inconsistent and users may experience issues such as being logged out unexpectedly. Redis is a recommended option for storing session data in a distributed architecture, as it provides fast and reliable access to the data. The session host value in the env.php file must point to the Redis instance that is used for session storage. References: https://devdocs.magento.com/guides/v2.4/config-guide/redis/redis-session.html

This option would allow caching GraphQL query results using Varnish or Fastly with proper invalidation and differentiation mechanisms.

To solve the problem of out-of-date information in GraphQL queries, the Architect should 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. This will allow Varnish to invalidate the cache for these queries when the brand or product data changes. Option A is incorrect because it will make the queries cacheable without any cache tags, which will not solve the problem. Option B is incorrect because it will disable caching for these queries entirely, which will degrade performance. References: https://devdocs.magento.com/guides/v2.4/graphql/caching.html

The ‘after’ plugin is not suitable for modifying the arguments or return value of the original method. The ‘around’ plugin allows the plugin method to wrap around the original method and modify its behavior and output. References: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/plugins.html#around-methods

To meet the requirements, the Architect should use the following solution: • Create Fixed Bundle Product for gathering simple products. This will allow the purchase of a pre-defined set of products with a discount and separate stock and tax class for each product. • Manage price for every selected option. This will allow setting the original and sales price for each product in the bundle. • Add extension attribute original_simple_price for \Magento\Sales\Api\Data\OrderItemExtensionInterface and populate value with price of simple product. This will allow exposing the original price of the simple product via REST API along with other required data. Option B is incorrect because Dynamic Bundle Product will not allow setting a pre-defined set of products with a discount. Option C is incorrect because Grouped Product will not allow setting a discount for the whole set of products. References: https://docs.magento.com/user-guide/catalog/product-create-bundle.html https://devdocs.magento.com/guides/v2.4/extension-dev-guide/extension_attributes/adding-attributes.html