Cisco Exam 300-910 Topic 4 Question 82 Discussion

Actual exam question for Cisco's 300-910 exam

Question #: 82
Topic #: 4

A DevOps engineer must build a Docker image to containerize an application. Then the image must be pushed to a repository on Docker Hub in a CI/CD pipeline using GitHub Actions.

Which approach securely encrypts the Docker Hub access token as an environment variable within the CI/CD pipeline?

AStore the access token with GitHub environment variables

BStore the access token with GitHub encrypted secrets

CStore the access token in an environment file in the repository

DHard code the access token in the repository with Base64 encoding

Show Suggested Answer

Suggested Answer: B

by Alesia at Aug 25, 2024, 12:07 AM

Limited Time Offer

25%

Off

Get Premium 300-910 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Argelia

2 months ago

I'd rather not 'hard code' anything. That's just begging for a security breach. Option B is the clear winner here.

upvoted 0 times

Polly

27 days ago

User4: I always prefer secure options like encrypted secrets.

upvoted 0 times

...

Tina

29 days ago

User3: Storing it as an environment variable in GitHub is much safer.

upvoted 0 times

...

Cecilia

1 months ago

Definitely, option B with encrypted secrets is the way to go.

upvoted 0 times

...

Eden

1 months ago

Absolutely, security should always be a top priority. Option B is the most secure approach for storing the access token.

upvoted 0 times

...

Orville

2 months ago

I agree, hard coding sensitive information is never a good idea. Using encrypted secrets adds an extra layer of security.

upvoted 0 times

...

Mila

2 months ago

I agree, hard coding is risky.

upvoted 0 times

...

Leota

2 months ago

Option B is definitely the way to go. Storing the access token with GitHub encrypted secrets is much more secure.

upvoted 0 times

...

Lucina

3 months ago

I disagree, hard coding the access token in the repository with Base64 encoding is not secure at all.

upvoted 0 times

...

Stefania

3 months ago

Hah, hardcoding the token? What is this, the 90s? GitHub secrets all the way, folks!

upvoted 0 times

...

Kandis

3 months ago

I don't know, Option C seems like a good compromise. An environment file in the repo is still pretty secure, right?

upvoted 0 times

Vilma

2 months ago

I would go with Option B for better security measures.

upvoted 0 times

...

Alex

2 months ago

Option C might work too, but encrypted secrets provide an extra layer of security.

upvoted 0 times

...

Kimi

2 months ago

I agree with User1, storing the access token as encrypted secrets is the way to go.

upvoted 0 times

...

Tonette

2 months ago

I think Option B is the best choice. Encrypted secrets are more secure.

upvoted 0 times

...

Delfina

3 months ago

I believe storing the access token with GitHub environment variables is also a secure option.

upvoted 0 times

...

Brandon

3 months ago

Option D is a terrible idea. Hardcoding the token, even with Base64 encoding, is just asking for trouble. Go with B.

upvoted 0 times

Nobuko

2 months ago

I agree, storing the access token with GitHub encrypted secrets is the best approach.

upvoted 0 times

...

Marlon

3 months ago

Option D is definitely not secure. B is the way to go.

upvoted 0 times

...

Renea

3 months ago

I agree with Dolores, storing it as encrypted secrets adds an extra layer of security.

upvoted 0 times

...

Dolores

3 months ago

I think the best approach is to store the access token with GitHub encrypted secrets.

upvoted 0 times

...

Jerry

3 months ago

Definitely B. Storing the token as a GitHub secret keeps it out of the codebase and away from prying eyes.

upvoted 0 times

Detra

2 months ago

Agreed, it's important to keep sensitive information secure.

upvoted 0 times

...

Gregoria

2 months ago

That's the best practice for security.

upvoted 0 times

...

Leonida

2 months ago

B) Store the access token with GitHub encrypted secrets

upvoted 0 times

...

Loreen

3 months ago

A) Store the access token with GitHub environment variables

upvoted 0 times

...

Curtis

3 months ago

B) Store the access token with GitHub encrypted secrets

upvoted 0 times

...

Erin

3 months ago

That's the best practice for security.

upvoted 0 times

...

Felix

4 months ago

Option B is the way to go. GitHub encrypted secrets are the most secure way to store sensitive information like the Docker Hub access token.

upvoted 0 times

Jacinta

2 months ago

Let's make sure to follow best practices for security.

upvoted 0 times

...

Sherly

3 months ago

Agreed, it's important to keep sensitive information safe.

upvoted 0 times

...

Asuncion

3 months ago

Definitely, that's the most secure option.

upvoted 0 times

...

Jacquelyne

3 months ago

I think we should store the access token with GitHub encrypted secrets.

upvoted 0 times

...