Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E706 Topic 4 Question 52 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 52
Topic #: 4
[All AD0-E706 Questions]

You added the env:ADMIN_PASSWORD variable in the Project Web Ul to change a Magento admin user's password After deployment you are unable to login using the new password

What causes this?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Lavonne
1 days ago
I bet the Magento team is sitting back and laughing at us poor souls struggling with this question. At least they kept the answers entertaining.
upvoted 0 times
...
Zack
13 days ago
But what about option D? Maybe the sensitive option is required for the env:ADMIN_PASSWORD variable.
upvoted 0 times
...
Cordelia
14 days ago
Ah, the old 'variables in the wrong place' trick. It's like they're testing our ability to read their minds instead of our Magento skills.
upvoted 0 times
...
Dyan
19 days ago
C'mon, you'd think they'd make it more obvious that the env:ADMIN_PASSWORD needs to be in the .magento.env.yaml file. What are we, mind readers?
upvoted 0 times
Donette
4 days ago
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.
upvoted 0 times
...
...
Beata
19 days ago
I agree with Jolene. The admin password variable should be set in the .magento.env.yaml file.
upvoted 0 times
...
Jolene
23 days ago
I think the answer is C. Variables set in the Project Web UI are not available during the build phase.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77