About the Exam

Adobe Commerce Architect Master is Adobe's master-level certification for professionals who lead Adobe Commerce development projects and design, integrate, implement, and troubleshoot commerce solutions. It is aimed at experienced candidates in roles such as lead software architect, technical architect, solution architect, technical lead, and senior backend developer. Passing demonstrates the ability to design optimal Adobe Commerce solutions, review and refactor customizations, and configure and deploy commerce projects.

Exam Topics

  • Design and implement optimal solutions for Adobe Commerce to meet business needs0%
  • Configure all aspects of Adobe Commerce Cloud0%
  • Troubleshoot to identify the root cause of issues with Adobe Commerce0%
  • Troubleshoot design flows0%
  • Configure and Deploy0%
  • Enforce coding standards0%
  • Troubleshoot infrastructure and configuration issues0%
  • Utilize Commerce test frameworks throughout the whole workflow0%
  • Customize Commerce features0%

How to Use This Practice Exam

  1. Browse — Read each question, select your answer, and reveal the explanation.
  2. Exam Mode — Simulate real exam conditions with a timed session and score report.
  3. Learn Mode — Spaced repetition schedules questions you struggle with for long-term retention.

Download the Full Exam PDF

Get every question and answer in a clean, printable PDF built for offline study. Purchase once, keep permanent access, and re-download the latest version anytime.

Last updated November 9, 2025 at 9:21 PM

Topic filter
Retired questions
Question sort

QuestionQ1

Customize Commerce features

Within a custom module, an Architect needs to define a new XML configuration file. The module must be able to read every XML configuration file declared in the system, merge them, and use their values in a PHP class.

Which two steps should the Architect take to satisfy this requirement?

Choose two
  • A Inject a “reader” dependency for “Magento\Framework\Config\Data” in di.xml
  • B Write a plugin for \Magento\Framework\Config\Data::get() and read the custom xml files
  • C Create a Data class that implements “\Magento\Framework\Config\Data”
  • D Append the custom xml file name in “Magento\Config\Model\Config\Structure\Reader” in di.xml
  • E Make a Reader class that implements “\Magento\Framework\Config\Reader\Filesystem”
Explanation

Magento’s configuration framework uses a filesystem-based configuration reader to collect and merge a named XML configuration file from registered modules. Magento\Framework\Config\Data consumes that reader through dependency injection and provides the merged configuration values to PHP code. The system-configuration structure reader is for Admin configuration metadata, not a general custom XML configuration format. Commerce framework

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ2

Configure all aspects of Adobe Commerce Cloud

A third-party company needs to build an application that integrates with the Adobe Commerce system to retrieve order data for reporting. The integration requires access to the GET /V1/orders endpoint. It will invoke this endpoint automatically every hour, around the clock. The merchant wants to be able to restrict or expand access to resources and revoke that access through the Admin Panel.

Which authentication type available in Adobe Commerce should be used and implemented in the third-party system for this integration?

  • A Use token-based authentication to obtain the Admin Token. The third-party system will utilize the REST endpoint using the admin username and password to get the Admin Token, which will be used as the Bearer Token to authorize.
  • B Use token-based authentication to obtain an Integration Token. Integration will be created and activated in the admin panel using default integration token settings to get access to the token, which will be used as the Bearer Token to authorize.
  • C Use OAuth-based authentication to provide access to system resources. Integration will be registered by the merchant in the admin panel with an OAuth handshake during activation. The third-party system should follow OAuth protocol to authorize.
Explanation

Adobe Commerce uses OAuth 1.0a integrations for third-party applications. An integration is created and authorized in Admin, where the merchant can grant all or a custom subset of API resources, change authorization, or revoke the integration. OAuth requests use the integration’s OAuth credentials and signed Authorization header rather than treating an integration token as a standalone Bearer token. Adobe Commerce OAuth-based authentication

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ3

Customize Commerce features

An Adobe Commerce Architect creates an Italian-locale stopword named stopwordsJtJT.csv and changes the stopword directory to:

<magento_root>/app/code/CustomVendor/Elasticsearch/etc/stopwords/

