MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER Online Practice Questions and Answers

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?

A. Log in to the Project Web UI, choose the Staging environment, and click Sync

B. Log in to the Project Web UI, choose the Staging environment, and click Merge

C. Checkout the Staging branch and use the git push origin -f command

D. Checkout the Production environment and use the magento-cloud sync CLI command

You need to increase the Admin Session Lifetime up to 86400 seconds for the branch named Integration and children branches, but not for the Staging and Production branches.

How do you update this on the Integration branch and its child branches?

A. On your local environment, set the Admin Session Lifetime in the Magento admin backend under Stores > Configuration > Advanced > Admin > Security then dump this setting into the app/etc/ config.php file and commit this file

B. Add the following variable on the Integration branch and set its value to 86400: env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME

C. Run the following Magento CLI command: php bin/magento config:set admin/security/session_lifetime 86400

D. On the Integration environment, set the Admin Session Lifetime in the Magento admin backend under Stores > Configuration > Advanced > Admin > Security

On a project that deploys static content during the build phase, a merchant states the deploy phase is still taking too long. You consider turning off JavaScript minification to reduce the build time.

Besides reducing the build phase time, what two consequences does turning off JavaScript minification have? (Choose two.)

A. The deploy artifact size will be decreased because of the larger JavaScript can be symlinked

B. Browsing the store will be slower because larger JavaScript files have to be downloaded

C. The deploy phase will be shorter because JavaScript can be symlinked from init instead of copied

D. The build phase will be longer because the additional pass of JavaScript merging

In a Pro plan project, you notice there is a mail delivery problem in the Integration environment.

How do you troubleshoot this?

A. Change the log level in the log:email section of the .magento.env.yaml file

B. Update the SPF record in the DNS

C. Look in the var/log directory for the mail.log file

D. Move the test to the Staging environment

You add a new Composer dependency utilizing composer require. After testing composer install locally, you add the Composer lock and json files and perform a deployment. The build phase fails as Composer is unable to resolve the dependencies.

Why did this happen?

A. The versions of PHP on your local environment and integration environment differ

B. Your commit needs to contain the updated vendor folder

C. The project cache should have been cleared with the magento-cloud:project-build-cache command

D. You did not execute the install locally with --require-dev

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?

A. The Integration branch uses Platform-as-a-Service shared resources

B. Xdebug is always enabled on the Integration branch

C. The Staging and Production environments are consuming all available resources

D. The Integration branch services have not been optimized in the .magento/services.yaml file

You are testing an integration to an external service that requires you to configure an access key in an environment variable. You created a new environment to validate the functionality. The variable must only impact this environment.

How do you configure the variable?

A. Use the magento-cloud CLI utility with the environment, inheritable and level flags

B. Add the variable to the variables section under Project Settings specifying inheritance level

C. Add the variable to the .magento.env.yaml file specifying the environment and inheritable

D. Use vendor/bin/ece-tools to generate a local config.php file and commit the setting

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?

A. Use the Country Mapping in the Fastly settings to map country codes to store views.

B. In the Project Web UI, enable the Website IP Mapping setting.

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

D. Build or install a Magento extension that changes the default currency code on application init.

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 --scope-code=german general/locale/code de_DE

Static content deployment is set up on the deploy phase.

Why did this happen?

A. Static Content is not pre-generated for the de_DE locale

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

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

D. STATIC_CONTENT_SYMLINK is not configured in the .magento.env.yaml file

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

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

B. Add the env:COMPOSER_AUTH variable on the project level and make it visible on the build phase

C. Put the composer credentials into /mnt/build/.config/composer/auth.json

D. Add the COMPOSER_AUTH variable with the sensitive option enabled