Free Adobe Commerce Developer with Cloud Add-on Exam AD0-E716 Exam Practice Test

An Adobe Commerce developer successfully added a new column to the customers grid. This column needs the data to be formatted before showing its content in the grid. According to best practices, how would the developer add the custom logic to render the column?

• 1. Create an after pluginforMagento\Ui\Component\Listing\Columns\Column::prepareColumn(). 2. Add the custom logic within the afterPreparecoiumn method.
• 1. Create a customclassextending flagento\Ui\Component\Listing\Columns\Colunm. 2. Add the custom logic within the prepareDataSource method. 3. Add an attribute class to the column node within the module's customer_listing.xml.
• 1. Override the Magento\Customer\Ui\Component\DataProvider Class using a preference. 2. Override the getData() method and add the custom logic per row.

An Adobe Commerce developer is asked to create a new payment method for their project. This project has administrators who use the backend to manage customer information and occasionally place orders. When testing the new payment method on the frontend everything worked as expected, however, the payment method is missing in the admin. What is a possible reason for this?

• In the module di.xml, there were no default 3DS verification types configured as a VirtualType.
• In the module config.xmi, the boolean value for can_capture was set to false.
• In the module config.xmi, the node can_use_internal was not set to true.

An Adobe Commerce developer wants to create a product EAV attribute programmatically which should appear as WYSIWYG in the admin panel. They have made sure that wysiwyg_enabled has been set to true, however, the attribute is not appearing as WYSIWYG in the admin panel. What would be a possible reason?

• The is_html_allowed_on_front Option iS Set tO false.
• The input type is not set to text.
• The input type is not set to textarea.

An Adobe Commerce Cloud project is using Enhanced Integration Environments with two install a new payment module. The developer is using Cloud CLI for Commerce tool. What would a developer do to test this new feature under the integration environment?

• 1. Duplicate one of the integration environment branches. 2. Create a new active branch from integration and install the module. 3. Push the changes.
• 1. Create a new branch from integration and install the module. Adobe - AD0-E716 2. Push the changes. 3. Branch active status check is not necessary.
• 1. Deactivate one of the active integration environment branches. 2. Create a new active branch from integration and install the module. 3. Push the changes.

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: What is the problem with this xml snippet?

• The extension attribute references the wrong interface, it should have referenced the Magento\saies\Api\data\invoiceinterface.
• The extension attribute references the repository instead of the interface it implements (Magento\saies\Api\invoiceRepositorymterface).
• The type is wrong, string [] should be replaced with array.

A merchant of an Adobe Commerce Cloud project wants to setup one of their websites using a subdomain. The merchant is considering the domain to be set as secondstore.example.com. In addition to editing the magento-vars.php file, and apply a domain check and set $_SERVER["MAGE_RUN_CODE"] and $_SERVER["MAGE_RUN_TYPE"]. What file is required to perform this action?

• Configure secondstore.example.com subdomain route in NGINX virtual-host configuration file.
• Configure secondstore.example.com subdomain route in .magento/services.yaml.
• Configure secondstore.example.com subdomain route in .magento/routes.yaml.

A developer wants to deploy a new release to the Adobe Commerce Cloud Staging environment, but first they need the latest code from Production. What would the developer do to update the Staging environment?

• 1. Log in to the Project Web Interface. 2. Choose the Staging environment, and click Sync
• 1. Log in to the Project Web Interface. 2. Choose the Staging environment, and click Merge
• 1. Checkout to Production environment 2. Use the magento-cloud synchronize <environment-ID> Commerce CLI Command

Which hashing algorithm will Adobe Commerce choose to hash customer passwords?

• If the Sodium extension is installed, SHA256 will be chosen, otherwise MD5 will be used as the Magento default hashing algorithm.
• If the Sodium extension is installed, Argon 2ID13 will be chosen, otherwise SHA256 will be used as the Magento default hashing algorithm.
• It does not matter if the Sodium extension is installed or not, the Magento hashing default algorithm will be SHA256.

An Adobe Commerce developer was asked to provide additional information on a quote. When getting several quotes, the extension attributes are returned, however, when getting a single quote it fails to be returned. What is one reason the extension attributes are missing?

• The developer neglected to add coiiection="trueM to their attribute in etc/extension_attributes.xmi file. O ottribute code="my_attributesM type="MyVendor\MyModule\Api\Data\^AttributeInterface[]M collection="true" />
• The developer neglected to provide a plugin On Hagento\Quote\Api\CartRepositoryInterface: :get.
• The developer neglected to implement an observer on the coiiection_ioad_after event.

An integration named Marketing is created on the Adobe Commerce instance. The integration has access on Magento_Customer:: customer resources and the access token is xxxxxx. How would the rest API be called to search the customers?

• Using the integration access token as Bearer: Adobe - AD0-E716 curl -X GET https://magentourl/rest/Vl/customers/search?searchCriteria... -H 'Authorization: Bearer XXXXXX'
• Passing integration name and access token as http auth credentials: curl -X GET https ://Marketing:XXXXXX(Slmagentourl/rest/Vl/customers/search?5earchCriteria . . . Using integration name as username and access token as password, get the admin token (yyyyyy) via: curl -X POST https://magentourl/rest/Vl/integration/admin/token -d '{"username":"Marketing", "password":"XXXXXX"}' -H 'Content-
• Type: application/json' Use the admin token as Bearer curl -X GET https://magentourl/rest/Vl/customers/search?searchCriteria... -H 'Authorization: Bearer YYYYYY'