200-901 · Question #345
A developer is developing a web application that uses username and password to authenticate to the next service. The user credentials must be available at any time in the application. The developer…
The correct answer is B. Store the username and password in a vault. Storing credentials in a vault (B) is the most secure method. A secrets vault (such as HashiCorp Vault, AWS Secrets Manager, or CyberArk) provides encrypted, access-controlled storage for sensitive credentials, with audit logging and the ability to rotate secrets without…
Question
A developer is developing a web application that uses username and password to authenticate to the next service. The user credentials must be available at any time in the application. The developer must choose and implement a secure method of storing the authentication credentials that are used in the automation code. Which password handling method must be used to minimize the security risk?
Options
- AStore the username and password in a separate configuration file.
- BStore the username and password in a vault.
- CStore the passwords in a dictionary.
- DStore the username and password in code.
How the community answered
(24 responses)- A4% (1)
- B79% (19)
- C13% (3)
- D4% (1)
Explanation
Storing credentials in a vault (B) is the most secure method. A secrets vault (such as HashiCorp Vault, AWS Secrets Manager, or CyberArk) provides encrypted, access-controlled storage for sensitive credentials, with audit logging and the ability to rotate secrets without changing application code. Storing credentials in a configuration file (A) risks exposure if the file is committed to source control or accessed by unauthorized users. Storing in a dictionary (C) means they exist in memory or code in plaintext. Hardcoding credentials in source code (D) is the worst practice-it permanently exposes secrets in version control history and is a critical security vulnerability.
Topics
Community Discussion
No community discussion yet for this question.