Magento-Certified-Professional-Cloud-Developer Exam Practice Test Instant Access

Question 1

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 2

You cloned the Integration branch to your local environment and Imported the database dump from Integration. You performed composer install and bin/magento setup:install.

While placing an order using PayPal Express, the following error occurs:

PayPal gateway has rejected request. Security header is not valid (#10002: Security error).

What Is the cause of this error?

Paypal gateway has rejected request, Security header is not valid (#10002: Security error).

What is the cause of this error?

AA new encryption key has been created on the setup:install action.

BThe folder var/session has no write permissions for the web server user.

CPaypal Sandbox API credentials are not valid for the local environment.

DThe PHP extension mcrypt has not been installed locally.

Answer : A

Question 3

You have a Starter project. Your code is ready for testing in the Staging environment, but you need the latest data from Production What do you do to update the Staging environment?

ALog in to the Project Web Ul. choose the Staging environment, and click Sync

BLog in to the Project Web Ul. choose the Staging environment, and click Merge

CCheckout the Staging branch and use the git push origin -f command

DCheckout the Production environment and use the magento-cloud sync CLI command

Answer : A

Question 4

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 5

You added a grunt autoprefixer command, which adds CSS vendor prefix like --webkit- and --moz- to CSS files generated by the setup:static-connect: deploy command.

After deployment you still see CSS files without prefixes. The hooks section in the .magento. app. Yaml file is:

Considering static assets are being generated on the build phase why are CSS prefixes missing?

ACustom commands can be run only on the deploy phase

BCSS vendor prefixes must be added to CSS files locally and committed as part of a theme

CThe static assets were not generated yet when the grunt command ran

DThe custom command was run before static assets were transferred into the init directory

Answer : C

Question 6

You added the env:ADMIN_PASSWORD variable in the Project Web Ul to change a Magento admin user's password After deployment you are unable to login using the new password

What causes this?

AWhen you add a variable. the build stage is being skipped because the codebase has not been changed You must push a commit to trigger a full deploy

BDeploy scripts read configuration from the environment variable called magento_cloud_variables. which contains an array of variables which were set without the env: prefix

CVariables which are set using the Project Web Ul are not available on the build phase the admin password variable should be
set in the . magento. env. yaml file

DThe sensitive option is required for env:ADMIN PASSWORD variable

Answer : D

Question 7

You are reviewing a third party extension for Magento Commerce Cloud compatibility Which pattern makes a module incompatible with Magento Commerce Cloud?

ADirect instantiation by the objectManager of non-generated classes in .phtml template files

BDirect instantiation by the objectManager In non-constructor methods with the class also being referenced in the constructor signature

CConfiguration referencing generated Proxy classes In the modules erc/frontend/di.xml file

DDirect instantiation of generated classes by the objectManager without the class being referenced in the constructor

Answer : D

Magento Certified Professional Cloud Developer Magento-Certified-Professional-Cloud-Developer Exam Practice Test