Magento Certified Professional Cloud Developer

Review 60 MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER practice questions with answer explanations and community insights.

Question 1

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?

  1. In the .magento.app.yaml file, add their email under Users. They need to enter their SSH public key.
  2. Add their SSH public key to a file named .ssh/authorized_keys and deploy the change.
  3. In the Cloud Project Web UI, click Add User to add their email. They need to enter their SSH public key.
  4. 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.

Question 2

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?

  1. Log in to the Project Web UI, choose the Staging environment, and click Sync
  2. Log in to the Project Web UI, choose the Staging environment, and click Merge
  3. Checkout the Staging branch and use the git push origin -f command
  4. Checkout the Production environment and use the magento-cloud sync CLI command

Question 3

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?

  1. The Sensitive option is checked by default and must be disabled
  2. The env:ADMIN_PASSWORD variable can only be used for an initial installation
  3. The environment variable should not have the env: prefix
  4. The ADMIN_PASSWORD variable should be configured via .magento.env.yaml

Question 4

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?

  1. Static content for frontend themes is generated during the deploy phase
  2. All frontend theme static content will be reused from the previous deployment
  3. Only the static content for the adminhtml area will be generated
  4. Static content for all locales will be generated for all frontend themes

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?

  1. Use the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file
  2. Write a custom post_deploy hook to delete orphan lock files and include it in the .magento.app.yaml file
  3. Use the VAR_LOCKS_CLEAR variable available for the build stage in the .magento.app.yaml file
  4. You must access the Production environment and delete the lock file
We are moving to a new platform

CertificationTest is being migrated. Some pages may be slow or briefly unavailable; everything will be back to normal within a few hours. If you run into any issue, email support@certificationtest.net.