Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
A production microservice running on Cloud Run begins throwing intermittent HTTP 403 Forbidden runtime exceptions when attempting to integrate with downstream Google Cloud storage services. A recent security update introduced both VPC Service Controls perimeters and revised identity policies across service accounts. You need to isolate whether the integration failures originate from service account IAM permission gaps or VPC Service Controls perimeter restrictions, while identifying the exact caller identity and requested method.
Which troubleshooting strategy should you use to isolate the root cause?
protopayload_auditlog attributes, including authenticationInfo.principalEmail, methodName, resource.labels.service, and metadataJson.violationReason.Cloud Audit Logs capture detailed system and caller interactions across Google Cloud services by recording structured JSON payloads inside protopayload_auditlog. When external service integration failures or permission denials occur, Google Cloud records the full context of the invocation—including the principal, requested method, target resource, and specific denial reasons—into cloudaudit_googleapis_com_policy and related audit log streams.
protopayload_auditlog.authenticationInfo.principalEmail reveals the exact runtime service account identity initiating the API request, while protopayload_auditlog.methodName identifies the exact API method invoked.metadataJson.violationReason and checking whether a SERVICE_NOT_ALLOWED_FROM_VPC or perimeter boundary block occurred allows engineers to definitively differentiate between VPC Service Controls policy blocks and native IAM permission denied errors.resource.labels.service specifies which protected API was accessed, allowing immediate correlation with the application's external integration logic.metadataJson.dryRun).Directly inspecting structured audit log payloads provides unambiguous root-cause isolation without modifying running container code or guessing between IAM permission errors and VPC-SC perimeter denials.
Event Threat Detection is a built-in detection engine within Security Command Center that automatically analyzes stream logs (such as Cloud Logging and Cloud Audit Logs) for indicators of compromise, security threats, anomalous access patterns, and unauthorized privilege escalation.
Persistence: Unmanaged Account Granted Sensitive Role detects malicious persistence mechanisms where an unknown external account is granted elevated privileges. It does not address legitimate microservice integration failures or missing IAM permissions.Security operations detected that an unauthorized consumer Gmail address was added to an organizational IAM policy and needed to investigate suspicious account activity.
Cloud Infrastructure Entitlement Management (CIEM) in Security Command Center is designed to identify and remediate over-privileged identities, focusing on federated identities (such as Entra ID, Okta, and on-premises Active Directory) that have excess permissions on cloud resources.
methodName, callerIp, violationReason) necessary to troubleshoot failing API calls in real time.The objective was to perform a proactive compliance audit across multicloud federated accounts to discover and reduce dormant or excessive permissions assigned to external users.
iam.disableServiceAccountKeyCreation organization policy constraint across the folder to force Cloud Run to use short-lived OAuth tokens.The iam.disableServiceAccountKeyCreation constraint is an Organization Policy rule that blocks users and administrators from generating long-lived, downloadable JSON private service account keys. This enforces the security best practice of using ephemeral identity credentials and metadata-derived OAuth tokens.
The organization wanted to prevent developers from downloading static private key credentials to local workstations to mitigate credential leakage risks.
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