Magento Magento Certified Professional Cloud Developer Exam

Page:    1 / 12   
Total 60 questions

You are working with a new developer who needs to be able to deploy code and view logs on Magento Commerce Cloud.
What must you do to give them access?

  • A. In the .magento.app.yaml file, add their email under Users. They need to enter their SSH public key.
  • B. Add their SSH public key to a file named .ssh/authorized_keys and deploy the change.
  • C. In the Cloud Project Web UI, click Add User to add their email. They need to enter their SSH public key.
  • D. Add a Magento admin user for them and paste the SSH public key into their userג€™s SSH Key field, which is available only on Magento Commerce Cloud.


Answer : B

Reference:
https://devdocs.magento.com/cloud/before/before-workspace-ssh.html

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


Answer : B

Reference:
https://devdocs.magento.com/cloud/live/stage-prod-migrate-prereq.html

You need to specify the admin password using an environment variable. You have created an environment variable env:ADMIN_PASSWORD with a valid password. When attempting to log in to the Magento Admin it is not accepting the new password.
How do you correct the environment variable?

  • A. The Sensitive option is checked by default and must be disabled
  • B. The env:ADMIN_PASSWORD variable can only be used for an initial installation
  • C. The environment variable should not have the env: prefix
  • D. The ADMIN_PASSWORD variable should be configured via .magento.env.yaml


Answer : C

Reference:
https://devdocs.magento.com/cloud/env/environment-vars_magento.html

While investigating an inherited Magento Commerce Cloud project, you notice the following SCD_MATRIX configuration in .magento.env.yaml: stage: global:
SCD_MATRIX:
"magento/backend":
language:
- en_US
What is the effect of this configuration?

  • A. Static content for frontend themes is generated during the deploy phase
  • B. All frontend theme static content will be reused from the previous deployment
  • C. Only the static content for the adminhtml area will be generated
  • D. Static content for all locales will be generated for all frontend themes


Answer : D

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

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?

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


Answer : A

Page:    1 / 12   
Total 60 questions