AD0-E716 Questions and Answers

The developer has to add a formkey for the new export option because the formkey is required for security reasons. Without the formkey, the request will be rejected and redirected to the dashboard page. Verified References: [Magento 2.4 User Guide] [Magento 2.4 DevDocs]

The developer can test the new feature under the integration environment by deactivating one of the active integration environment branches, creating a new active branch from integration and installing the module, and pushing the changes. This is because Enhanced Integration Environments have a limit of four active branches at a time, and each branch has its own dedicated database and services. The developer can use the Cloud CLI for Commerce tool to manage the branches and deploy the code changes. Verified References: [Magento 2.4 DevDocs] 1

To ensure that the configuration is deployed and consistent across all environments, the developer can use the following steps:

Create a data patch that contains the configuration for the new website.

Deploy the data patch to all environments.

Use the magento deploy:status command to verify that the configuration has been deployed to all environments.

According to the Develop data and schema patches guide for Magento 2 developers, data patches are classes that contain data modification instructions. They are defined in a //Setup/Patch/Data/.php file and implement MagentoFrameworkSetupPatchDataPatchInterface. Data patches can also implement Patchversioninterface to specify the module version that the patch is associated with. The getVersion() method returns the module version as a string. To skip changes that were already applied via old format (install/upgrade scripts), the developer should implement Patchversioninterface and return 1.5.4 on the getVersion() method. This way, the data patch will only be applied if the module version is greater than or equal to 1.5.4. Verified References: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/declarative-schema/data-patches.html

The following XML will allow the new content type to be a child of slider content types:

slider

improved_slide

Use code with caution. 

This XML will tell Magento that the slider content type can have improved_slide content types as children.

Decreasing the batch size value improves performance by reducing the memory usage for the temporary table. The batch size value determines how many rows of data are processed at a time by the indexer. A large batch size value can cause the allocated memory size for the temporary table to exceed 20% of innodb_buffer_pool_size, which can result in errors and slow down the indexing process. By lowering the batch size value, the indexer can process the data more efficiently and avoid memory issues. Verified References: [Magento 2.4 DevDocs] [Magento Stack Exchange]

The probable cause for the delay in reflecting the changes on the frontend after a full product import is the combination of the number of products, customer groups and websites. This leads to a huge amount of values being stored in the price index which is too large to be processed at a normal speed. The price index calculates the final price of each product for each customer group and website, taking into account various factors such as tax, discounts, catalog price rules, etc. When there are many products, customer groups and websites, the price index becomes very complex and time-consuming to update. Verified References: [Magento 2.4 DevDocs] [Magento Stack Exchange]

The reason why there are records remaining in the inventory_reservation table is that only reservations no longer needed are removed by the cron job. The inventory_reservation table tracks the quantity of each product in each order and creates a reservation for each product when an order is placed, shipped, cancelled or refunded. The initial reservation has a negative quantity value and the subsequent reservations have positive values. When the order is complete, the sum of all reservations for the product is zero. The cron job removes only those reservations that have a zero sum from the table, leaving behind any reservations that are still needed for incomplete orders. Verified References: [Magento 2.4 DevDocs] [Magento Stack Exchange]

The correct answers are A and C.

The errors in the snippet are:

Column roll_no does not have an index. It is needed since attribute_identity is set to true.

Column student_name does not have an attribute length.

The attribute_identity attribute specifies whether the primary key of the table should be auto-incremented. If attribute_identity is set to true, then the roll_no column must have an index. The student_name column does not have an attribute length, which is required for string columns.

The following code shows how to fix the errors:

XML

int

true

true

false

int

false

true

false

true

true

string

255

false

Once the errors have been fixed, the table can be created successfully.

To store a block in the system cache, the developer needs to set values for both the cache_lifetime and cache_key data properties of the block. The cache_lifetime property specifies how long the block should be cached, and the cache_key property specifies a unique identifier for the block.

The following code shows how to set the cache_lifetime and cache_key data properties of a block:

PHP

$block->setData('cache_lifetime', 600);

$block->setData('cache_key', 'my_custom_block');

Once the cache_lifetime and cache_key data properties have been set, the block will be stored in the system cache and will not be regenerated on each page load.

The developer can update the Staging environment with the latest code from Production by logging in to the Project Web Interface, choosing the Staging environment, and clicking Sync. This will synchronize the code, data, and media files from Production to Staging, creating an exact copy of Production on Staging. The developer can then deploy the new release to Staging and test it before pushing it to Production. Verified References: [Magento 2.4 DevDocs]

The developer can enable the magnification of CSS files on an Adobe Commerce Cloud Staging environment by locally running the command bin/magento config:set --lock-config dev/css/minify_files 1 from the command line. This will set the configuration value in the app/etc/config.php file and lock it from being changed in the Admin Panel. The developer then needs to commit the app/etc/config.php file and redeploy the environment. Verified References: [Magento 2.4 DevDocs] 2

According to the Declarative Schema Overview guide for Magento 2 developers, declarative schema is a new feature that allows developers to declare the final desired state of the database and has the system adjust to it automatically, without performing redundant operations. However, declarative schema does not support uninstalling modules or reverting changes. To remove a table when a module is disabled, the developer needs to add a schema patch that implements Magento\Framework\setup\Patch\PatchRevertabieinterface and drops the table in the revert function. The revert function will be executed when the module is disabled using bin/magento module:disable command. Verified References: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/declarative-schema/

The extension attributes are missing because the collection="true" attribute is not set in the etc/extension_attributes.xmi file. This attribute tells Magento that the extension attributes should be returned when the quote is retrieved.

To fix this issue, the developer needs to add the collection="true" attribute to the my_attributes extension attribute.

Once the collection="true" attribute is set, the extension attributes will be returned when the quote is retrieved.

Two ways to access the PHP error logs on Adobe Commerce Cloud are to use the dedicated command from Cloud CLI for Commerce and to connect to the servers via SSH and localize the log files. The Cloud CLI for Commerce is a command-line tool that allows developers to interact with their Adobe Commerce Cloud projects and environments. The developer can use the command magento-cloud log php to view or download the PHP error logs from any environment. Alternatively, the developer can connect to the servers via SSH and navigate to the var/log directory where the PHP error logs are stored. Verified References: [Magento 2.4 DevDocs] 3