AD0-E722 Sample Questions Answers

The group property determines which section of the customer account the attribute belongs to. By setting the group property to 1, the reward_card_number attribute will be assigned to the default group, which is the Account Information section. This will make the attribute available in the My account/My rewards page template. References: https://experienceleague.adobe.com/docs/commerce-admin/customers/customer-accounts/attributes/attribute-properties.html?lang=en#group 1

The issue here is that the product price changes are not reflected on the storefront, even though the indexes are set to update by schedule and there are no items in the backlog. This indicates that there might be some problem with the changelog and indexing process, which are responsible for tracking and applying the data changes to the index tables. Therefore, the Architect should recommend the developer to check if any custom or third-party modules interfere with the changelog and indexing process, and disable or fix them if needed. Additionally, the Architect should recommend the developer to verify that the version_id for the price indexer in the mview_state table is consistent with the last entry for the same column in the changelog table, and re-synchronize them if they are out of sync. This will ensure that the indexer can process all the data changes correctly and update the index tables accordingly. References: https://experienceleague.adobe.com/docs/commerce- admin/systems/tools/index-management.html?lang=en#cron-groups-and-processes1 https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#m2devgde-mview 2

According to the Adobe Commerce documentation, to create a new xml configuration file, the Architect needs to create a Data class and a Reader class for the custom module. The Data class is responsible for storing and retrieving the configuration data from the cache or the Reader class. The Data class should implement the “\Magento\Framework\Config\Data” interface or extend the “\Magento\Framework\Config\Data” class. The Reader class is responsible for reading and validating the xml configuration files from the file system. The Reader class should implement the '\Magento\Framework\Config\Reader\Filesystem" interface or extend the '\Magento\Framework\Config\Reader\Filesystem" class. The Architect also needs to declare the Data class and the Reader class in the di.xml file of the custom module, and specify the name of the xml configuration file, the converter class, and the schema locator class for the Reader class.

References:

• Configuration types | Adobe Commerce - Experience League
• Create configuration types | Adobe Commerce - Experience League

Private content blocks are sections of the page that are specific to each customer and are not cached by the server. To update these blocks when a customer performs an action, such as adding a gift registry item to the quote, the Adobe Commerce Architect needs to specify the new action in a sections.xml configuration file. This file defines which blocks need to be updated for each action and how often they should be updated.By doing this, the Architect can ensure that the private content blocks are refreshed with the latest data from the server. References:

• Private content | Magento 2 Developer Documentation
• Configure private content | Magento 2 Developer Documentation

The magento-vars.php file is used to set the website or store view based on the HTTP host, but it does not affect GraphQL requests. GraphQL requests are handled by a separate controller that does not use the magento-vars.php file. Instead, GraphQL requests use the default store view of the default website, unless a store header or store cookie is provided in the request. The store header or cookie should contain the store code of the desired store view. For example, to query data from website_two, the request should include a header like store: store_two or a cookie like store=store_two12. References:

• GraphQL overview | Adobe Commerce 2.4 User Guide - Magento
• How to set up multiple websites with Magento 2 - Mageplaza

According to the Adobe Commerce documentation, OAuth-based authentication is the recommended method for integrations that need access to system resources, such as orders, customers, products, etc. OAuth-based authentication allows the merchant to control the access level and scope of the integration, as well as to revoke the access at any time using the admin panel. OAuth-based authentication also requires an OAuth handshake between the integration and the Adobe Commerce system during activation, which ensures a secure exchange of tokens and keys. The third-party system should follow the OAuth protocol to obtain and refresh the access token, which will be used as the Bearer Token to authorize the REST API calls.

References:

• Authentication | Adobe Commerce Developer Guide
• OAuth-based authentication | Adobe Commerce Developer Guide

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. References: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/develop/deploy/static-content.html?lang=en#deploy-static-view-files 1

