Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Cisco Exam 300-910 Topic 15 Question 75 Discussion

Actual exam question for Cisco's 300-910 exam
Question #: 75
Topic #: 15
[All 300-910 Questions]

An application is being developed to be used by the HR department of a company on a global scale. The application will be used as a central repository for employee contracts. For user access, a RADIUS server will be used with authorized user groups.

Which action must be used to prevent developers from accidentally committing secrets in the code?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Meaghan
30 days ago
Secrets in the code? I thought we were supposed to keep those in the company safe, not the GitHub repo! Guess the developers have been watching too many spy movies.
upvoted 0 times
...
Annice
1 months ago
A unit test? Really? That's like trying to use a sledgehammer to swat a fly. Definitely go with the pre-commit hook!
upvoted 0 times
...
Ben
1 months ago
Hmm, I'm not sure about C. DAST is more for dynamic security testing, not really for detecting secrets in the code.
upvoted 0 times
Octavio
8 days ago
B) Add a precommit Git hook to block the secrets
upvoted 0 times
...
Hillary
14 days ago
A) Add a unit test to block the secrets
upvoted 0 times
...
...
Keneth
1 months ago
D seems like a good choice too. A CI job can scan the entire repository and block the commit if any secrets are found.
upvoted 0 times
Vanesa
14 days ago
D) Add a job in the CI build to block the secrets
upvoted 0 times
...
Cecily
20 days ago
B) Add a precommit Git hook to block the secrets
upvoted 0 times
...
Bonita
21 days ago
A) Add a unit test to block the secrets
upvoted 0 times
...
...
Irene
2 months ago
I think option B is the way to go. A pre-commit hook is a great way to catch those secrets before they even make it into the codebase.
upvoted 0 times
Meaghan
27 days ago
User 2: Yeah, a pre-commit hook would definitely help prevent secrets from being committed.
upvoted 0 times
...
Nikita
1 months ago
User 1: I agree, option B is the best choice.
upvoted 0 times
...
...
Alita
2 months ago
I'm not sure about the answer. Can you explain why a precommit Git hook is the best option?
upvoted 0 times
...
Sarah
3 months ago
I agree with Roosevelt. Using a precommit Git hook is a good way to prevent secrets from being committed accidentally.
upvoted 0 times
...
Roosevelt
3 months ago
I think the answer is B) Add a precommit Git hook to block the secrets.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77