Labour Day - Special 70% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: 70dumps

Magento-Certified-Professional-Cloud-Developer Questions and Answers

Question # 6

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 Ul. choose the Staging environment, and click Sync

B.

Log in to the Project Web Ul. 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-cloudsync CLI command

Full Access
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. yamlfile 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?

A.

Configure therelationships Section of the .magento.app.yaml file

B.

Find an appropriate Elasticsearch module to require with Composer

C.

Specify Elasticsearch as the search engine in the Magento Admin panel

D.

Remove the MySQL service from the services. yaml file

Full Access
Question # 8

After contacting Magento Support you were advised topermanently enable the Redis disable_locking option.

How do you implement this on a Production environment?

A.

Add disable_locking =true into the php.ini file in the Magento project root.

B.

Modify the .magento,app,yaml file to add the REDIS_SESSION_CONFIGURATION environment variable.

C.

Add the SESSION_CONFIGURATION environment variable into , magento,env,yaml with the correct value.

D.

In app/etc./env.php,add disable_locking: True inside the Redis session configuration block.

Full Access
Question # 9

A merchant slates the downtime during the deployment phase is too long

After analysis, it is determined the static content deployment is the longest process

Static content needs to be available immediately after deployment

How can the static content deployment time to be reduced?

A.

Move static content deploy the build phase

B.

Commit var.view_preprocessed to git so it already exists duringthe deployment phase

C.

Set stage /global/SKIP_SCD to true.

D.

Reduce the number of store view website

Full Access