AD0-E716 Adobe Commerce Developer Expert Questions and Answers

The plugin execution order is as follows:

• PluginA::beforeDispatch()
• PluginB::beforeDispatch()
• PluginA::aroundDispatch()
• The code in the around plugin
• PluginB::afterDispatch()
• PluginA::afterDispatch()

ThearoundDispatch()method is executed in a separate scope, so the code in the around plugin will be executed after thebeforeDispatch()methods of both plugins, but before theafterDispatch()methods of both plugins.

Here is a diagram that shows the plugin execution order:

PluginA

beforeDispatch()

aroundDispatch()

afterDispatch()

PluginB

beforeDispatch()

afterDispatch()

According to the Magento Stack Exchange answer, form key validation is a security feature that prevents CSRF attacks by checking if the form key in the request matches the one generated by Magento. If the developer does not include the form_key in their custom form, the validation will fail and an error will be shown. Therefore, the developer needs to add the form_key to their requests by using getBlockHtml (‘formkey’) ?> in their template file. Verified References: https://magento.stackexchange.com/questions/95171/magento-2-form-validation

To display the "file upload" field and process the actual CSV import, the following two requirements must be met:

• The developer must create a new system configuration setting that specifies the path to the CSV file.
• The developer must create a new controller action that handles the file upload and import process.

Thesystem.xmlfile is used to define system configuration settings. The following XML snippet shows how to define a new system configuration setting for the CSV file path:

XML

/path/to/csv/file

TheController\Adminhtml\ShipmentFeescontroller class is used to handle the file upload and import process. The following code shows how to create a new controller action that handles the file upload and import process:

PHP

public function uploadAction()

{

$file = $this->getRequest()->getFile('shipment_fees_csv_file');

if ($file->isUploaded()) {

$importer = new ShipmentFeesImporter();

$importer->import($file);

}

return $this->redirect('adminhtml/system_config/edit/section/shipment_fees');

}

To add an action to a pre-existing route without interfering with the functionality of the original route, the developer must use thebeforeorafterparameters in the route declaration. This will load the developer's module in before or after the original module, respectively.

For example, the following code would add an action to themy_module/indexroute before the action from the original module:

my_module_before

Themy_module_beforeaction would be executed before theMyModule\Controller\Indexaction, which would allow the developer to perform any necessary setup before the original action is executed.

Two features that come out of the box with Adobe Commerce Cloud are Support ACL and Fastly. Support ACL is a feature that allows the developer to manage access control lists for different users and roles on the Adobe Commerce Cloud platform. The developer can create and assign permissions for different actions and resources on the project and environment levels. Fastly is a cloud-based caching service that improves site performance and security forAdobe Commerce Cloud projects. Fastly provides features such as CDN, image optimization, WAF, DDoS protection, etc. Verified References: [Magento 2.4 DevDocs] 3

The developer can turn on outgoing emails on an Adobe Commerce Cloud Staging environment by accessing the Project Web Interface and selecting the Staging environment. Then, the developer can select Configure environment and toggle Outgoing emails On. This will enable the SMTP service for the Staging environment and allow emails to be sent from the application. Verified References: [Magento 2.4 DevDocs] 1

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.

Theattribute_identityattribute specifies whether the primary key of the table should be auto-incremented. Ifattribute_identityis set totrue, then theroll_nocolumn must have an index. Thestudent_namecolumn 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.

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

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

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]

To ensure that the developer's observer runs after the observer defined by the third-party module, they need to set the sort order of the new observer to be less than that of the third-party vendor's observer.

The sort order is a number that is assigned to each observer. The lower the number, the earlier the observer will be executed.

For example, if the third-party vendor's observer has a sort order of 10, the developer's observer would need to have a sort order of 9 or lower.

To configure the tracking_level parameter indi.xmlto have a value of 4 for theDownloadclass and all classes that extendDownload, the developer would use the following code:

Thesettingelement is used to set a configuration value for a specific model. Therewriteelement is used to override the default configuration value for a specific model. In this case, thetracking_levelparameter is set to 4 for all models that extendDownload.

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

The order in which the ECE-Tools package applies patches is as follows:

• All required Magento patches included in the Cloud Patches for Commerce package.
• Selected optional Magento patches included in the Quality Patches Tool.
• Custom patches in the /m2-hotfixes directory in alphabetical order by patch name.

The ECE-Tools package is a set of scripts and tools designed to manage and deploy Adobe Commerce Cloud projects. The Cloud Patches for Commerce package is a dependency of ECE-Tools that provides a set of required patches for Magento core issues that affect Adobe Commerce Cloud functionality. The Quality Patches Tool is an optional tool that allows developers to apply individual patches for specific Magento issues without waiting for a full product release. The /m2-hotfixes directory is a directory where developers can place their own custom patches for their Adobe Commerce Cloud projects. Verified References: [Magento 2.4 DevDocs]

According to the Magento Stack Exchange answer, system.xml is a file that defines the configuration fields for the admin area. Each field can have a validate attribute that specifies avalidation rule for the field value. Magento provides some built-in validation rules, such as phoneUS, which validates a US telephone number. Therefore, to ensure that the option contains a valid US telephone number, the developer needs to add phoneUS to the field in system.xml. Verified References:https://magento.stackexchange.com/questions/104570/magento-2-system-xml-validation-rules

The developer can resolve this issue by creating a plugin for theMagento\Catalog\Model\Indexer\Product\Price::executeRow()method. This method is responsible for updating the product price index.

The plugin can be used to add the pricing adjustment from the database to the product price index. Once the product price index is updated, the layered navigation will display the correct price.

Here is an example of a plugin for theexecuteRow()method:

PHP

class MyPlugin

{

public function executeRow(

\Magento\Catalog\Model\Indexer\Product\Price $subject,

\Magento\Catalog\Model\Product $product,

array $data

) {

$adjustment = $this->getAdjustment($product);

$product->setPrice($product->getPrice() + $adjustment);

}

private function getAdjustment(Product $product)

{

$adjustment = $product->getData('adjustment');

if (!is_numeric($adjustment)) {

return 0;

}

return $adjustment;

}

}

This plugin will add theadjustmentdata from the product to the product price index. Once the product price index is updated, the layered navigation will display the correct price.