AD0-E706 Online Practice Questions and Answers

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?

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

B. The extension should be modified so it does not write to generated at runtime

C. The file should be generated locally and pushed via Git

D. The generated_code_WRITABLE variable should be set to true whenever using extensions

You are adding a new website to the Magento store you manage. This website will run on thesame instance of Magento to take advantage of shared integration processes.

When accessing the new website URL. it redirects to the original website. The files in /media/ and /static/

do not redirect The correct URL is present in the website configuration.

What step must you complete for the URL to stop redirecting?

A. Deploy an updated app/etc/config.php that includes the website URL.

B. In the Project Web Ul, add a separate branch for the new website and set the URL in the appropriate branch variable

C. Deploy an updated magento-vars. php that maps the hostname to the website code

D. in the Project Web Ul, add a JSON variable mapping website codes to URLs

A merchant with three websites using en_GB. fr_FR and de_AT requires a change in locale to de_DE for the German Production website After running the following command on Production you notice the frontend design of the German website is broken:

Php bin/magento config:set –scope=websites –scopes code=germ general /local./codede_DE

Static content deployment is set up toon the deploy phase.

Why did this happen?

A. Static Content is not pre-generated for the de_DE locale

B. de_DE is not writeable in pub/static and has to be configured via the .magento.app.yaml file

C. The magento-cloud environment: deploy command has not been run yet to generate static content for the new locale

D. STA"IC_CONTENT_SYKLINK is not Configured in the .magento.env.yaml file

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 瓀 ith-dependencies argument

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

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?

A. Use the magento-cloud CLl utility with the environmentinheritable and level flags

B. Add the variable to the variables section under Project Settings specifying inheritance level

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

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

You are setting up a third-party integration only for the Production environment, which connects to anexternal RabbitMQ server.

Where do you put the configuration?

A. In the app/etc/env.php file

B. In the QUEUE_ConFIGURATION variable added in the project Web UI or magento- cloud CLI

C. In the env:QUEUE_CONFIGURATION variable added in the project Web UI ormagento Cloud CLI

D. In the QUEUE_CONFIGURATION variable in the ,magento, env, yaml file

You created a custom module that is not functioning as expected on your Integration environment. You would like to debug the code using Xdebug. XdeDug is missing from the output of the command php -m.

What are two ways to load the Xdebug module? Choose 2 answers

A. Create a custom php.ini that includes the extension

B. You log a support request as php modules canonly be installed by support

C. Add xdebug into the . magento. app. yaml file under the extensions section

D. In the phpserver folder. create a folder conf-d and add a file ext-xdebug.im that Includes the extension

A merchant slates the downtime during the deployment phase is too long.

After analysis, it is determined the static content deployment is the longest process.

Static content needs to be available immediately after deployment.

How can the static content deployment time to be reduced?

A. Move static content deploy the build phase

B. Commit var.view_preprocessed to git so italready exists during the deployment phase

C. Set stage /global/SKIP_SCD to true.

D. Reduce the number of store view website