17. 5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:Helvetica;
color:black;mso-bidi-font-weight:bold’>C
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black;mso-bidi-font-weight:bold’>
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black;mso-bidi-font-weight:bold’>17.Pipelines often require
access to protected resources such as servers, databases, and SCMs.
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black;mso-bidi-font-weight:bold’>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)?
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black;mso-bidi-font-weight:bold’>A. Store the secrets on the
Jenkins master using the Credentials plugin.
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black;mso-bidi-font-weight:bold’>B. Include the secrets In the
home directory of the Jenkins agent account.
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black;mso-bidi-font-weight:bold’>C. Store the secrets required
in the SCM alongside the application source code.
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black;mso-bidi-font-weight:bold’>D. Embed secrets into the
build and deployment scripts invoked by the job.
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black;mso-bidi-font-weight:bold’>E. Store the secrets as Node
Properties for each agent definition.
style=’mso-bidi-font-size:10.5pt;font-family:”Arial”,sans-serif;mso-fareast-font-family:
Helvetica;color:black’>