Magento MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER Exam
Magento Certified Professional Cloud DeveloperExam (Page 3 )

Updated On: 1-Feb-2026

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.

Answer(s): B


Reference:

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



You cloned the Integration branch to your local environment and imported the database dump from Integration. You performed composer install and bin/magento setup:install. While placing an order using PayPal Express, the following error occurs:

PayPal gateway has rejected request. Security header is not valid (#10002: Security error).

What is the cause of this error?

  1. A new encryption key has been created on the setup:install action.
  2. The folder var/session has no write permissions for the web server user.
  3. PayPal Sandbox API credentials are not valid for the local environment.
  4. The PHP extension mcrypt has not been installed locally.

Answer(s): C



You want to exclude some themes from static assets generation only for integration environments. You are trying to choose where to set the SCD_EXCLUDE_THEMES variable in the .magento.env.yaml file or in the Project Web UI.

What prevents the usage of the .magento.env.yaml file?

  1. Child environments inherit the variable when you use the .magento.env.yaml file
  2. The code from integration would be merged into the Staging and Production branches
  3. The .magento.env.yaml file can contain only deployment configuration options, which are only available if static assets generation runs on the deploy phase
  4. Only variables which are set using the Project Web UI has the option visible during build

Answer(s): C



You fixed an issue in a third-party extension using a patch named m2-hotfixes/extension-fix.patch. Before committing the patch to the repository you want to test it locally.
How do you test a patch in a clean working copy?

  1. Commit the patch because the pre-commit hook will abort the commit if any hotfix causes an issue
  2. Run the command git apply m2-hotfixes/extension-fix.patch
  3. Run the command bin/magento setup:hotfix:apply --patch=m2-hotfixes/extension-fix.patch
  4. Configure a deploy hook in .magento.app.yaml that executes vendor/bin/ece-tools hotfix:apply --dry-run

Answer(s): B


Reference:

https://devdocs.magento.com/cloud/project/project-patch.html



You need to test a data-related issue occurring on your Production environment. You replicate the data to your staging environment utilizing the Synchronization tool. When you access your staging environment, you are redirected to your Production environment. Your project is on the Starter plan.

How do you prevent the redirect?

  1. Use the magento-cloud route:add command to create a route to the Staging URL
  2. Modify the MAGENTO_CLOUD_ROUTES environment variable on your staging environment
  3. Enter the proper URL in the Routes for Staging under the Environment Settings in the Project Web UI
  4. Configure UPDATE_URLS to true in the .magento.env.yaml file

Answer(s): C



Viewing page 3 of 13
Viewing questions 11 - 15 out of 60 questions



Post your Comments and Discuss Magento MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER exam prep with other Community members:

Join the MAGENTO-CERTIFIED-PROFESSIONAL-CLOUD-DEVELOPER Discussion