What is the correct way to change the stopwords directory within the custom module?

  • A Add stopwords to the stopwordsDirectory and CustomVendor_Elasticsearch to the stopwordsModule parameter of the \Magento\Elasticsearch\SearchAdapter\Query\Preprocessor\Stopwords class via di.xml
  • B Add a new class implementing \Magento\Framework\Setup\Patch\PatchInterface to modify the default Value of elasticsearch\custom\stopwordspath in core_config_data table.
  • C Add stopwords to the stopwordsDirectory parameter of the \Magento\Elasticsearch\Model\Adapter\Document\DirectoryBuilder class via stopwords/it.xml and Adobe Commerce will automatically detect the current module.
Explanation

Adobe Commerce configures custom-module stopwords through etc/di.xml for \Magento\Elasticsearch\SearchAdapter\Query\Preprocessor\Stopwords. Set stopwordsModule to CustomVendor_Elasticsearch and stopwordsDirectory to stopwords; the module-relative directory resolves to etc/stopwords, where the locale CSV file belongs.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ4

Design and implement optimal solutions for Adobe Commerce to meet business needs

While reviewing a newly created pull request that refactors several custom payment methods, the Architect observes that multiple classes rely on \Magento\Framework\Encryption\EncryptorInterface to decrypt sensitive credential data. The commonly duplicated code is:

Question Image

In every module, the user_secret configuration is declared as follows:

Question Image

The Architect must recommend an optimal approach to eliminate redundant dependencies and duplicated code across the methods.

Which solution should the Architect recommend?

  • A Create a common config service class Vendor\Payment\Gateway\Config\Config under Vendor_Payment and use it as a parent class for all of the Vendor\PaymentModule\Gateway\Config\Config classes and remove $scopeConfig and $encryptor dependencies
  • B Replace all Vendor\PaymentModule\Gateway\Config\Config classes with virtualType of Magento\Payment\Gateway\Config\Config and set <user_secret backend_model=“Magento\Config\Model\Config\Backend\Encrypted” /> under config.xml
  • C Add a plugin after the getValue method of $scopeConfig, remove the $encryptor from dependency and use it in the plugin to decrypt the value if the config name is ‘user_secret’
Explanation

A shared payment gateway configuration base class centralizes retrieval and decryption of the encrypted user_secret. Its payment-method-specific subclasses inherit that behavior and no longer need to declare the repeated scope-config and encryptor dependencies themselves. A virtual type of the generic payment config class does not implement secret decryption, and a plugin on the general configuration getter would apply cross-cutting behavior based on a generic field name rather than encapsulating the payment configuration concern.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

QuestionQ5

Design and implement optimal solutions for Adobe Commerce to meet business needs

An Adobe Commerce store owner creates a custom customer attribute, my_attribute.

An Architect must show additional content on the home page only to customers whose my_attribute has a specified value; the content must be identical for all such customers. The website uses Full Page Cache.

With simplicity in mind, which two steps should the Architect take to implement these requirements?

Choose two
  • A Add a new context value of “my.attribute” to Magento\Framework\App\Http\Context
  • B Create a Customer Segment and use “my_attribute” in the conditions
  • C Add a custom block and a pHTML template with the content to the cmsjndexjndex.xml layout
  • D Add a dynamic block with the content to the Home Page
  • E Use customer-data JS library to retrieve “my_attribute” value
Explanation

Customer Segments can target registered customers using customer-account attributes, provided the attribute is enabled for use in customer-segment conditions. A Dynamic Block can be associated with that segment to determine which customers see its content, and it can be inserted into the home page through Page Builder. This provides the required targeted, shared content without custom cache-context or JavaScript implementation.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!

That's the end of the preview

It's free

100% of the questions are free for all users.
No strings attached.

Topics covered
Design and implement optimal solutions for Adobe Commerce to meet business needsConfigure all aspects of Adobe Commerce CloudTroubleshoot to identify the root cause of issues with Adobe CommerceTroubleshoot design flowsConfigure and DeployEnforce coding standardsTroubleshoot infrastructure and configuration issuesUtilize Commerce test frameworks throughout the whole workflowCustomize Commerce features
Know a question that should be here? Contribute to this exam
Back home