Which command links a secret to the builder service account?

Which command links a secret to the builder service account?

• A. oc secrets link builder my secret
• B. oc logs -f build jhost-1
• C. oc delete all -l app=appname
• D. oc set triggers bc/name --from-image=project/image:tag

Answer: (A)

Linking a secret to a service account is how you grant pods running under that account access to the secret’s data. In OpenShift, the builder service account is used by build pods, so attaching a secret to the builder SA allows those builds to use credentials stored in the secret (for example, to pull from a private image registry). The command shown uses the correct pattern: oc secrets link <serviceaccount> <secret-name>. By applying it to the builder service account and the secret, you enable the build process to access the secret as needed. The other commands do unrelated tasks—watching build logs, deleting resources, or changing build triggers—so they don’t accomplish linking a secret to a service account.

Linking a secret to a service account is how you grant pods running under that account access to the secret’s data. In OpenShift, the builder service account is used by build pods, so attaching a secret to the builder SA allows those builds to use credentials stored in the secret (for example, to pull from a private image registry).

The command shown uses the correct pattern: oc secrets link . By applying it to the builder service account and the secret, you enable the build process to access the secret as needed. The other commands do unrelated tasks—watching build logs, deleting resources, or changing build triggers—so they don’t accomplish linking a secret to a service account.