Multiple Choice
You added the env:ADMIN_PASSWORD variable in the Project Web UI to change a Magento admin user's password. After deployment you are unable to login using the new password. What causes this?
A) When you add a variable, the build stage is being skipped, because the codebase has not been changed. You must push a commit to trigger a full deploy
B) Deploy scripts read configuration from the environment variable called $MAGENTO_CLOUD_VARIABLES , which contains an array of variables which were set without the env: prefix Deploy scripts read configuration from the environment variable called $MAGENTO_CLOUD_VARIABLES , which contains an array of variables which were set without the env: prefix
C) Variables which are set using the Project Web UI are not available on the build phase, the admin password variable should be set in the .magento.env.yaml file Variables which are set using the Project Web UI are not available on the build phase, the admin password variable should be set in the .magento.env.yaml file
D) The sensitive option is required for env:ADMIN_PASSWORD variable The sensitive option is required for variable
Correct Answer:
Verified
Correct Answer:
Verified
Q25: You are upgrading a project to the
Q26: You have created a new Integration branch
Q27: A custom module that adds a new
Q28: You add a new Composer dependency utilizing
Q29: You are reviewing a third party extension
Q31: You want to improve the ability to
Q32: You need to increase the Admin Session
Q33: You are migrating an existing Magento 2
Q34: Your project is in a phase where
Q35: Your team is working on two major