Adobe Commerce Developer Professional AD0-E717 Exam Questions

Answer : B

The Discard Subsequent Rules option is only applied if the pricing rules have different priorities. If two pricing rules have the same priority, the discount from both rules will be applied.

For the 'Discard Subsequent Rules' option set to 'Yes' to work effectively, each pricing rule must have a defined priority. When multiple discount rules can apply to the same product, Magento evaluates them in the order of their priority values. If a rule with 'Discard Subsequent Rules' set to 'Yes' is applied, any subsequent rules with lower priority (higher priority number) will not be applied to that product.

Answer : A

The type of product that would assist a seller in offering an electronic version of an album and selling each song individually is a Downloadable product. In Adobe Commerce, a Downloadable product type is specifically designed for selling digital products such as music files, which customers can download. This type of product allows sellers to upload individual songs and sell them separately or as part of a complete album.

Answer : C

In Magento, plugins (Interceptors) can only intercept public methods. This is because the plugin system relies on Magento's object manager to dynamically create proxy classes that can intercept method calls. Since private and final methods are not accessible from outside the class they are defined in, and static methods are not called on an object instance, these method types cannot be intercepted. This mechanism allows for the extension and customization of Magento's core behavior in a transparent and non-intrusive manner.

Answer : C

When renaming a table in Magento, to prevent data loss, the developer must define the table and its columns mapping in the db_schema_whitelist.json file. This declarative schema approach ensures that the data migration tool knows about the changes and can migrate data from the old table to the newly named table without losing any data.

Answer : C

To set a custom CMS Page as a store home page, the developer or merchant should follow these steps:

In the Admin panel, go to Content > Pages and create or edit a CMS Page that will be used as a home page.

In the Admin panel, go to Stores > Configuration > General > Web > Default Pages.

In the CMS Home Page field, select the CMS Page that was created or edited in step 1.

Save the configuration.

There is no ''Home Page'' column in the CMS Page admin grid or ''Default Home Page'' value in the CMS Page admin form.

Verified Reference: [Adobe Commerce User Guide - Set up your home page]

In Adobe Commerce, to set a custom CMS page as the store's homepage, you need to go to the store configuration. Specifically, navigate to Content > Design > Configuration, select the relevant store view, and then under the 'Default Pages' tab, set the 'CMS Home Page' option to your custom CMS page. Options A and B do not exist in the Adobe Commerce admin panel for setting a home page.

Answer : A, B

The two attribute input types that Adobe Commerce already has by default are Multiple Select and Text Field. Multiple Select allows the user to select multiple values from a list of options. Text Field allows the user to enter text in a single line.

The Geographic coordinate and Numeric Field input types do not exist in Adobe Commerce.

Verified Reference: [Adobe Commerce User Guide - Create a product attribute]

Magento, by default, provides various attribute input types to accommodate different data entry needs for product and customer attributes. The 'Text Field' input type allows for single-line text input, suitable for short, textual data such as names, titles, or any other brief information. The 'Multiple Select' input type enables the selection of multiple options from a predefined list, useful for attributes with multiple applicable values like colors, sizes, or features. These input types are part of Magento's flexible attribute system, allowing for customizable data entry fields that cater to diverse product and customer data requirements.

Answer : A, D

By default, third-party modules are located in vendor/ or app/code/ directories. The vendor/ directory contains modules that are installed using Composer, while the app/code/ directory contains modules that are manually copied or cloned from a repository.

Third-party modules in Magento 2 are typically located in two directories by default: the vendor/ directory and the app/code/ directory. The vendor/ directory is used for modules that are installed via Composer, Magento's dependency manager, which includes both Magento's core modules and third-party modules. The app/code/ directory is used for custom modules developed specifically for the project or for third-party modules that are manually installed without Composer. These conventions provide a structured approach to managing Magento modules, whether they are part of Magento's core functionality, contributed by the community, or developed for specific projects.