Adobe AD0-E716 Practice Test - Questions Answers, Page 3

To configure the tracking_level parameter in di.xml to have a value of 4 for the Download class and all classes that extend Download, the developer would use the following code:

<config>

<global>

<models>

<Vendor\FreeDownload\Model\Download>

<setting name='tracking_level' value='4'/>

</Vendor\FreeDownload\Model\Download>

<Vendor\FreeDownload\Model\DownloadPdf>

<rewrite name='tracking_level' value='4'/>

</Vendor\FreeDownload\Model\DownloadPdf>

<Vendor\FreeDownload\Model\DownloadImage>

<rewrite name='tracking_level' value='4'/>

</Vendor\FreeDownload\Model\DownloadImage>

</models>

</global>

</config>

The setting element is used to set a configuration value for a specific model. The rewrite element is used to override the default configuration value for a specific model. In this case, the tracking_level parameter is set to 4 for all models that extend Download.

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

Reference: https://devdocs.magento.com/guides/v2.3/ui_comp_guide/components/image-uploader/

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 a validation 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 <validate>phoneUS</validate> to the field in system.xml. Verified

Reference: https://magento.stackexchange.com/questions/104570/magento-2-system-xml-validation-rules

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.

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

<?xml version='1.0'?>

<catalog_attributes>

<label>Is Delayed</label>

<note>This attribute indicates whether the product is delayed.</note>

<sort_order>10</sort_order>

<required>false</required>

</catalog_attributes>

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.

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

Reference: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/declarative-schema/

The correct answers are A and C.

The errors in the snippet are:

Columnroll_nodoes not have an index. It is needed sinceattribute_identityis set totrue.

Columnstudent_namedoes 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

<table name='vendor_module_table'>

<entity_id>

<type>int</type>

<identity>true</identity>

<unsigned>true</unsigned>

<nullable>false</nullable>

</entity_id>

<roll_no>

<type>int</type>

<identity>false</identity>

<unsigned>true</unsigned>

<nullable>false</nullable>

true

<index>true</index>

</roll_no>

<student_name>

<type>string</type>

<length>255</length>

<nullable>false</nullable>

</student_name>

</table>

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

The input_type attribute 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. The textarea input type is used for WYSIWYG fields. If the input_type attribute is not set to textarea, then the attribute will not appear as WYSIWYG in the admin panel.

To fix this, the developer should set the input_type attribute to textarea.

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.