Free AD0-E722 Exam Braindumps
Adobe Commerce Architect Master Questions 11–15 (page: 4)

Updated On: 9-Feb-2026

An Adobe Commerce Architect is planning to create a new action that will add gift registry items to the customer's quote.
What should the Architect do to guarantee that private content blocks are updated?

  1. Mark the controller by setting no-cache HTTP headers
  2. Invalidate the status of gift registry indexers
  3. Specify a new action in a sections.xml configuration file

Answer(s): C

Explanation:

Private content blocks are sections of the page that are specific to each customer and are not cached by the server. To update these blocks when a customer performs an action, such as adding a gift registry item to the quote, the Adobe Commerce Architect needs to specify the new action in a sections.xml configuration file. This file defines which blocks need to be updated for each action and how often they should be updated. By doing this, the Architect can ensure that the private content blocks are refreshed with the latest data from the server.


Reference:

Private content | Magento 2 Developer Documentation
Configure private content | Magento 2 Developer Documentation



An Adobe Commerce Architect needs to scope a bespoke news section for a merchants Adobe

Commerce storefront. The merchant's SEO agency requests that the following URL structure:
news/{date}/{article_url_key}, where {date} is the publication date of the article, and {article_url_key} is the URL key of the article.
The Architect scopes that a news entity type will be created. The date and URL key data will be stored against each record and autogenerated on save. The values will be able to be manually overridden.

  1. The Architect needs to manage routing this functionality and adhere to best practice.
    Which two options should the Architect consider to meet these requirements? (Choose two.)
  2. Create a standard controller route and mapping the internal URLs (such as news/article/view/id/i) to rewrites that are generated on save and then stored in the URL rewrites table.
  3. Create a custom router that runs before the standard router and matches the news portion of the URL, then looks for and loads a news article by matching the date and URL key parts of the URL
  4. Create a plugin that intercepts Magento\Framework\App\Action: :(), looks for the news portion of the URL, and if it matches, loads the relevant news article by matching the URL date and URL key parts.
  5. Create a standard controller route and an index/index controller class that loads the relevant news article by matching the URL date and URL key parts.

Answer(s): B,C

Explanation:

These two options are both valid ways to manage routing for the bespoke news section and adhere to best practice. Option B leverages the existing URL rewrite functionality of Adobe Commerce, which allows creating custom URLs for any entity type and storing them in the database. This option requires creating a standard controller route for the news entity type, such as news/article/view/id/i, where i is the news article ID. Then, on saving each news article, a rewrite rule is generated that maps the internal URL to the desired SEO-friendly URL, such as news/{date}/{article_url_key}. The rewrite rule is stored in the url_rewrite table, which is used by the standard router to match and redirect requests.
Option C involves creating a custom router class that implements \Magento\Framework\App\RouterInterface and runs before the standard router in the routing process. The custom router class can match the news portion of the URL and extract the date and URL key parts from it. Then, it can look for and load a news article that matches those values using a model or repository class. If a match is found, it can set the request parameters accordingly and dispatch the request to a controller action that renders the news article page.


Reference:

Routing | Adobe Commerce Developer Guide
URL Rewrites | Adobe Commerce Developer Guide
Custom Router | Adobe Commerce Developer Guide



An external system integrates functionality of a product catalog search using Adobe Commerce GraphQL API. The Architect creates a new attribute my_attribute in the admin panel with frontend type select-Later, the Architect sees that Productlnterf ace already has the field my_attribute, but returns an Int value. The Architect wants this field to be a new type that contains both option id and label.
To meet this requirement, an Adobe Commerce Architect creates a new module and file etc/schema.graphqls that declares as follows:



After calling command setup:upgrade, the introspection of Productlnterface field my_attribute remains Int.
What prevented the value type of field my_attribute from changing?

  1. The Magento_CatalogGraphQI module occurs later in sequence than the Magento_GraphQI module and merging output of dynamic attributes schema reader overrides types declared in schema.graphqls
  2. The fields of Productlnterface are checked during processing schema.graphqls files. If they have a corresponding attribute, then the backendjype of product attribute is set for field type.
  3. The interface Productlnterface is already declared in Magento.CatalogGraphQI module. Extending requires use of the keyword extend before a new declaration of Productlnterface.

