Which two steps are required to delete a manually installed theme? (Choose two.)
Answer : B, D
To delete a manually installed theme, the developer needs to remove the theme directory from the app/design/frontend directory and also delete the corresponding record from the theme table in the database. The theme:uninstall CLI command is only used for deleting themes that are installed as Composer packages. Disabling the theme from the backend admin configuration does not delete the theme files or records, but only makes it unavailable for use. Reference: [Delete a theme], [theme:uninstall]
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 : 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. Reference: [Theme structure], [Module naming convention]
An Adobe Commerce developer needs to add CMS content above products on a specific category page via the Admin Panel. Where would the developer need to put the content in order to use Display Modes functionality and display it on the category?
An Adobe commerce developer wants to initialize a JavaScript component using a data attribute. Which option would initialize the JavaScript component?
Answer : C
To initialize a JavaScript component using a data attribute, the developer should use the data-mage-init attribute. This attribute allows the developer to specify the name and configuration of the component in a JSON format. For example:
<nav data-mage-init='{''Vendor_Module/js/nav'': {''option1'': ''value1'', ''option2'': ''value2''}}'></nav>
This will initialize the nav component from the Vendor_Module/js/nav file with the given options. The data-bind and data-init attributes are not valid and will not work, as they are not supported by Magento. Reference: [JavaScript initialization], [data-mage-init]
An Adobe Commerce developer has just installed an extension via composer. When running, bin/magento module: status Vendor_Module, the status is returned as Module is disabled.
Which two CLI commands need to be run to make the extension work properly? (Choose two.)
Answer : B, D
The developer needs to run these two CLI commands to make the extension work properly:
bin/magento module:enable Vendor_Module --clear-static-content This command enables the extension and clears any outdated static files that might interfere with its functionality.
bin/magento setup:upgrade This command updates the database schema and data according to the extension's requirements. The other two options are incorrect because they are not necessary to make the extension work properly. The composer install command installs all dependencies specified in the composer.json file, but it does not enable or update any extensions. The composer update vendor/module command updates an existing extension to its latest version, but it does not enable or upgrade it.
An Adobe Commerce developer is implementing a sticky sidebar using a jQuery widget. How would the developer initialize the block in a JavaScript file?
A)
C)
Answer : C
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://developer.adobe.com/commerce/docs/
Which Ul component property is used for cross tracking property changes?
Answer : B
The listens property is used for cross tracking property changes in the UI component. The listens property defines the dependencies between the properties of different UI components. It allows one UI component to listen to the changes of another UI component's property and react accordingly. For example, the listens property can be used to update the value of a text field based on the selection of a dropdown menu