Magento Magento Certified Professional Cloud Developer Exam Practice Questions (P. 1)
- Full Access (60 questions)
- Six months of Premium Access
- Access to one million comments
- Seamless ChatGPT Integration
- Ability to download PDF files
- Anki Flashcard files for revision
- No Captcha & No AdSense
- Advanced Exam Configuration
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?
What must you do to give them access?
- AIn the .magento.app.yaml file, add their email under Users. They need to enter their SSH public key.
- BAdd their SSH public key to a file named .ssh/authorized_keys and deploy the change.
- CIn the Cloud Project Web UI, click Add User to add their email. They need to enter their SSH public key.
- DAdd 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.
Correct Answer:
B
Reference:
https://devdocs.magento.com/cloud/before/before-workspace-ssh.html
B
Reference:
https://devdocs.magento.com/cloud/before/before-workspace-ssh.html
send
light_mode
delete
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?
What do you do to update the Staging environment?
- ALog in to the Project Web UI, choose the Staging environment, and click Sync
- BLog in to the Project Web UI, choose the Staging environment, and click Merge
- CCheckout the Staging branch and use the git push origin -f command
- DCheckout the Production environment and use the magento-cloud sync CLI command
Correct Answer:
B
Reference:
https://devdocs.magento.com/cloud/live/stage-prod-migrate-prereq.html
B
Reference:
https://devdocs.magento.com/cloud/live/stage-prod-migrate-prereq.html
send
light_mode
delete
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?
How do you correct the environment variable?
- AThe Sensitive option is checked by default and must be disabled
- BThe env:ADMIN_PASSWORD variable can only be used for an initial installation
- CThe environment variable should not have the env: prefix
- DThe ADMIN_PASSWORD variable should be configured via .magento.env.yaml
Correct Answer:
C
Reference:
https://devdocs.magento.com/cloud/env/environment-vars_magento.html
C
Reference:
https://devdocs.magento.com/cloud/env/environment-vars_magento.html
send
light_mode
delete
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?
SCD_MATRIX:
"magento/backend":
language:
- en_US
What is the effect of this configuration?
- AStatic content for frontend themes is generated during the deploy phase
- BAll frontend theme static content will be reused from the previous deployment
- COnly the static content for the adminhtml area will be generatedMost Voted
- DStatic content for all locales will be generated for all frontend themes
Correct Answer:
D
Reference:
https://devdocs.magento.com/cloud/env/variables-deploy.html
D
Reference:
https://devdocs.magento.com/cloud/env/variables-deploy.html
send
light_mode
delete
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?
There are instances when the process gets locked after Production deployments and order data is not exported.
How do you prevent this from happening?
- AUse the VAR_LOCKS_CLEAR variable available for the post_deploy stage in the .magento.env.yaml file
- BWrite a custom post_deploy hook to delete orphan lock files and include it in the .magento.app.yaml file
- CUse the VAR_LOCKS_CLEAR variable available for the build stage in the .magento.app.yaml file
- DYou must access the Production environment and delete the lock file
Correct Answer:
A
A
send
light_mode
delete
All Pages