Without using an external credentials manager, which of the following provides the most secure centralized mechanism for managing the "secrets" that Jenkins requires to login/authenticate (for example: keys, tokens, passwords)?

Pipelines often require access to protected resources such as servers, databases, and SCMs.

Without using an external credentials manager, which of the following provides the most secure centralized mechanism for managing the "secrets" that Jenkins requires to login/authenticate (for example: keys, tokens, passwords)?
A . Store the secrets on the Jenkins master using the Credentials plugin.
B . Include the secrets In the home directory of the Jenkins agent account.
C . Store the secrets required in the SCM alongside the application source code.
D . Embed secrets into the build and deployment scripts invoked by the job.
E . Store the secrets as Node Properties for each agent definition.

View Answer

Answer: A