AD0-E720 Practice Questions

To remove a block using layout XML, the developer should use the tag with the

name attribute specifying the name of the block and the remove attribute set to true. For example:

This will remove the block from the layout and prevent it from rendering. The 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. Reference: [Layout

instructions], [Remove an element]

Option C is the correct way to implement the viewport button icon. The image node specifies the

path to the .svg file relative to the web/css directory of the module. Option A is incorrect because

there is no icon node in the viewport configuration data. Option B is incorrect because there is no

button-image node in the viewport configuration data. Option D is incorrect because the image node

value

should

not

include

the

web/css

part

of

the

path.

https://api.flutter.dev/flutter/widgets/PageView-class.html

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. Reference:

[Theme structure], [Module naming convention]

After compiling the .less file into a .css file, the result of the code above will be option B. This is

because the .less file uses a mixin called .animation() that takes two parameters: the name of the

animation and the duration. The mixin defines a set of vendor-prefixed properties for the animation

and assigns them the values of the parameters. For example:

.animation(@name; @duration) { -webkit-animation-name: @name; -webkit-animation-duration:

@duration; -moz-animation-name: @name; -moz-animation-duration: @duration; animation-name:

@name; animation-duration: @duration; }

When the mixin is called with the values “fade” and “2s”, it will generate the following CSS code:

-webkit-animation-name: fade; -webkit-animation-duration: 2s; -moz-animation-name: fade; -moz-

animation-duration: 2s; animation-name: fade; animation-duration: 2s;

Option A is not correct because it does not use the vendor prefixes for the animation properties.

Option C is not correct because it uses the wrong values for the animation name and duration.

Reference: [LESS Mixins], [CSS Animations]

To apply a knockout binding to a

to run a function, onClick(), when it’s clicked, the developer can use either of the following solutions: A. : This solution will use the click binding to execute the onClick() function as an expression when the

is clicked. The function will be called with the current binding context as the first parameter and the event object as the second parameter. C. : This solution will use the click binding to execute the onClick function as a reference when the

is clicked. The function will be called with the current binding context as the first parameter and the event object as the second parameter. The following solutions are not valid and will not work: B.

: This solution will use the virtual element syntax to apply the click binding, but it will pass a string literal instead of a function expression or reference. This will cause an error, as the click binding expects a function value. D. : This solution will use a custom attribute instead of a data-bind attribute to apply the click binding. This is not supported by knockout and will not have any effect.

To modify the width and height of all product images inside a theme, the developer needs to edit the

view.xml file inside the etc directory of the theme. The view.xml file contains the configuration for

the theme’s images, fonts, and layout. The images.xml file does not exist by default and is not used

for configuring images. The theme.xml file is used for specifying the parent theme and other

metadata of the theme. Reference: [view.xml], [theme.xml]

Option C is the correct way to initialize a jQuery widget in a JavaScript file. The widget name should

be prefixed with “mage” and the options should be passed as an object literal. Option A is incorrect

because it uses a dot notation instead of a colon to separate the widget name and the options.

Option B is incorrect because it uses a string instead of an object literal to pass the options.

https://experienceleague.adobe.com/docs/certification/program/technical-certifications/ac/acexpert/ac-e-fedeveloper0623.html?lang=en

https://developer.adobe.com/commerce/docs/

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 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. Reference:

[Layout override], [Remove an element]

To

find

the

default

values

for

the

buttons,

the

developer

needs

to

look

at

the

lib/web/css/source/lib/_buttons.less file. This file contains various variables, mixins, and styles for

defining and customizing buttons. The developer can override these values in their custom theme by

using the .lib-button() mixin or by creating their own mixins or classes. For example:

.lib-button( @_button-selector, @_button-type, @_button-shape, @_button-color, @_button-

background, @_button-border, @_button-text-transform, @_button-box-shadow, @_button-hover-

color, @_button-hover-background, @_button-hover-border, @_button-hover-box-shadow );

The lib/web/less/source/lib/_buttons.less and lib/web/css/source/lib/_button.less files are not valid

and do not exist. Reference: [Buttons], [Magento UI library]

To override a layout XML file from a parent theme, the developer just needs to place the modified

file in the same path relative to the layout directory of the child theme. In this case, the file would be

app/design/frontend/ExampleCorp/orange/Vendor_Module/layout/catalog_product_view.xml. The

override directory is not used for overriding layout files, but for overriding templates and web assets.

Reference: [Layout instructions], [Override templates and layout files]