QUESTION: 5

A project has a Magento cron job implemented to export new order data to a file. This process can also be triggered by a custom bin/magento command. The functionality uses a lock file in var/locks to prevent concurrent execution. There are instances when the process gets locked after Production deployments and order data is not exported.
How do you prevent this from happening?

Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file
Write a custom post_deploy hook to delete orphan lock files and include it in the .magento.app.yaml file
Use the VAR_LOCKS_CLEAR variable available for the build stage in the .magento.app.yaml file
You must access the Production environment and delete the lock file

Answer(s): A

Reveal Solution Next Question

QUESTION: 6

While launching a site migrated from Magento 1, you are instructed to change the website CNAME record in your DNS provider by Magento for go live. What is the purpose of setting this record?

Setting this record causes sent email to be properly authenticated and not show in junk folders.
Setting this record enables the page caching service for your site.
Setting this record is needed on Pro to allow upsizing servers without downtime.
Setting this record reduces the time it takes for customers to start seeing your Magento 2 site.

Answer(s): D

Reference:

https://devdocs.magento.com/cloud/live/site-launch-checklist.html

Reveal Solution Next Question

QUESTION: 7

While setting up a Magento project, you run the following command:

magento-cloud variable:update ADMIN_USERNAME --value=alice

What will this command do?

Configure the Magento Commerce Cloud tools to use alice for API call authentication.
Change your username to alice for logging into the magento-cloud CLI tool.
Update the Magento cloud/admin/username config variable to alice.
Change the username of the default administrator account to alice.

Answer(s): C

Reveal Solution Next Question

QUESTION: 8

Exploring the Production environment, you find MYSQL_USE_SLAVE_CONNECTION is enabled. What is the purpose of this setting?

To split the database tables between the three Production servers and improve performance.
To enable fault tolerance on the MySQL cluster.
To utilize the read-only slave servers and improve the overall performance.
To allow database backups from a MySQL slave server with minimal impact on the Production site.

Answer(s): C

Reference:

https://devdocs.magento.com/cloud/env/variables-deploy.html

Reveal Solution Next Question

Free MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER Exam Braindumps (page: 2)

QUESTION: 5

QUESTION: 6

Reference:

QUESTION: 7

QUESTION: 8

Reference: