AD0-E706 Practice Online

Question 1

You added the env:ADMIN_PASSWORD variable in the Project Web Ul to change a Magento admin user's

password After deployment you are unable to login using the new password

What causes this?

A : When you add a variable. the build stage is being skipped because the codebase has not been changed You must push a commit to trigger a full deploy

B :

Deploy scripts read configuration from the environment variablecalled magento_cloud_variables. which

contains an array of variables which were set without the env: prefix

C :

Variables which are set using the Project Web Ul are not available on the build phase the admin

password variable should be

set in the . magento.env. yaml file

D :

The sensitive option is required for env:ADMIN PASSWORD variable

Answer: D

Question 2

You are reviewing a third party extension for Magento Commerce Cloud compatibility

You discover the module writes to a custom directory called internal/ within the Magento base directory

The directory has to be shared by all web servers

What do you do so the module can be used on Magento Commerce Cloud?

A : Create a symlink from /top/internal to the internal/ folder

B : Declare a shared mount for the internal/directory in .magento. app.yaml

C : Request the vendor make the directory configurable in the Magento admin

D : Add a patch for extension so it uses the subdirectory var/internal/ instead

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?

A : Remove all themes from stages/global/SCD_MATRIX so they will not be generated

B : Set stage/global/Static_CONTENT_SYMLINK to true to symlink static assets to the init directory

C : Set stage/global/SCD_COMPRESSION_LEVEL to 0 to avoid the compression overhead

D : Set stage/global/SKIP_SCD to true to completely avoid static content processing

Answer: B

Question 4

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?

A :

Create a new project based on magento/ project-enterprise-edition: 2, 3, 0, the add eco-tools,

custommodules and themes again with composer and migrate the data

B :

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

dependencies

C :

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

–with-dependencies argument

D :

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

composer update

Answer: B

Question 5

For the Magento search backend you would like lo move from MySQL lo Elasticsearch for your existing

project. You have confirmed that your services. yaml file is configured appropriately However, after your

most recently deployment, you notice the search engine is still set to MySQL

What additional step must be completed?

A : Configure the relationships Section of the .magento.app.yaml file

B : Find an appropriate Elasticsearch module to require with Composer

C : SpecifyElasticsearch as the search engine in the Magento Admin panel

D : Remove the MySQL service from the services. yaml file

Answer: A

Name:	Adobe Certified Expert - Magento Commerce Cloud Developer
Exam Code:	AD0-E706
Certification:	Adobe Magento Commerce
Vendor:	Adobe
Total Questions:	62
Last Updated:	Apr 23, 2024

Download Demo AD0-E706 Dumps

Create Account

Password Recovery

AD0-E706 Practice Online

Download Demo AD0-E706 Dumps

Member Login

Create Account

Password Recovery

AD0-E706 Practice Online