Cyber Monday 2024! 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 9 Question 34 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 34
Topic #: 9
[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 Kristeen at Jun 03, 2024, 12:56 AM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Alyssa
6 months ago
I'm with Beckie on this one. Option A is just asking for trouble. You gotta keep those credentials out of the repo at all costs.
upvoted 0 times
Carey
5 months ago
Definitely, we need to find a secure way to handle composer credentials.
upvoted 0 times
...
Ria
5 months ago
I agree, keeping credentials in the repo is a big security risk.
upvoted 0 times
...
...
Beckie
6 months ago
Ha! Keeping the credentials in the auth.json file? That's like storing your password in a plain text file. Option B seems like the best choice here.
upvoted 0 times
Silvana
5 months ago
Adding the env:COMPOSER_AUTH variable on the project level is definitely the way to go.
upvoted 0 times
...
Alisha
5 months ago
I agree, storing credentials in a plain text file is a big security risk.
upvoted 0 times
...
Elvera
5 months ago
Option B seems like the best choice here.
upvoted 0 times
...
Nan
5 months ago
Yeah, adding the env:COMPOSER_AUTH variable is the way to go.
upvoted 0 times
...
Audry
5 months ago
I agree, Option B seems like the safest choice.
upvoted 0 times
...
Peggy
6 months ago
Storing credentials in a plain text file is a big no-no.
upvoted 0 times
...
...
Talia
6 months ago
I agree with Jesusa, putting the credentials in a specific directory seems like a secure option.
upvoted 0 times
...
Mirta
6 months ago
Option D sounds good, but I'm not sure about the 'sensitive option' part. I'll need to look into that further.
upvoted 0 times
Alaine
6 months ago
C) Put the composer credentials into/mnt/build/.config/composer/auth.json
upvoted 0 times
...
Nathan
6 months ago
B) Add the env:coMPOSER_AUTH variable on the project level and make it visible on the build phase
upvoted 0 times
...
Felicitas
6 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
...
...
Jesusa
6 months ago
I think option C is the best way to secure composer credentials.
upvoted 0 times
...
Marilynn
6 months ago
I think option C is the way to go. It's the most straightforward approach and keeps the credentials secure.
upvoted 0 times
Bev
5 months ago
Yeah, putting the composer credentials in a separate directory definitely sounds like a good idea.
upvoted 0 times
...
Ronnie
5 months ago
I agree, option C seems like the best way to keep the credentials secure.
upvoted 0 times
...
Donte
5 months ago
Yeah, putting the credentials in /mnt/build/.config/composer/auth.json is a simple and secure way to handle it.
upvoted 0 times
...
Ayesha
6 months ago
I agree, option C seems like the best choice for securing composer credentials.
upvoted 0 times
...
Sherrell
6 months ago
Yeah, I think putting the composer credentials in a separate directory is a good practice for security.
upvoted 0 times
...
Lilli
6 months ago
I agree, option C seems like the best choice. It's simple and secure.
upvoted 0 times
...
...

Save Cancel