Reviewed by Aditya Kumar · Last reviewed 2026-03-24
Architectural options: (1) Service account + JSON key in Jenkins credentials. (2) Workload Identity (Jenkins on GKE)—no keys. Flow: Create SA → download JSON → add to Jenkins → use in GCP plugin or gcloud....
Architectural options: (1) Service account + JSON key in Jenkins credentials. (2) Workload Identity (Jenkins on GKE)—no keys. Flow: Create SA → download JSON → add to Jenkins → use in GCP plugin or gcloud. Best practice: Prefer Workload Identity; restrict SA permissions; rotate keys; separate dev/prod accounts.
Red Flag: Committing JSON keys to Git. Pro-Move: 'We use Workload Identity on GKE—Jenkins assumes SA; zero keys; audit via Cloud IAM.'
According to DataEngPrep.tech, this is one of the most frequently asked Cloud/Tools interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.