BlackFriday 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 29 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 29
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 Rebecka at Apr 14, 2024, 03:29 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Jesusita
4 months ago
I think adding the composer_auth variable with the sensitive option enabled (option D) provides an extra layer of security.
upvoted 0 times
...
Sommer
5 months ago
I agree with Gracie, keeping the credentials in a specific directory like /mnt/build/.config/composer/auth.json seems more organized.
upvoted 0 times
...
Gracie
5 months ago
That's true, but I prefer to keep the credentials in a separate location like option C.
upvoted 0 times
...
Jamika
5 months ago
But don't you think option A is also a good choice? We can hash the password for extra security.
upvoted 0 times
...
Gracie
5 months ago
I think option C is the best way to secure composer credentials.
upvoted 0 times
...
Heike
5 months ago
I prefer option B actually. Making the credentials visible only during the build phase seems like a good approach.
upvoted 0 times
...
Samira
6 months ago
I disagree, I believe option A is better. Hashing the password provides an added layer of security.
upvoted 0 times
...
Octavio
6 months ago
I think option C is the best way to secure composer credentials. Putting them in a separate directory makes sense.
upvoted 0 times
...
Alyce
7 months ago
Haha, good one Rene. *laughs* Okay, let's consider the other options too. Option A seems like it might work, but I'm not sure I like the idea of storing the password hash instead of the actual credentials.
upvoted 0 times
Kimbery
5 months ago
Putting the composer credentials into/mnt/build/.config/composer/auth.json (option C) seems like a secure way to handle it.
upvoted 0 times
...
Katheryn
5 months ago
I agree. It's important to keep sensitive information like credentials out of the repository.
upvoted 0 times
...
Gilberto
5 months ago
I think option B is a good idea. It keeps the credentials secure without storing them directly in the project repository.
upvoted 0 times
...
...
Rene
7 months ago
That's a solid solution. That way, we can keep the credentials secure and still have them accessible when we need them. *chuckles* I wonder if the exam writers have a sense of humor, though. Might as well throw in a joke about composer while we're at it.
upvoted 0 times
...
Vincent
7 months ago
Good point, Catarina. I'm leaning towards option B - adding the COMPOSER_AUTH variable on the project level and making it visible during the build phase.
upvoted 0 times
...
Catarina
7 months ago
I agree, keeping sensitive information like that out of the repository is a good security practice. But how do we do that without breaking the build process?
upvoted 0 times
...
Veronique
7 months ago
Okay, let's break this down. The goal is to remove the auth.json file from the project repository, right? That makes sense, we don't want to expose our composer credentials.
upvoted 0 times
...
Arminda
7 months ago
Hmm, this question seems a bit tricky. I'm not sure if I fully understand the context, but let's discuss it together.
upvoted 0 times
...

Save Cancel