(Kevin Ryan has been working as a DevSecOps engineer in an MNC company that develops various software products and web applications. For easy…

To complete the integration, Kevin must provide Jenkins with the credentials needed to authenticate to the Azure Key Vault. This is accomplished by creating a new credential entry within Jenkins's central credential store. He would navigate to "Manage Jenkins" -> "Manage Credentials" and add a new "Microsoft Azure Service Principal" credential in the "Global Credentials (unrestricted)" domain. This new credential object will store the service principal's ID, secret, and tenant ID, allowing the Azure Key Vault plugin to securely access the secrets stored in the vault on behalf of Jenkins jobs.

A. Modifying old credentials is incorrect; a new, distinct credential for the Azure service principal should be created for proper management.

C. While credentials can be restricted, the standard and initial setup typically uses the global, unrestricted domain for general access.

D. This is incorrect because it involves modifying existing credentials and assumes a restricted scope, neither of which is the standard procedure.

1. Microsoft Documentation. (2023). Use Azure Key Vault secrets in Jenkins pipelines. Azure for Jenkins. Retrieved from https://learn.microsoft.com/en-us/azure/jenkins/jenkins-key-vault-plugin. (The section "Add a service principal to your Jenkins credentials" explicitly details the steps to add new credentials in the global domain.)

2. Jenkins Project. (n.d.). Azure Key Vault Plugin. Jenkins Plugins. Retrieved from https://plugins.jenkins.io/azure-keyvault/. (The plugin's usage documentation outlines the prerequisite of configuring a service principal credential in Jenkins.)