Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A multinational enterprise is hardening its Google Cloud environment against identity compromise and unauthorized privilege escalation. The security operations team identified that attackers might attempt to chain service account impersonations or exploit dormant and default service accounts to perform unauthorized administrative actions. The team needs to establish a comprehensive strategy to meet the following requirements:
Which combination of controls and tools should the security engineer implement?
This option suggests using Web Security Scanner (WSS) against Google Cloud APIs, wrapping the IAM service in VPC Service Controls (VPC SC) perimeters, and relying on OS Login 2FA to prevent service account key generation.
gcloud iam service-accounts keys create via Cloud Shell, the Cloud Console, or local developer workstations.The primary requirement were securing SSH bastion host access against compromised credentials while testing public-facing web applications for OWASP Top 10 web vulnerabilities.
This solution combines Security Command Center (SCC) Event Threat Detection (ETD), Google Cloud Organization Policy Service, and IAM Recommender to establish end-to-end detection, prevention, and remediation for service account security.
Privilege Escalation: Anomalous Multistep Service Account Delegation for Admin Activity and Privilege Escalation: Impersonation Role Granted for Dormant Service Account. It analyzes the delegation chain, identifying the initial caller and intermediary impersonated principals.iam.disableServiceAccountKeyCreation at the organization root blocks users and automation pipelines from generating user-managed private key files (.json), forcing workloads to use secure, short-lived tokens and workload identity federation.This approach directly aligns with Google Cloud security best practices by pairing preventive guardrails (Organization Policies) with continuous runtime threat detection (SCC Event Threat Detection) and intelligent rightsizing (IAM Recommender).
This option proposes using VPC Flow Logs and Cloud IDS for monitoring IAM delegation, enforcing CMEK-related organization policies to block key creation, and using custom scripts for lifecycle management.
constraints/gcp.restrictNonCmekServices constraint enforces Customer-Managed Encryption Keys (CMEK) on supported Google Cloud services; it has no effect on preventing user-managed service account key creation.The primary goal were detecting network-based lateral movement within private compute subnets and enforcing encryption key compliance across storage systems.
This option suggests dropping Admin Activity logs to save ingestion costs, delegating key creation permissions through the Service Account Key Admin (roles/iam.serviceAccountKeyAdmin) role with conditions, and disabling Google-managed service agents.
roles/iam.serviceAccountKeyAdmin role facilitates the creation of long-lived service account keys rather than preventing their generation.The objective was granting developers self-service key rotation within tightly defined testing environments while deliberately bypassing centralized organizational policies.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated