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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe AD0-E706 Exam - Topic 5 Question 63 Discussion

To secure composer credentials you want to remove the auch. Json file from the project repository How do you do that?
B) Add the env:coMPOSER_AUTH variable on the project level and make it visible on the build phase
A) The build phase runs on a separate server and variables are not available there you must keep the credentials in the auth. j son file, but you can replace the password with its hash
C) Put the composer credentials into/mnt/build/.config/composer/auth.json
D) Add the composer_auth variable with the sensitive option enabled

Adobe AD0-E706 Exam - Topic 5 Question 63 Discussion

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

To secure composer credentials you want to remove the auch. Json file from the project repository How do you do that?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Selma at Oct 28, 2025, 07:39 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Joaquin
5 months ago
Option C is risky. Better to avoid hardcoding credentials.
upvoted 0 times
...
Kerrie
6 months ago
I'm confused. Why not just use option A?
upvoted 0 times
...
Vashti
6 months ago
I agree, but option D sounds good too. Sensitive option is key.
upvoted 0 times
...
Delila
6 months ago
I think option B is the best choice. It keeps credentials secure.
upvoted 0 times
...
Launa
6 months ago
I disagree, option A is outdated thinking.
upvoted 0 times
...
Ivory
6 months ago
Isn't it risky to expose any credentials at all?
upvoted 0 times
...
Daniel
6 months ago
Wait, you mean I can't just delete the auth.json file? That's the easiest solution!
upvoted 0 times
...
Mi
7 months ago
Option D sounds like the most secure solution. Enabling the sensitive option is crucial for protecting those credentials.
upvoted 0 times
...
Odette
7 months ago
Option C is the way to go. Keeping the credentials in a secure location on the build server is the safest approach.
upvoted 0 times
...
Marg
7 months ago
I’m a bit confused about the options, but I remember that keeping sensitive data out of the repository is important. Maybe option A is not the best approach?
upvoted 0 times
...
Tien
7 months ago
I practiced a similar question where we had to manage credentials, and I think putting them in a specific directory like in option C could be a solution too.
upvoted 0 times
...
Viki
7 months ago
Wait, are we really supposed to keep credentials in a file?
upvoted 0 times
...
Paz
7 months ago
I think option B is the best way to go.
upvoted 0 times
...
Edward
8 months ago
The auth.json file should never be committed to the repository. Option B seems like the best way to handle this.
upvoted 0 times
...
Carlee
8 months ago
Haha, option A is a joke, right? Storing passwords in plain text is a big no-no.
upvoted 0 times
...
Nichelle
8 months ago
Option D sounds like a solid choice for security.
upvoted 0 times
...
Gussie
8 months ago
I'm not entirely sure, but I feel like option D sounds familiar. It might be about adding sensitive variables, but I can't recall the details.
upvoted 0 times
...
Latrice
8 months ago
I think I remember something about environment variables being used to secure credentials, so maybe option B is the right choice?
upvoted 0 times
...
Arlene
9 months ago
I've dealt with this kind of issue before. I think Option D is the way to go - adding the composer_auth variable with the sensitive option enabled. That should keep the credentials secure while still allowing the build process to access them.
upvoted 0 times
...
Anglea
9 months ago
Okay, let's think this through step-by-step. The goal is to remove the auth.json file from the project repository, so that the credentials aren't exposed. Option C seems like the most straightforward solution, but I'll need to double-check the details.
upvoted 0 times
...
Vince
9 months ago
Hmm, this is an interesting one. I think the key here is to find a way to securely store the composer credentials without having them in the project repository. Option B looks promising, but I'm not sure if that's the best approach.
upvoted 0 times
...
Dean
9 months ago
I'm not sure about this one. The question seems a bit confusing, and I'm not familiar with the specifics of managing composer credentials. I'll need to read through the options carefully and think it through.
upvoted 0 times
Amber
4 months ago
I agree with B. Visibility on the build phase is key!
upvoted 0 times
...
Mammie
4 months ago
C seems like a good workaround, but is it safe?
upvoted 0 times
...
Darrel
4 months ago
A sounds risky. Keeping the password in the file? No way!
upvoted 0 times
...
Earleen
5 months ago
I’m leaning towards D. Sensitive options are important.
upvoted 0 times
...
Andree
5 months ago
I think option B makes sense. It keeps things secure.
upvoted 0 times
...
...

Save Cancel