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 Exam AD0-E706 Topic 7 Question 47 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 47
Topic #: 7
[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 Serita at Oct 24, 2024, 08: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
Earnestine
3 months ago
Option A? More like 'option OMG no, what are you thinking?!' *facepalm*
upvoted 0 times
Dino
2 months ago
User 4: Yeah, C seems like the best choice for securing composer credentials.
upvoted 0 times
...
Tiara
2 months ago
User 3: I think C is the safest option, putting credentials in a secure location.
upvoted 0 times
...
Antonette
2 months ago
User 2: Definitely not A, that sounds risky.
upvoted 0 times
...
Erick
2 months ago
User 1: Option A? More like 'option OMG no, what are you thinking?!' *facepalm*
upvoted 0 times
...
...
Mozelle
3 months ago
B seems like the easiest solution, but I wonder if it'll work on all build servers. Gotta test that one out.
upvoted 0 times
...
Marge
4 months ago
A is just asking for trouble. Storing passwords in plain text? No way! *shakes head*
upvoted 0 times
Rory
2 months ago
Adding the composer_auth variable with the sensitive option enabled sounds like a good solution.
upvoted 0 times
...
Leonora
2 months ago
Definitely, we need to prioritize security when it comes to sensitive information.
upvoted 0 times
...
Eva
3 months ago
I think putting the composer credentials in a separate file is a safer option.
upvoted 0 times
...
Halina
3 months ago
Agreed, storing passwords in plain text is a big no-no.
upvoted 0 times
...
...
Dean
4 months ago
D seems interesting, but I'm not sure about the 'sensitive option'. Hmm, I'll have to look into that one.
upvoted 0 times
Royal
3 months ago
D) Add the composer_auth variable with the sensitive option enabled
upvoted 0 times
...
Rosalind
3 months ago
B) Add the env:coMPOSER_AUTH variable on the project level and make it visible on the build phase
upvoted 0 times
...
Beckie
3 months ago
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
upvoted 0 times
...
...
Shoshana
4 months ago
I agree with Aja, adding the env:composer_auth variable seems like the most secure option.
upvoted 0 times
...
Helaine
4 months ago
Option C is the way to go. Keeping sensitive info like credentials out of the project repo is security 101.
upvoted 0 times
Kayleigh
3 months ago
C) Put the composer credentials into /mnt/build/.config/composer/auth.json
upvoted 0 times
...
Sharen
3 months ago
B) Add the env:COMPOSER_AUTH variable on the project level and make it visible on the build phase
upvoted 0 times
...
Elenora
3 months ago
A) The build phase runs on a separate server and variables are not available there you must keep the credentials in the auth.json file, but you can replace the password with its hash
upvoted 0 times
...
Micheline
4 months ago
C) Put the composer credentials into /mnt/build/.config/composer/auth.json
upvoted 0 times
...
...
Aja
4 months ago
I think option B is the best way to secure composer credentials.
upvoted 0 times
...

Save Cancel