Adobe AD0-E706 Exam Practice Test Instant Access

Question 1

After installing a Magento extension that implements a new class for a site and deploying this to an integration environment you see it is not working.

In the logs you discover the following error:

How do you fix this?

AA support ticket should be riled with Magento Commerce Cloud to fix the filesystem issue

BThe extension should be modified so it does not write to generated at runtime

CThe file should be generated locally and pushed via Git

DThe generated_code_WRITABLE variable should be set to true whenever using extensions

Answer : A

Question 2

You are testing an integration to an external service that requires you to configure an access key in an environment variable. You created a new environment to validate the functionality The variable must only impact this environment

How do you configure the variable?

AUse the magento-cloud CLl utility with the environment inheritable and level flags

BAdd the variable to the variables section under Project Settings specifying inheritance level

CAdd the variable to the .magento.env.yaml file specifying the environment and inheritable

DUse vendor/bin/ece-tools to generate a local config.phpfile and commit the setting

Answer : B

Question 3

You need to get code with a backend order placement security related fix into production as quickly as possible.

The project currently deploys static content during the build phase with both stags/global/SKIP_SCD and stage/deploy/STATIC_STATIC_CONTENT_SYMLINK set to false.

What setting in .magento,env,yaml minimizes the overall deployment time?

ARemove all themes from stages/global/SCD_MATRIX so they will not be generated

BSet stage/global/Static_CONTENT_SYMLINK to true to symlink static assets to the init directory

CSet stage/global/SCD_COMPRESSION_LEVEL to 0 to avoid the compression overhead

DSet stage/global/SKIP_SCD to true to completely avoid static content processing

Answer : B

Question 4

A custom module that adds a new console command for bin/magento has just been built Deploying this to the Production environment on your Pro plan site causes the build phase to fall.

You find this occurs when you inject certain Magento core classes in your console command class The command works on your local environment

Why does this occur?

AThe injected class logged to the exception log rile, but a different logging implementation is used during deployment

BFiles were written to the root Magento directory. which is read-only on Magento Commerce Cloud

CA connection to the database was attempted which Is not available during the build phase

DThe three webservers generated different content which causes the build to be rolled back for safety

Answer : A

Question 5

You need to directly access the database that belongs to your Integration environment from your local environment How do you achieve this?

AFind the connection Information from the env.php file and connect with your local MySQL client

BCollect the SSH connection details using magento-cloud ssh --pipe and connect with your local MySQL client

CAdd the ece-tools db-expose command to your deploy hook

DUse the magento-cloud db:sql command

Answer : D

Question 6

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?

ACreate 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

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

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

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

Answer : B

Question 7

After deploying to Staging for the first time with the Fastly module installed, you notice that Fastly is not caching pages. Page caching works properly in a local development environment.

What two steps are required to make Fastly cache pages?

Choose 2 answers

AActivate the module by setting Caching Application to Fastly CDN.

BConnect the Fastly shield using the Shield setting in the Magento admin.

CEnable the Fastly connection by running magento-Cloud fastly:setup.

DPopulate VCL in Fastly by clicking on Upload VCL to Fastly in the Magento admin.

Answer : A, D

Adobe AD0-E706 Adobe Certified Expert-Magento Commerce Cloud Developer Exam Practice Test