Question 1

In a Pro plan project, you notice there is a mail delivery problem in the Integration environment How do you troubleshoot this?

AChange the log level in the lcg:emall section of the .magento.env.yaml file

BUpdate the SPF record in the DNS

CLook In the var/log directory for the mail. log file

DMove the test to the Staging environment

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?

ACreate a symlink from /top/internal to the internal/ folder

BDeclare a shared mount for the internal/directory in .magento. app.yaml

CRequest the vendor make the directory configurable in the Magento admin

DAdd a patch for extension so it uses the subdirectory var/internal/ instead

Answer : B

Question 3

Your team is working on two ma)or changes affecting the product page and you want the ability to implement and test these changes in parallel. Your company is using the Pro plan

How do you achieve this using the Project Web Ul?

ACreate branches from Production to ensure the catalog is up to date

BCreate branches from Integration to facilitate merging

CCreate branches from the Magento Cloud Docker image to ensure the changes are made on the most recent codebase

DCreate branches from Staging to ensure the changes are tested on an environment similar to Production

Answer : A

Question 4

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 it locally

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

ACommit the patch because the pre-commit hook will abort the commit it any hotfix causes an issue

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

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

DConfigure a deploy hook in .magento.app.yaml that executes

Answer : B

Question 5

You need to test a data-related issue occurring on your Production environment. You replicate the data to your staging environment utilizing the Synchronization tool. When you access your staging environment you are redirected to your Production environment Your project is on the Starter plan.

How do you prevent the redirect?

AUse the magento-cloud route:add command to create a route to the Staging URL

BModify the yA3EXT0_CLOUD_R0UTES environment variable on your staging environment

CEnter the proper URL in the Routes tor Staging under the Environment Settings in the Project Web Ul

DConfigure UPDATE_URLS to true in the .magento.env.yaml file