Adobe AD0-E718 Adobe Commerce Architect Master Exam Practice Test

Page: 1 / 14
Total 50 questions
Question 1

A company has an Adobe Commerce store. An attribute named "my.attribute" (type "text") is created to save each product's global ID that is shared between multiple systems.

Several months after going live, the values of "my.attribute" are all integer. This causes a problem for the other systems when those systems receive this data.

An Adobe Commerce Architect needs to recommend a solution to change the type of "my.attribute" from textXo int

Which two steps should the Architect take to achieve this? (Choose two.)



Answer : A, D

Option A is correct because it will migrate data from one table to another based on the attribute id, which is required when changing the attribute type14.Option D is correct because it will create a data patch that will update 'my.attribute' type from ''text'' to ''int'', which is a recommended way of changing the attribute type programmatically4.

To change the type of ''my.attribute'' from text to int, the Architect should take two steps: A) Migrate data from table ''catalog_product_entity_text'' to ''catalog_product_entity_int'' for the attribute_id. This step will move the existing values of the attribute from the text table to the int table, which corresponds to the new type. D) Create a Data Patch and update 'my.attribute' type from ''text'' to ''int''. This step will update the attribute metadata in the database and reflect the new type. Option B is incorrect because the Admin panel does not allow changing the type of an existing attribute. Option C is incorrect because writing a plugin for \Magento\Eav\Model\Entity\Attribute\Backend\AbstractBackend::afterLoad() will not change the type of the attribute, but only load data from a different table. Option E is incorrect because running the command bin/magento indexer:reset catalog_product_attribute will not change the type of the attribute, but only reset the indexer status. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/attributes.html


Question 2

An Adobe Commerce Architect is working on a scanner that will pull prices from multiple external product feeds. The Architect has a list of vendors and decides to create new config file marketplacejeeds.xml.

Which three steps can the Architect take to ensure validation of the configuration files with unique validation rules for the individual and merged files? (Choose three.)



Answer : B, C, D

To ensure validation of the configuration files with unique validation rules for the individual and merged files, you need to do the following steps:

Add the Uniform Resource Name (URN) to the XSD file in the config XML file. The URN is a unique identifier for a resource that follows a specific syntax. For example:

<config xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xsi:noNamespaceSchemaLocation='urn:magento:module:Vendor_Module:etc/marketplacefeeds.xsd'>

Provide schema to validate a merged file. The schema defines the structure and constraints of the XML document that represents the merged configuration from all modules. The schema file should be named as <config_file_name>.xsd and placed in the etc directory of the module. For example:

marketplacefeeds.xsd

Provide schema to validate an individual file. The schema defines the structure and constraints of the XML document that represents the configuration from a single module. The schema file should be named as <config_file_name>_merged.xsd and placed in the etc directory of the module. For example:

marketplacefeeds_merged.xsd


Question 3

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 Productinterface already has the field my_atcribute, but returns an mc 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 xy_attribute remains int. What prevented the value type of field my_attribute from changing?



Answer : A

According to the Adobe Commerce Developer Guide1, the fields of ProductInterface are checked during processing schema.graphqls files. If they have a corresponding attribute, then the backend_type of product attribute is set for field type. Therefore, the value type of field my_attribute remains int because it corresponds to the attribute my_attribute that has a frontend type select and a backend_type int.


Question 4

An Adobe Commerce Architect notices that the product price index takes too long to execute. The store is configured with multiple websites and dozens of customer groups.

Which two ways can the Architect shorten the full price index execution time? (Choose two.)



Answer : A, D

The two best ways the Architect can shorten the full price index execution time are Option A. Enable price index customer group merging for products without tier prices, and Option D. Set MaGEINDEXERTHREADS_COUNT environment variable to enable parallel mode. Enabling customer group merging will help reduce the number of customer groups that need to be processed, while setting the environment variable will allow the indexer to use multiple threads and run in parallel mode, thus reducing the overall execution time.

