AD0-E716 Adobe Commerce Developer with Cloud Add-on Question and Answers

The possible reason why the payment method is missing in the admin is that in the module config.xml, the node can_use_internal was not set to true. This node determines whether the payment method can be used in the admin area or not. If it is set to false or omitted, the payment method will not be available for admin orders. To enable the payment method for admin use only, the node can_use_internal should be set to true and the node can_use_checkout should be set to false. Verified References: [Magento 2.4 DevDocs] [Magento Stack Exchange]

According to the ImageUploader component guide for Magento 2 developers, the ImageUploader UI component gives users the ability to upload images to the Magento Media Gallery. This component is a variation of the FileUploader component and uses the same configuration settings. The ImageUploader component uses the Magento\catalog\Model\iinageUploader class for image uploading, which has properties such as basePath and baseTmpPath that define where the images are stored. To extend the default imageuploader class and use it without affecting the other modules that are already using it, the developer needs to create a virtual type of this class in their module’s di.xml file and specify different values for basePath and baseTmpPath. The developer also needs to inject their virtual type into their admin controller using the imageUploader argument. Therefore, option B is the correct answer, as it shows the correct di.xml and controller code to extend and use the imageuploader class. Verified References: https://devdocs.magento.com/guides/v2.3/ui_comp_guide/components/image-uploader/

To allow theis_delayedEAV attribute to be used in the .phtml cart page, the developer needs to create a new file calledetc/catalog_attributes.xmi. This file will contain the definition of theis_delayedattribute.

The following code shows how to create theetc/catalog_attributes.xmifile:

XML

Is Delayed

This attribute indicates whether the product is delayed.

10

false

Once theetc/catalog_attributes.xmifile has been created, theis_delayedattribute will be available in the .phtml cart page. The attribute can be accessed using thegetIsDelayed()method of theProductclass.

PHP

$product = $block->getProduct();

$isDelayed = $product->getIsDelayed();

TheisDelayedvariable will contain the value of theis_delayedattribute. If the value of the attribute is 1, then the product is delayed. If the value of the attribute is 0, then the product is not delayed.

The developer can achieve this by adding the following configuration to their di.xml file:

XML

This configuration will ensure that all instances of theCustom\Module\Model\Exampleclass will receive a new instance of theMagento\Filesystem\Adapter\Localclass.

The developer can create a snapshot before deploying a critical feature to their Adobe Commerce Cloud (Pro Plan) production by using the dedicated button on Project Web Interface. A snapshot is a backup of an entire environment, including code, data, media files, and configuration settings. A snapshot can be used to restore an environment to a previous state in case of any issues or errors during deployment or testing. The developer can create a snapshot by accessing the Project Web Interface, choosing an environment, and clicking Create Snapshot. Verified References: [Magento 2.4 DevDocs]

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 anexact 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]

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');

}

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/

According to the Develop data and schema patches guide for Magento 2 developers, data patches can also implement PatchRevertabieinterface to provide rollback functionality for their changes. The revert() method contains the instructions to undo the data modifications made by the patch. To ensure that the product attribute is removed when the module is uninstalled, the developer should make the data patch implement PatchRevertabieinterface and implement the revert method to remove the product attribute using EavSetupFactory or AttributeRepositoryInterface. Verified References:https://devdocs.magento.com/guides/v2.3/extension-dev-guide/declarative-schema/data-patches.html

The developer can extend the existing CartltemPrices GraphQL schema to include a custom base_price field by adding the following code to the module’s etc/schema.graphqls file:

extend type CartltemPrices { base_price: Money! @doc(description: “The base price of the cart item”) }

This code adds a new field called base_price to the CartltemPrices type and specifies that it is of type Money and it is not nullable. The @doc directive adds a description for the field that will be shown in the schema documentation. The developer also needs to create a custom resolver class for the base_price field and declare it in the di.xml file of the module. 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]

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 following SearchCriteria query will replicate the SQL query:

$searchCriteria = new \Magento\Framework\Api\SearchCriteriaBuilder();

$searchCriteria->addFilter('name', 'Brand 1', 'eq');

$searchCriteria->addFilter('status', 1, 'eq');

$brandCollection = $this->brandRepository->getList($searchCriteria);

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()

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.

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.

Theinput_typeattribute of a product EAV attribute specifies the type of input field that will be used to enter the value of the attribute in the admin panel. Thetextareainput type is used for WYSIWYG fields. If theinput_typeattribute is not set totextarea, then the attribute will not appear as WYSIWYG in the admin panel.

To fix this, the developer should set theinput_typeattribute totextarea.