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
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.
B
Reference:
https://devdocs.magento.com/cloud/before/before-workspace-ssh.html

Hi! Do you need help with this question ?
- Why isn't the A the right answer?
- Traducir la pregunta al español
Contributor get free access to an augmented ChatGPT 4 trained with the latest IT Questions.
Question #2
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
B
Reference:
https://devdocs.magento.com/cloud/live/stage-prod-migrate-prereq.html

Hi! Do you need help with this question ?
- Why isn't the A the right answer?
- Traducir la pregunta al español
Contributor get free access to an augmented ChatGPT 4 trained with the latest IT Questions.
Question #3
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
C
Reference:
https://devdocs.magento.com/cloud/env/environment-vars_magento.html

Hi! Do you need help with this question ?
- Why isn't the A the right answer?
- Traducir la pregunta al español
Contributor get free access to an augmented ChatGPT 4 trained with the latest IT Questions.
Question #4
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
D
Reference:
https://devdocs.magento.com/cloud/env/variables-deploy.html

Hi! Do you need help with this question ?
- Why isn't the A the right answer?
- Traducir la pregunta al español
Contributor get free access to an augmented ChatGPT 4 trained with the latest IT Questions.
Question #5
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
A

Hi! Do you need help with this question ?
- Why isn't the A the right answer?
- Traducir la pregunta al español
Contributor get free access to an augmented ChatGPT 4 trained with the latest IT Questions.
All Pages