AD0-E718 Adobe Commerce Architect Master - Practice Questions

Question 1

In a custom module, an Architect wants to define a new xml configuration file. The module should be able to read all the xml configuration files declared in the system, merge them together, and use their values in PHP class.

Which two steps should the Architect make to meet this requirement? (Choose two.)

Select all that apply, then click Submit answer.

○
Write a plugin for \Magento\Framework\Config\Data::get() and read the custom xml files
○
Append the custom xml file name in "Magento\Config\Model\Config\Structure\Reader" in di.xml
○
Create a Data class that implements "\Magento\Framework\Config\Data'
○
Inject a "reader" dependency for "Magento\Framework\Config\Data" in di.xml
○
Make a Reader class that implements "\Magento\Framework\Config\Reader\Filesystem"

Reference / correct answer:

Create a Data class that implements "\Magento\Framework\Config\Data'

Make a Reader class that implements "\Magento\Framework\Config\Reader\Filesystem"

Based on web searches, it seems that Magento uses different classes and interfaces to interact with configuration files, such as Data, Reader, and Converter 1 2.

According to the documentation 1, Data is a class that provides access to configuration data using a scope. Reader is an interface that reads configuration data from XML files. Converter is an interface that converts XML data into an array representation.

Based on these definitions, I would say that two possible steps that the Architect should make to meet the requirement are:

These steps would allow the custom module to read all the XML configuration files declared in the system, merge them together, and use their values in PHP class.

The Architect should make two steps to meet this requirement: C) Create a Data class that implements “\Magento\Framework\Config\Data”. This class will be responsible for reading and merging the custom xml configuration files and providing access to their values. The Data class should extend \Magento\Framework\Config\Data and use the constructor to inject the Reader class and the cache type. E) Make a Reader class that implements “\Magento\Framework\Config\Reader\Filesystem”. This class will be responsible for loading and validating the custom xml configuration files from different modules. The Reader class should extend \Magento\Framework\Config\Reader\Filesystem and use the constructor to specify the file name, schema file, and validation state of the custom xml configuration files. Option A is incorrect because writing a plugin for \Magento\Framework\Config\Data::get() will not define a new xml configuration file, but rather modify the existing one. Option B is incorrect because appending the custom xml file name in “Magento\Config\Model\Config\Structure\Reader” in di.xml will not define a new xml configuration file, but rather add it to the system configuration structure. Option D is incorrect because injecting a “reader” dependency for “Magento\Framework\Config\Data” in di.xml will not define a new xml configuration file, but rather use an existing one. References: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/build/XSD-XML-validation.html

Question 2

A developer needs to uninstall two custom modules as well as the database data and schemas. The developer uses the following command:

bin/magento module:uninstall Vendor_SampleMinimal Vendor_SampleModifyContent

When the command is run from CLI, the developer fails to remove the database schema and data defined in the module Uninstall class.

Which three requirements should the Architect recommend be checked to troubleshoot this issue? (Choose three.)

Select all that apply, then click Submit answer.

○
remove-schema and --remove-data options are specified as arguments for the CLI command
○
bin/magento maintenance: enable command should be run in CLI before
○
composer.json file is present and defines the module as a composer package
○
Invoke uninstallData() and uninstallSchema () are defined in the Uninstall class
○
--remove-data option is specified as an argument for the CLI command
○
invoked uninstall () method is implemented in the Uninstall class

Reference / correct answer:

remove-schema and --remove-data options are specified as arguments for the CLI command

Invoke uninstallData() and uninstallSchema () are defined in the Uninstall class

--remove-data option is specified as an argument for the CLI command

To troubleshoot the issue of failing to remove the database schema and data using the bin/magento module:uninstall command, the following requirements should be checked: A. Check if the remove-schema and --remove-data options are specified as arguments for the CLI command. These options will remove the schema and data for the specified module. D. Confirm that the uninstallData() and uninstallSchema() methods exist in the Uninstall class. These methods are responsible for removing the database schema and data. E. Check if the --remove-data option is specified as an argument for the CLI command. This option will remove the data for the specified module.

Question 3

An Adobe Commerce system is configured to run in a multi-tier architecture that includes:

• A cache server with Varnish installed

• A backend web server with Adobe Commerce installed

• A database server with MySQL installed

When an Adobe Commerce Architect tries to clean the cache from the Store Admin by using the "Flush Magento Cache" in Cache Management, the Full Page Cache does not clear.

Which two steps should the Architect take to make the Full Page Cache work properly? (Choose two.)

Select all that apply, then click Submit answer.

○
Set the backend destination host to the frontend server's address in the Store Admin
Stores > Configuration > Advanced > System > Full Page Cache > Varnish Configuration > Backend Host
○
Set the backend port destination to the frontend server's Varnish port in the Store Admin
Stores > Configuration > Advanced > System > Full Page Cache > Varnish Configuration > Backend Port
○
Set the cache type to "Varnish Caching" in the Store Admin.
Stores > Configuration > Advanced > System > Full Page Cache > Caching Application
○
Use "Flush Cache Storage" instead of "Flush Magento Cache"
○
Set the cache destination host using magento CLI bin/magento setup:config:set --http-cache-hosts:

AD0-E718 – Adobe Commerce Architect Master