AD0-E706 Online Practice Questions and Answers

Youare 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?

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

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

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

D. Enable debug logging in the Admin interface in Production

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?

A. The injected class logged to the exception logrile, but a different logging implementation is used during deployment

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

C. A connection to the database was attempted which Is not available during the build phase

D. The three webservers generated different content which causes the build to be rolled back for safety

You fixed an issue in a third-party extension using a patch named m2-hotfixes/extension- fix.patch Before committing the patch to the repository you want to test itlocally.

How do you test a patch in a clean working copy?

A. Commit the patch because the pre-commit hook will abort the commit it any hotfix causes an issue

B. Run the command git apply m2-hotfixea/extension-fix.patch

C. Run the command bin/magento setup:hotfix:apply --patch=m2-hctfixes/extension- fix.patch

D. Configure a deploy hook in .magento.app.yaml that executes vendor/bin/ece-tools hotfix:apply --dry-run

On a project that deploys static content during the build phase a merchant states the deploy phase Is still taking too long You consider turning oft JavaScript minification to reduce the build time.

Besides reducing the build phase time what two consequences does turning off JavaScript minification have? Choose 2 answers

A. The deploy artifact size will be decreased because of the larger JavaScript can be symlinked

B. Browsing the store will be slower because larger JavaScript files have tobe downloaded

C. The deploy phase will be shorter because JavaScript can be symlinked from init instead of copied

D. The build phase will be longer because the additional pass of JavaScript merging

You need to disable a module on a Magento Commerce 2 3 Cloud project and remove its database tables The module usesthe declarative schema system to manage its database changes.

Which action do you take?

A. Run bin/magento module: disable MyCompany_MyModule on the local environment and then commit and deploy the app/etc/config.php file

B. Run bin/magento module:disable MyCompany_MyModule on the production environment and download and commit the app/etc/config.php file

C. Delete the module from the git repository leaving the record in app/etc/config.php Intact and deploy the changes

D. Remove the module line from the app/etc/config.php file on the local environment and then deploy the file

You want tomove static content deploy to the build phase of deployments. Which two actions do you take? Choose 2 answers

A. Download and commit app/etc/config.php from production

B. Run ece-tools scd-deploy:set build on production

C. Run ece-tools config:dump on production

D. Use scp to copy app/etc/config.php from local to production

You migrated a live On-Premise application to Magento Commerce Cloud Pro. The performance on Staging and Production is fine.

However, the internal testing team notices overall performance degradation on the Integration environment.

Why is this happening?

A. The Integration branch uses Platform-as-a-Service shared resources

B. Xdebug Is always enabled on the Integration branch

C. The Staging and Production environments are consuming all available resources

D. The Integration branch services have not been optimized In the .magento/services.yaml file

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

A. Activate the module by setting Caching Application to Fastly CDN.

B. Connect the Fastly shield using the Shield setting in the Magento admin.

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

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

You add a new Composer dependency utilizing composer require. After testing composer install locally, you add the Composer local and Json files and perform a deployment. The build phase fails as Composer is unable to resolve the dependencies.

Why do this happen/

A. The versions of PHP on your local environment and integration environment differ

B. Your commit needs to contain the updated vendor folder

C. The project cache should have been cleared with the magento-Cloud:project-build- cache command

D. You did not execute the install locally with --require-dev

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