Adobe Updated AD0-E722 Exam Questions and Answers by marlowe

To display additional content on the home page based on a custom customer attribute, the Architect needs to do the following steps:

• Add a new context value of “my_attribute” to Magento\Framework\App\Http\Context. This will allow the Full Page Cache to generate different versions of the page for customers with different values of “my.attribute”. The context value can be set using a plugin on the Magento\Customer\Model\Context class.
• Add a dynamic block with the content to the Home Page. A dynamic block is a type of content block that can be configured to display only to specific customer segments or conditions. The Architect can use the ‘my.attribute’ in the conditions of the dynamic block and assign it to the Home Page in the Content > Blocks section of the Admin Panel. References:
• Private content | Magento 2 Developer Documentation
• Dynamic Blocks | Adobe Commerce 2.3 User Guide - Magento

The issue here is that the gather_reporting_data job is running for a long time and blocking the sitemap_generate job from running. The solution is to create a new cron group for the reporting job and specify i so that the reporting job runs in a separate process and does not block the sitemap_generate job. References: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-architecture.html?lang=en#cron-groups-and-processes

The error is caused by the generated child class not being updated with the new dependency. Removing the generated child class will allow the system to generate a new child class with the correct dependency. The generated child class is a proxy class that extends the original controller class and overrides the constructor to inject the dependencies using the object manager. The generated child class is created when the system runs in developer mode with cache enabled, to avoid performance issues. However, when a new dependency is added to the original controller class, the generated child class does not reflect the change and causes a mismatch in the constructor arguments. Therefore, deleting the generated child class from the generated/code directory will solve the problem.

References:

• Generated code | Adobe Commerce Developer Guide
• Constructor signature change | Adobe Commerce Developer Guide