Magento-Certified-Professional-Cloud-Developer Exam Questions Instant Access

Question 1

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 2

You built a custom command that runs during the build phase, but it is not generating files property Magento Support provided a patch that you added to the project

What must you do to ensure this command runs after the patch has been applied?

AEnsure your custom command runs after the ece-tools build hooks

BMove your custom command to run in the deploy phase

CApply the patch manually in your custom command, because patches are always applied at the end of deployment

DNothing because patches are already applied when any hook runs

Answer : A

Question 3

The merchant wants to offer specific pricing in different currency markets so you have set up multiple websites to cover each currency.

Now they want customers to be directed to the appropriate website based on the country they are in.

How do you configure this?

AUse the Country Mapping in the Fastly settings to map country codes to store views

BIn the Project Web UI. enable the Website IP Mapping setting

CUpdate magento-vars.php to detect the country code from the IP address and map it

DBuild or install a Magento extension that changes the default currency code on application init

Answer : A

Question 4

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?

AThe Integration branch uses Platform-as-a-Service shared resources

BXdebug Is always enabled on the Integration branch

CThe Staging and Production environments are consuming all available resources

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

Answer : C

Question 5

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?

ACreate a new project based on magento/ project-enterprise-edition: 2, 3, 0, the add eco-tools, custom modules and themes again with composer and migrate the data

BRun composer require magento/magento-cloud-metapakage:'' =2, 3.0 < 2, 3,1'' -- update-with dependencies

CRevert the composer.join to the last commit before the update and run the command again with the --with-dependencies argument

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

Answer : B

Question 6

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 7

For the Magento search backend you would like lo move from MySQL lo Elasticsearch for your existing project. You have confirmed that your services. yaml file is configured appropriately However, after your most recently deployment, you notice the search engine is still set to MySQL

What additional step must be completed?

AConfigure the relationships Section of the .magento.app.yaml file

BFind an appropriate Elasticsearch module to require with Composer

CSpecify Elasticsearch as the search engine in the Magento Admin panel

DRemove the MySQL service from the services. yaml file

Answer : A

Magento Certified Professional Cloud Developer Magento-Certified-Professional-Cloud-Developer Exam Questions