An Adobe Commerce developer is trying to remove a block using the <remove name="test.block'/> tag in a layout XML file but it shows an error and doesn't work.Which tag would be applied to fix the error?
Answer(s): A
To remove a block using layout XML, the developer should use the <referenceBlock> tag with the name attribute specifying the name of the block and the remove attribute set to true. For example:<referenceBlock name="test.block" remove="true"/>This will remove the block from the layout and prevent it from rendering. The <remove> tag is not valid and will cause an error. The name attribute should not include the module name, as it is not part of the block name. The delete attribute is not valid and will not work.
[Layout instructions], [Remove an element]
An Adobe Commerce developer wants to remove the default Wishlist and Compare Products blocks on a category page with layered navigation Where would this modification be placed, assuming the developer only wants to make this change?
Answer(s): B
To remove the default Wishlist and Compare Products blocks on a category page with layered navigation, the developer should place the modification in the app/design/frontend/Vendor/Theme/Magento_LayeredNavigation/layout/catalog_category_view_t ype_layered.xml file. This file is specific to the category pages with layered navigation and will override the default layout file from the Magento_LayeredNavigation module. The modification should use the <referenceBlock> tag with the name attribute specifying the name of the block and the remove attribute set to true. For example:<referenceBlock name="catalog.compare.sidebar" remove="true"/> <referenceBlock name="wishlist_sidebar" remove="true"/>The app/design/frontend/Vendor/Theme/Magento_LayeredNavigation/layout/override/catalog_categor y_view_type_layered.xml file is not valid and will not work, as it is not a valid override path. The app/design/frontend/Vendor/Theme/Magento_Catalog/layout/catalog_category_view.xml file is not specific to the category pages with layered navigation and will affect all category pages.
[Layout override], [Remove an element]
An Adobe Commerce developer has created a system configuration field:Using Layout XML, how can the visibility of a block be controlled by a system configuration?
To control the visibility of a block using a system configuration, the developer should use the ifconfig attribute in the <block> tag. The ifconfig attribute should specify the path to the system configuration field that determines whether the block is visible or not. For example:<block name="block.name" template="Vendor_Module::template.phtml" ifconfig="vendor/general/enable" />This will render the block only if the vendor/general/enable system configuration field is set to true. The module/general/enable and general/module/enable paths are not valid and will not work, as they do not match the system configuration field defined in the image.
[Layout instructions], [System configuration]
An Adobe Commerce developer has been asked to add text to an email template that supports translations. Which two options would they use during their implementation? (Choose two.)
Answer(s): B,D
To add text to an email template that supports translations, the developer should use the {{trans}} directive with the text enclosed in double quotes. For example:{{trans "Lorem Ipsum is simply dummy text of the printing"}}This will render the text as it is, or translate it if a translation file is available for the current locale. If the text contains a variable, the developer should use a placeholder with a percent sign and pass the variable name as an argument. For example:{{trans "%items items" items="numItems"}}This will render the text with the value of numItems replacing the %items placeholder, or translate it if a translation file is available for the current locale. The {{translations}} directive is not valid and will not work.
[Translate email templates], [Email template syntax]
An Adobe Commerce developer wants to completely overwrite _module. less of Orange_Checkout module, in their theme. Where would the developer place the file?
Answer(s): C
To completely overwrite _module.less of Orange_Checkout module in a custom theme, the developer should place the file in the Custom/theme/Orange_Checkout/web/css/source directory. This will override the default _module.less file from the Orange_Checkout module and apply the custom styles to the theme. The Custom/theme/Orange_Checkout/frontend/web/css/_module.less and Custom/theme/web/css/source/Orange_Checkout/_module.less paths are not valid and will not work, as they do not follow the theme structure or the module naming convention.
[Theme structure], [Module naming convention]
Post your Comments and Discuss Adobe AD0-E720 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AD0-E720 content, but please register or login to continue.