• Option A is correct because enabling the config flag under deployment/blue_green/enabled is one of the steps to ensure zero downtime during the deployment process of Magento 2 on-premises. This flag enables the blue-green deployment feature, which allows deploying a new version of the Magento application to a separate environment (blue) without affecting the current live environment (green). Once the new version is ready, the traffic can be switched from green to blue with minimal or no downtime1.
• Option C is correct because running bin/magento setup:upgrade --keep-generated is another step to ensure zero downtime during the deployment process of Magento 2 on-premises. This command updates the database schema and data without deleting the generated code and static view files. This way, the Magento application can still serve requests from the cache while the database is being upgraded2.
• Option B is incorrect because running bin/magento setup:upgrade --dry-run=true does not upgrade the database, but only checks if there are any errors or conflicts in the database schema or data. This command can be used for testing purposes, but it does not affect the deployment process or the downtime3.
• Option D is incorrect because there is no such option as --convert-old-scripts-true for the bin/magento setup:upgrade command. This option does not exist in Magento 2 and does not have any effect on the deployment process or the downtime.
• Option E is incorrect because there is no such config flag as developer/zero_down_time/enabled in Magento 2. This flag does not exist in Magento 2 and does not have any effect on the deployment process or the downtime.

References:

• 1: Blue-green deployment | Adobe Commerce Developer Guide
• 2: Deploy Magento to production | Adobe Commerce Developer Guide
• 3: Command-line installation options | Adobe Commerce Developer Guide

The Architect can take the following steps to ensure validation of the configuration files with unique validation rules for the individual and merged files:

• Create validation rules in marketplace.schema.xsd. This file defines the structure and constraints of the XML elements and attributes for the marketplace.feeds.xml configuration file. The Architect can use this file to specify the required and optional elements, data types, values, and patterns for the configuration file.
• Provide schema to validate a merged file. This schema is used to validate the final configuration file that is generated after merging all the individual configuration files from different modules. The Architect can use this schema to check the consistency and completeness of the merged configuration file.
• Provide schema to validate an individual file. This schema is used to validate each individual configuration file from each module before merging them. The Architect can use this schema to check the syntax and validity of each configuration file.

References: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/architecture/starter-architecture.html?lang=en#configuration-files 1 https://devdocs.magento.com/guides/v2.4/extension-dev-guide/build/XSD-XML-validation.html 2

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.

References: https://experienceleague.adobe.com/docs/commerce-admin/b2b/purchase-orders/account-dashboard-approval-rules.html?lang=en#account-dashboard 1 https://experienceleague.adobe.com/docs/commerce-admin/b2b/purchase-orders/purchase-order-payment-method.html?lang=en#payment-method 2

• Option C is correct because the developer did not check for an active content staging campaign and emulate the campaign state when retrieving product data. Content staging campaigns can modify the product data such as price, name, description, and so on, based on a schedule. To get the correct product data for a specific date and time, the developer needs to use the Magento\Staging\Model\VersionManager class to set the current version ID and emulate the campaign state1. Otherwise, the product data will be retrieved from the default store view without applying the campaign changes.
• Option A is incorrect because retrieving product data directly from the database using the entity_id column is not necessarily wrong. It may not be the best practice, but it does not cause the feed output to be incorrect for products in the content staging campaign. The content staging campaigns are stored in separate tables with a version ID that links to the main product table2. The developer can still join these tables and query the product data based on the version ID and date.
• Option B is incorrect because there is no such method as getContentStagingValue in Magento 2. The developer cannot use this method to retrieve the active campaign value of the product data. The correct way to get the product data for a specific campaign is to use the Magento\Staging\Model\VersionManager class as mentioned above.

References:

• 1: Content Staging | Adobe Commerce Developer Guide
• 2: Content Staging | Adobe Commerce Developer Guide

The issue here is that the database storage is not being fully cleaned after the test is run. The solution is to modify the method PHPDoc and change the annotation @magentoDbIsolation to enabled. This will ensure that the database storage is fully cleaned after the test is run. References: https://developer.adobe.com/commerce/testing/guide/integration/#database-isolation 1