AD0-E706 Practice Questions

Question 1

You are reviewing a third party extension for Magento Commerce Cloud compatibility Which pattern makes a module incompatible with Magento Commerce Cloud?

Accepted Answer

Direct instantiation of generated classes by the objectManager without the class being referenced in the constructor

Answer

Direct instantiation by the objectManager of non-generated classes in .phtml template files

Answer

Direct instantiation by the objectManager In non-constructor methods with the class also being referenced in the constructor signature

Answer

Configuration referencing generated Proxy classes In the modules erc/frontend/di.xml file

Question 2

You are migration an existing Magento 2 website to Magento Commerce Cloud. After setting up the project you would like to migrate the database to the integration branch. The database import fails with a disk space error.

How do you migrate the database data loss?

Accepted Answer

Configure the mysql disk Size in the .magento/services.yaml file

Answer

Configuration the mysql disk size using a variable in the , magento,evn,yaml file

Answer

Open a Magento Support ticket to increase the Integration branch disk size

Answer

Trim down the database to a smaller size

Question 3

You are updating a Magento Commerce Cloud project from version 2.2.5 to 2.3.0 with the command

Composer require magento/product-enterprise-edition:2,3,0

However, composer is unable to complete the task because the installed version of magento/magento-cloud-metapackage is not compatible.

How do you upgrade magento to the desired version?

Accepted Answer

Run composer require magento/magento-cloud-metapakage:'' =2, 3.0 < 2, 3,1'' -- update-with dependencies

Answer

Create a new project based on magento/ project-enterprise-edition: 2, 3, 0, the add eco-tools, custom modules and themes again with composer and migrate the data

Answer

Revert the composer.join to the last commit before the update and run the command again with the --with-dependencies argument

Answer

Remove magento.produce-enterprise-edition from the root composer, Json requirements and run composer update

Question 4

You need to increase the Admin Session Lifetime up to 86400 seconds for the branch named Integration and children branches but not for the Staging and Production branches.

How do you update this on the integration branch and its child branches?

Accepted Answer

Add the following variable on the Integration branch and set Its value to 86400 env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME

Answer

On your local environment, set the Admin Session Lifetime In the Magento admin backend under
Stores> Configuration> Advanced > Admin > Security then dump this setting into the app /etc/ confi.php file and commit this file

Answer

Run the following Magento CLI command php bin/magento config:set admin/security/session_lifetime 86400

Answer

On the Integration environment set the Admin Session Lifetime in the Magento admin backend under Stores > Configuration > Advanced > Admin > Security

Question 5

You are debugging an issue with an extension that only occurs in Production. The extension writes relevant information using the debug log level

However that specific information is not getting written to the logs on Production

How do you fix this>

Accepted Answer

Enable debug logging in the Admin interface in Production

Answer

Enable developer mode in Production for a short period to gather the required information

Answer

Write a custom logger that writes the debug information to var/log/custom, log

Answer

Enable debug logging in app/etc/config.php locally and deploy it to Production

Free Adobe AD0-E706 Exam Practice Questions & Explanations