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

Question 1

A merchant using Magento Commerce Cloud Pro reports an issue with an order missing transaction dat

a. The application uses a payment gateway integration which posts a series of callbacks to Magento

You would like to retrieve a complete list of calls to build a timeline of what happened

How do you achieve this?

AUse the magento -cloud environment: logs command to retrieve the access. log file from Production

BUse SSH to access all nodes and investigate the access. leg riles

CUse the magento-cloud environment:ssh command to access the environment and investigate the access.log file

DView the access. log file in the Project web UI

Answer : B

Question 2

You are upgrading a project to the latest version of Magento Commerce Cloud and part of the process involves a PHP version upgrade. This is now ready to be tested by the QA Team on the Integration environment.

How do you apply the PHP version upgrade?

AChange the PHP version in the .magento. app. yaml file and re-deploy

BSSH Into the Integration environment and upgrade PHP manually

CChange the php_version configuration in the ,magento,env,yaml file and re-deploy

DUse the magento-cloud CLI tool to update the php_version variable

Answer : A

Question 3

Your project is in a phase where the locales that will be used are still being determined. You need to configure your project in a manner that will allow them to be changed dynamically

How can you accomplish this?

ARemove the system/default/general/locale configuration from the app/etc/config.php file

BConfigure SCD_ON_DEMAND to true in the .magento.env.yaml file

CRun the command vendor/bin/ece-tools locales:unlock on the environment

DConfigure DYNAMIC_LOCALES in the SCD_MATRIX to true in the . magento. env. yarn! file

Answer : B

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

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 7

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?

AOn 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/ confi.php file and commit this file

BAdd the following variable on the Integration branch and set Its value to 86400
env:CONFIG_STORES_DEFAULT_ADMIN_SECURITY_SESSION_LIFETIME

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

DOn the Integration environment set the Admin Session Lifetime in the Magento admin backend under
Stores > Configuration > Advanced > Admin > Security

Answer : B

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