Adobe Certified Expert-Magento Commerce Cloud Developer: AD0-E706

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 need to install a third party extension which is provided in a tar archive.

It expands to a folder Structure in app/code/MyCompany/MyMedule.

Which action do you take to install the extension?

A. Use the composer package command to create a composer package and install it with composer require

B. Use the composer-merge-plugin to enable support for extension in app/code

C. Add it to the project inapp/code and commit it to git

D. Request composer repository credentials from the extension vendor

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.