Enabling price index customer group merging allows Magento to merge the price index rows for products that have the same price for all customer groups. This reduces the number of rows in the price index table and improves the performance of the indexer. Setting the MaGE_INDEXER_THREADS_COUNT environment variable allows Magento to run the indexer in parallel mode, which splits the index into multiple batches and processes them simultaneously. This reduces the execution time of the indexer. Reference: https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#customer-group-merging https://devdocs.magento.com/guides/v2.4/extension-dev-guide/indexing.html#parallel-mode


Question 5

An Adobe Commerce Architect is asked by a merchant using B2B features to help with a configuration issue.

The Architect creates a test Company Account and wants to create Approval Rules for orders. The Approval Rules tab does not appear in the Company section in the Customer Account Menu when the Architect logs in using the Company Administrator account.

Which two steps must be taken to fix this issue? (Choose two.)



Answer : A, C

Enabling Purchase Orders at both the B2B Admin and the Company Record levels is necessary for Approval Rules to appear in the Company section of the Customer Account Menu. When 'Enable Purchase Orders' is set to TRUE, the system assumes that the company will be making purchases using purchase orders, and the Approval Rules tab becomes visible.

To create Approval Rules for orders, the Architect needs to enable Purchase Orders both in the B2B Admin and on the Company Record. This will allow the Company Administrator to access the Approval Rules tab in the Customer Account Menu and create rules based on various criteria. The Purchase Order payment method and the B2B Quote feature are not required for this functionality. Reference: https://docs.magento.com/user-guide/customers/account-dashboard-approval-rules.html


Question 6

An Adobe Commerce Architect needs to create a new customer segment condition to enable admins to specify an 'Average sales amount' condition for certain segments.

The Architect develops the custom condition under vendor\Module\Model\Segment\condition\AverageSalesAmount with all of its requirements:

Which two steps should the Architect complete to fix the problem? (Choose two.)

A)

B)

C)

D)

E)



Answer : B, E

According to the Adobe Commerce Developer Guide1, to create a new customer segment condition, the custom condition class must implement the Magento\CustomerSegment\Model\Segment\Condition\Combine\Interface interface. The class must also have a constructor that accepts an array of data and a context object that contains the required dependencies. Therefore, option B is correct because the constructor is missing the context object parameter. Option E is also correct because the class does not implement the required interface. The other options are not relevant for this problem.


Question 7

An Architect working on a headless Adobe Commerce project creates a new customer attribute named my_attribure. Based on the attribute value of the customer, the results of GraphQI queries are modified using a plugin. The frontend application is communicating with Adobe Commerce through Varnish by Fastly, which is already caching the queries that will be modified. The Adobe Commerce Fastly extension is installed, and no other modifications are made to the application.

Which steps should the Architect take to make sure the vcl_hash function of Varnish also considers the newly created attribute?

A)

B)

C)



Answer : B

Option B is the correct way to make sure the vcl_hash function of Varnish also considers the newly created attribute. The Architect should create a new module that depends on Magento_Fastly and declare a plugin for \Magento\Fastly\Model\Config::getVclSnippets() method. The plugin should add a new snippet to the result array with the type 'recv' and the content 'set req.http.my_attribute = req.http.X-Magento-Vary;'. This will append the value of the customer attribute to the hash key used by Varnish for caching. Option A is incorrect because it modifies the core file of Magento_Fastly module, which is not recommended and can cause issues during upgrades. Option C is incorrect because it uses the wrong type and content for the snippet, which will not affect the vcl_hash function. Reference: https://devdocs.magento.com/cloud/cdn/fastly-vcl-bypass-to-origin.html

According to the Adobe Commerce Developer Guide2, to make sure the vcl_hash function of Varnish also considers the newly created attribute, the Architect should use a plugin for Magento\Customer\Model\Context::getVaryString method and add the attribute value to the vary string. This will ensure that Varnish caches different versions of GraphQL queries based on the attribute value of the customer. Therefore, option B is correct. Option A is not correct because it does not affect the vcl_hash function. Option C is not correct because it does not use a plugin for the getVaryString method.


Page:    1 / 14   
Total 50 questions