Adobe Exam AD0-E706 Topic 4 Question 52 Discussion

Actual exam question for Adobe's AD0-E706 exam

Question #: 52
Topic #: 4

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?

AWhen 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

BDeploy scripts read configuration from the environment variable called magento_cloud_variables. which contains an array of variables which were set without the env: prefix

CVariables which are set using the Project Web Ul are not available on the build phase the admin password variable should be
set in the . magento. env. yaml file

DThe sensitive option is required for env:ADMIN PASSWORD variable

Show Suggested Answer

Suggested Answer: A

by Eulah at Feb 11, 2025, 11:26 PM

Limited Time Offer

25%

Off

Get Premium AD0-E706 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Malcolm

2 months ago

Oh, the joys of cloud deployment. Where the variables are made up and the build phases don't matter. I need a drink.

upvoted 0 times

Erinn

12 days ago

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.

upvoted 0 times

...

Evangelina

23 days ago

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.

upvoted 0 times

...

Lavonna

24 days ago

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.

upvoted 0 times

...

Meaghan

24 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

...

Larue

1 months ago

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.

upvoted 0 times

...

Crista

1 months 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

...

Lavonne

2 months 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

2 months ago

But what about option D? Maybe the sensitive option is required for the env:ADMIN_PASSWORD variable.

upvoted 0 times

...

Cordelia

2 months 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

Danilo

1 months ago

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

upvoted 0 times

...

Cora

2 months 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

...

Dyan

2 months 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

Olive

16 days ago

D) The sensitive option is required for env:ADMIN_PASSWORD variable.

upvoted 0 times

...

Barrett

20 days ago

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.

upvoted 0 times

...

Man

1 months ago

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.

upvoted 0 times

...

Donette

2 months 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

2 months ago

I agree with Jolene. The admin password variable should be set in the .magento.env.yaml file.

upvoted 0 times

...

Jolene

2 months ago

I think the answer is C. Variables set in the Project Web UI are not available during the build phase.

upvoted 0 times

...