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
Q34: You are going to create a backup
Q35: You need to test a data-related issue
Q36: To secure composer credentials you want to
Q37: Magento Support advises you to upgrade to
Q38: Exploring the Production environment, you find MYSQL_USE_SLAVE_CONNECTION
Q39: After making changes to custom commands in
Q41: You need to get code with a
Q42: You have created a new Integration branch
Q43: Your project is in a phase where
Q44: A merchant with three websites using en_GB,
Unlock this Answer For Free Now!
View this answer and more for free by performing one of the following actions
Scan the QR code to install the App and get 2 free unlocks
Unlock quizzes for free by uploading documents