Question 1

After making changes lo custom commands in the deploy and build phases you deploy to Staging. The deployment takes much longer than expected, and Staging is in maintenance mode tor most of this time.

What do you do to reduce site downtime?

ASet the SKIP_MAINTENANCE_SCD variable to true In the . magento. env. yaml file

BAdd a custom command to the post_deploy phase to activate deferred deployment

CMove custom commands from the deploy phase to the build phase.

DUpdate the SCD_MATRIX variable to include only necessary custom commands

Answer : C

Question 2

You want to improve the ability to monitor Production deployments by setting up an email notification system How do you achieve this?

AEnable Deployment Notifications under Configure Environment > Settings in the Protect Web

BBuild a custom module which hooks into the deployment phase and sends emails in real-time

CConfigure log notifications in the .magento.env.yaml file

DUse the magento-cloud environment:deploy:email command to enable email notifications

Answer : B

Question 3

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./code de_DE

Static content deployment is set up to on the deploy phase

Why did this happen?

AStatic Content is not pre-generated for the de_DE locale

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

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

DSTA'IC_CONTENT_SYKLINK is not Configured in the .magento.env.yaml file

Answer : A

Question 4

To secure composer credentials you want to remove the auch. Json file from the project repository How do you do that?

AThe build phase runs on a separate server and variables are not available there you must keep the credentials in the auth. j son file, but you can replace the password with its hash

BAdd the env:coMPOSER_AUTH variable on the project level and make it visible on the build phase

CPut the composer credentials into/mnt/build/.config/composer/auth.json

DAdd the composer_auth variable with the sensitive option enabled

Answer : B

Question 5

You have created a new Integration branch and did not receive the administrator email with the password reset link. What is prohibiting the email from sending?

AYou have not enabled the Magento Email module with bin/magento module: enable

BThe Outgoing Emails setting is disabled under Environment Settings in the Project Web Ul

CEmail is always disabled on all integration branches

DYou have not configured SendGrid tor this environment

Answer : B

Free Practice Questions for Magento-Certified-Professional-Cloud-Developer Exam

Question 1

Question 2

Question 3

Question 4

Question 5