AD0-E717 Practice Questions

To define a class as transient in Magento's di.xml, the correct approach is to set the shared attribute to "false" for that class. This tells Magento's object manager not to use the singleton pattern for this class, meaning a new instance will be created each time the class is requested. This is particularly useful for classes that should not maintain state across different areas of the application or during a single request lifecycle​​.

The customer data JS library is used to store private customer data in local storage. This data can be

used to improve the customer's experience on the store, such as by remembering their shipping

address or their preferred payment method.

The customer data JS library in Adobe Commerce is used for managing customer data on the client

side, such as the shopping cart, comparison list, and wishlist. It does not store sensitive information

like credit card details or usernames and passwords. Instead, it utilizes local storage to keep a private

data section where customer-specific data is stored securely and accessed via JavaScript, making

option B correct.

On an Adobe Commerce Cloud project, a custom patch should be placed in the m2-hotfixes/

directory to have it automatically applied during the build phase. The patches in this directory are

applied in alphabetical order and can be used to apply quick fixes to the code that will be included in

the build artifact.

The Cloud Project Portal (Onboarding UI) of an Adobe Commerce Cloud project is a web interface

that allows you to perform various actions related to your project, such as creating and managing

environments, deploying code, configuring services, and adding users1. One of the actions that you

can perform from the Cloud Project Portal is adding a Technical Admin, which is a user role that has

full access to all environments and can perform any action on the project2. To add a Technical Admin

from the Cloud Project Portal, you need to follow these steps2:

Log in to the Cloud Project Portal with your Magento account credentials.

Click on the Users tab on the left sidebar.

Click on the Add User button on the top right corner.

Enter the email address of the user you want to add as a Technical Admin.

Select the Technical Admin role from the Role dropdown menu.

Click on the Send Invitation button.

The user will receive an email invitation to join your project as a Technical Admin. They will need to

accept the invitation and set up their account before they can access your project2.

The database engine that is part of the infrastructure of Adobe Commerce Cloud projects is MariaDB.

MariaDB is a fork of MySQL that offers improved performance, scalability, and security features.

The database engine that is part of the infrastructure of Adobe Commerce Cloud projects is MariaDB.

Adobe Commerce Cloud is configured to use MariaDB, which is a binary drop-in replacement for

MySQL and is chosen for its performance, reliability, and feature set.

In Magento, the default store ID for the admin panel is 0. This is used as a fallback mechanism where,

if the current store view's ID is not 0, Magento automatically adds 0 as a fallback. This ensures that

the admin panel has a unique identifier, differentiating it from the frontend store views, which

typically start with IDs higher than 0. This setup is crucial for Magento's multi-store architecture,

allowing for distinct configurations and behaviors between the admin and frontend contexts​​.

The Pub/ directory is the recommended webroot for the web server in Magento. This is because it

contains all of the static content that is used by the Magento store, such as images, CSS, and

JavaScript files.

The recommended webroot for the web server in a Magento project is the pub/ directory. This

directory is used to access Magento static files and is the safer option for webroot as it minimizes

security risks by not exposing the entire application structure to the web​​.

The pub/ directory in Magento is designed to be the root directory for web servers. This design

choice is intended to enhance security and efficiency by serving static files directly from this location,

thereby reducing the need for PHP processing for these files. By setting the webroot to pub/, it

ensures that only the necessary files are publicly accessible, protecting the application's core code

and structure from external access. This setup is a recommended best practice in Magento

development for maintaining a secure and well-organized file system structure​​.

If a developer wants to allow the removal of columns from the database when deleting them from

db.schema.xml, they need to define the removable columns in the db_schema_whitelist.json file.

This file will tell Magento which columns can be removed from the database.

To allow columns to be removed from the database when they are deleted from db_schema.xml,

they must be listed in the db_schema_whitelist.json file. This file acts as a reference for which

database schema elements are safe to modify or delete, providing a safeguard against unintentional

data loss during schema updates.

The

two

methods

that

add

sorting

to

collections

inherited

from

the

\Magento\Framework\Model\ResourceModel\Db\Collection\AbstractCollection class are setOrder

and addOrder. These methods allow adding one or more order clauses to a collection query.

The setSorting and addSorting methods do not exist in Adobe Commerce.

Verified Reference: [Adobe Commerce Developer Guide - Collections]

In

Magento

2,

collections

inherited

from

\Magento\Framework\Model\ResourceModel\Db\Collection\AbstractCollection class can be sorted

using the setOrder and addOrder methods. The setOrder method is used to set the order for a field in

the collection, specifying the field by which to sort and the direction of the sorting (ASC or DESC).

The addOrder method is similar but allows for adding multiple sorting orders to the collection,

enabling more complex sorting scenarios. There are no setSorting or addSorting methods in the

standard Magento 2 collection classes.

A widget is a CMS content element that can be used to display dynamic content on a page. Widgets

can be used to display things like product reviews, social media feeds, or even custom content.

In Adobe Commerce, widgets are a correct CMS content element. Widgets allow merchants to add

dynamic data or content blocks to CMS pages, static blocks, and various other locations throughout

the store's layout without needing to directly edit the site's code. Options B (Sheet) and C (Image) are

not recognized CMS content elements in the context of Adobe Commerce's terminology, making

option A the correct answer.