AD0-E716 Practice Questions

According to the Configure and run cron guide for Magento 2 developers, the crontab.xmi file is used

to declare and configure cron jobs for a module. The file should specify the name, instance, method

and schedule of the cron job. Therefore, creating a crontab.xmi file and setting a schedule for the

new cron job are the minimally required steps to accomplish this task. Verified Reference:

https://devdocs.magento.com/guides/v2.3/config-guide/cli/config-cli-subcommands-cron.html

The _transformAttrs class property array of the importer and exporter classes can be used to specify

a serializer class for a particular attribute. The serializer class will be used to convert the attribute

value from one format to another when the data is exported or imported.

In this case, the developer can specify a serializer class that will convert the JSON data in the

media_gallery attribute to a string. This will prevent the software that the client is using to modify

the exported data from changing the JSON data.

The following code shows how to specify a serializer class for the media_gallery attribute:

PHP

class MySerializer

{

public function serialize($value)

{

return json_encode($value);

}

public function deserialize($value)

{

return json_decode($value);

}

}

$importer->setSerializer('media_gallery', MySerializer::class);

$exporter->setSerializer('media_gallery', MySerializer::class);

Once the serializer class has been specified, the JSON data in the media_gallery attribute will be

converted to a string when the data is exported or imported. This will prevent the software that the

client is using to modify the exported data from changing the JSON data.

The developer can use the plugin to trigger the consumer restart by calling the function

\Magento\Framework\MessageQueue\Consumers\TriggerRe5tartInterface:trigger(). This function

will write a flag to the cache storage that will be checked by the consumer process. If the flag is set,

the consumer process will terminate itself and restart with the updated configuration. Verified

Reference: [Magento 2.4 DevDocs] 1

The developer needs to add environment level environment variables to be sure that the payment

configurations are always properly set on the Staging environment. Environment variables are

configuration settings that affect the behavior of the Adobe Commerce Cloud application and

services. Environment variables can be set at the project level or the environment level. Project level

variables apply to all environments, while environment level variables override the project level

variables for a specific environment. The developer can use environment level variables to customize

the payment configurations for the Staging environment without affecting other environments.

Verified Reference: [Magento 2.4 DevDocs]

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 for Adobe Commerce Cloud

projects. Fastly provides features such as CDN, image optimization, WAF, DDoS protection, etc.

Verified Reference: [Magento 2.4 DevDocs] 3

To allow the is_delayed EAV attribute to be used in the .phtml cart page, the developer needs to

create a new file called etc/catalog_attributes.xmi. This file will contain the definition of the

is_delayed attribute.

The following code shows how to create the etc/catalog_attributes.xmi file:

XML

Is Delayed

This attribute indicates whether the product is delayed.

10

false

Once the etc/catalog_attributes.xmi file has been created, the is_delayed attribute will be available

in the .phtml cart page. The attribute can be accessed using the getIsDelayed() method of the

Product class.

PHP

$product = $block->getProduct();

$isDelayed = $product->getIsDelayed();

The isDelayed variable will contain the value of the is_delayed attribute. 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 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 Reference: [Magento 2.4 DevDocs] [Magento Stack Exchange]

Two options to get the connection credentials for the environment’s deployed services are to run the

magento-cloud relationships CLI command and to connect to the server via SSH and read

$_ENV[‘services’] variable. The magento-cloud relationships CLI command displays information

about the relationships between an environment and its services, such as database, cache, search,

etc. The developer can use this command to get the connection data for each service in JSON

format. Alternatively, the developer can connect to the server via SSH and read the $_ENV[‘services’]

variable, which contains the same information as the CLI command output. Verified Reference:

[Magento 2.4 DevDocs] 3

According to the Magento Stack Exchange answer, UI components are used to render various

elements on Magento admin pages, such as grids, forms, buttons, etc. UI components are defined in

XML files that are located in the view/adminhtml/ui_component directory of each module. To add a

custom logic to render a column in a grid, the developer should create a custom class extending

MagentoUiComponentListingColumnsColumn and add the custom logic within the

prepareDataSource method. This method receives an array of data sources and modifies them

according to the column logic. The developer should also add an attribute class to the column node

within the module’s customer_listing.xml file and specify their custom class name as its value.

Verified Reference: https://magento.stackexchange.com/questions/317821/how-to-add-customlogic-to-render-a-column-in-a-grid-in-magento-2

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 Reference: [Magento 2.4 DevDocs] [Magento Stack Exchange]