Question 1

An Adobe Commerce developer added a new API method to search and retrieve a list of Posts for a custom Blog functionality. This is the content of the module's etc/webapi.xml file:

The new code has been deployed to production and the merchant is using https: //merchant.domain.com/swagger to review the new endpoint, but it is not visible in swagger.

What would be a reason for this?

ASince the new endpoint is not anonymous, the merchant needs to enter a valid integration token in swagger in order to see the new method.

BThe webapi.xml file should be moved into the etc/webapi_rest/webapi.xml file.

CThe @return annotation is missing in the MyVendor\Blog\Api\Post Repositoryinterfacec

Answer : B

Question 2

An Adobe Commerce developer has created a before plugin for the save() function within the magento\Framework\App\Cache\Proxy class. The purpose of this plugin is to add a prefix on all cache identifiers that fulfill certain criteria.

Why is the plugin not executing as expected?

AAnother around ptugm defined for the same function does not call the callable .

BCache identifiers are immutable and cannot be changed.

CThe target class implements Magento\frameworK\ObjectManager\Nointerceptablelnterface .

Answer : C

Question 3

A message queue currently has queue/consumer-wait-for-messages set to true, which allows the consumer process to run until a message is inserted into the queue. A piece of functionality is driven by data stored in the model. \Magento\Variable\\Model\variable and this value is only loaded once during the consumer run. If the variable is updated we want the consumer to restart so that the new value is loaded into memory without having to reload the variable on each message consumed.

The Adobe Commerce developer has created an after plugin on the \Magento\variable\variable::save() function.

How would the developer use the plugin to trigger the consumer restart?

ASet the global cache key trigger_consumer_resart to 1.

BCall the function \Magento\FrameWork\MessageQueue\Constomers triggerRest art Interface: trigger () .

CCall the function \Magento\Framework\MessageQueue\Poison\PillPoisoninterface::put() .

Answer : A

Question 4

An Adobe Commerce developer is working on an Acme_Exceptions module which is supposed to overwrite logic inside some of Magento native exceptions such as \Magento\Frame-work\Exception\NoSuchEntityException or \Mogento\Framwork\GraphQ1\Exception\GrephQlInputException , The module is open-source and will be available on packagist.org.

The build of the codebase of projects, including the module, will sometimes take place in docker containers with full access to filesystem. but then it is deployed to a read-only filesystem.

Which two approaches would the developer use to overwrite logic in those exceptions? (Choose two.)

A1. Create a version of those exceptions inside the module using the original namespaces and classes, e.g. \Magento\Framewrk\Exception\NoSuchEntityException .
2. Use composer's extra > nap node to copy those exceptions to their original destinations like vendor/Magento/framework/exception/ to replace original files.

B1. Create a version of those exceptions inside the module using new namespace, e.g.
\Acme\Exceptions\Exception\NoSuchEntityException .
2. Create a di.xmi file inside of the module and use to make the system use own versions instead of native versions.

C1. Create a version of those exceptions inside the module using the original namespaces and Classes, e.g. \Magento\Framework\Exceptioin\NoSuchEntityException .
2. Use composer's scripts > post-install-and and scripts > post-update-cmd nodes to copy those exceptions to their original destinations like

D1. Create a version of Those exceptions inside the module using the original namespaces and classes, e.g. \Magento\Framework\Exception\NoSuchEntityException .
2. Create a data patch copying those exceptions to their original destinations like vendor/magento/ framework /except Ion/ to replace original files.

Answer : A, B

Question 5

An Adobe Commerce developer adds a new extension attribute to add an array of values to the invoices that are fetched through the APIs.

After a while, their technical manager reviews their work and notices something wrong with the extension_attributes.xml file that the developer created in their module: extension_attributes for="Magento\Sales\Hotel\Order\InvoiceRepository"> attribute code"my_code" type=string]''> What is the problem with this xml snippet?

AThe extension attribute references the repository instead of the interface it implements
(Magento\Sales\Api\invoiceRepositoryinteface

BThe type is wrong, string[] should be replaced with array.

CThe extension attribute references the wrong interface it should have referenced the Magento\Sales\APi\Invoiceinterface.