Answer(s): C

Explanation:

According to the Adobe Commerce documentation, to extend an existing GraphQL interface, the keyword extend must be used before the interface name. This indicates that the new declaration is adding or modifying fields to the existing interface, rather than redefining it. If the keyword extend is omitted, the new declaration will be ignored and the original interface will be used. In this case, the Architect wants to change the type of the my_attribute field in the ProductInterface interface, which is already declared in the Magento.CatalogGraphQl module. Therefore, the Architect should use the keyword extend before declaring the ProductInterface interface in the schema.graphqls file of the custom module. This will allow the Architect to override the type of the my_attribute field from Int to MyAttributeType.


Reference:

Extend existing schema | Adobe Commerce Developer Guide Schema language with GraphQL | Adobe Commerce



An Adobe Commerce store owner sets up a custom customer attribute "my.attribute". An Architect needs to display additional content on the home page, which should display only to Customers with "my.attribute" of a certain value and be the same content for all of them. The website is running Full Page Cache.
With simplicity in mind, which two steps should the Architect take to implement these requirements? (Choose two.)

  1. Add a new context value of "my_attribute" to Magento\Framework\App\Http\Context
  2. Create a Customer Segment and use 'my.attribute' in the conditions
  3. Add a custom block and a pHTML template with the content to the cmsjndexjndex.xml layout
  4. Add a dynamic block with the content to the Home Page
  5. Use customer-data JS library to retrieve "my.attribute" value

Answer(s): A,D

Explanation:

To display additional content on the home page based on a custom customer attribute, the Architect needs to do the following steps:
Add a new context value of "my_attribute" to Magento\Framework\App\Http\Context. This will allow the Full Page Cache to generate different versions of the page for customers with different values of "my.attribute". The context value can be set using a plugin on the Magento\Customer\Model\Context class.
Add a dynamic block with the content to the Home Page. A dynamic block is a type of content block that can be configured to display only to specific customer segments or conditions. The Architect can use the `my.attribute' in the conditions of the dynamic block and assign it to the Home Page in the Content > Blocks section of the Admin Panel.


Reference:

Private content | Magento 2 Developer Documentation
Dynamic Blocks | Adobe Commerce 2.3 User Guide - Magento



An Adobe Commerce Architect designs a data flow that contains a new product type with its own custom pricing logic to meet a merchant requirement.
Which three steps are required when adding a product type with custom pricing? (Choose three.)

  1. Content of the etc/product_types.xml file
  2. Data patch to register the new product type
  3. Hydrator for attributes belonging to the new product type
  4. New price model extending \Magento\Catalog\Model\Product\Type\Price
  5. Custom type model extended from the abstract Product Type model
  6. A new class with custom pricing logic, extending the abstract Product model class

Answer(s): A,D,E

Explanation:

To add a product type with custom pricing, the Architect needs to do the following steps:
Create a content of the etc/product_types.xml file that defines the new product type, its label, model, index priority, and price model. This file is used to register the new product type and its associated classes in Magento1.
Create a new price model that extends \Magento\Catalog\Model\Product\Type\Price and implements the custom pricing logic for the new product type. The price model is responsible for calculating the final price of the product based on various factors, such as special price, tier price, catalog price rules, etc2.
Create a custom type model that extends from the abstract Product Type model (\Magento\Catalog\Model\Product\Type\AbstractType) and overrides the methods related to the product type behavior, such as prepareForCart, getAssociatedProducts, etc. The type model defines how the product type interacts with other components, such as quote, order, cart, etc3.


Reference:

How to add a new product type in Magento 2? (MageStackDay mystery question 1) - Magento Stack Exchange
Magento 2: How to create custom product types - BelVG Blog Magento 2: How to create custom product types - BelVG Blog



Viewing page 4 of 11
Viewing questions 16 - 20 out of 50 questions


Post your Comments and Discuss Adobe AD0-E722 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!