Which two steps should the Architect make to meet this requirement?

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.)
A . Write a plugin for MagentoFrameworkConfigData::get() and read the custom xml files
B. Append the custom xml file name in "MagentoConfigModelConfigStructureReader" in di.xml
C. Create a Data class that implements "MagentoFrameworkConfigData’
D. Inject a "reader" dependency for "MagentoFrameworkConfigData" in di.xml
E. Make a Reader class that implements "MagentoFrameworkConfigReaderFilesystem"

Answer: C,E

Explanation:

Based on web searches, it seems that Magento uses different classes and interfaces to interact with configuration files, such as Data, Reader, and Converter12. According to the documentation1, 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:

✑ C. Create a Data class that implements “MagentoFrameworkConfigData”

✑ E. Make a Reader class that implements

“MagentoFrameworkConfigReaderFilesystem”

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.

Latest AD0-E718 Dumps Valid Version with 50 Q&As

Latest And Valid Q&A | Instant Download | Once Fail, Full Refund

Subscribe
Notify of
guest
0 Comments
Inline Feedbacks
View all comments