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 security operations team is investigating unauthorized modifications made to sensitive cloud storage buckets. The actions were executed directly by a privileged deployment service account. The team needs to trace the authentic originating human principal who initiated the impersonated session and prevent future credential exfiltration risks by enforcing short-lived impersonation workflows enterprise-wide.
Which combination of Cloud Audit Log inspection and Organization Policy enforcement should the security engineer implement?
This option attempts to trace the caller by correlating network IP metadata (callerIp) with third-party Identity Provider (IdP) logs, and applies the iam.allowedPolicyMemberDomains list constraint to restrict IAM role grants to authorized corporate domains.
callerIp is indirect, unreliable, and often obstructed by corporate NAT gateways, proxies, VPNs, or Google Cloud internal IPs. Cloud Audit Logs natively record the exact originating identity within the log entry itself under serviceAccountDelegationInfo without requiring external log correlation.iam.allowedPolicyMemberDomains constraint ensures that external consumer accounts (e.g., @gmail.com) cannot be added to IAM policies. However, authorized corporate users can still create and exfiltrate long-lived service account keys unless key creation is explicitly disabled.requestMetadata.callerIp provides network socket context rather than authenticated IAM identity context.iam.allowedPolicyMemberDomains acts as an IAM boundary filter by domain Customer ID, not a key lifecycle restriction.The requirement focused on blocking external non-corporate accounts from being granted permissions in IAM allow policies across the organization hierarchy.
While IP addresses provide supplementary telemetry during forensic investigations, Google Cloud's IAM architecture provides deterministic cryptographic delegation records directly inside audit logs, making external IP matching unnecessary for impersonation tracking.
This option inspects the policyDelta structure within audit log metadata to examine changes made to IAM allow policies, and enforces the compute.setNewProjectDefaultToZonalDNSOnly constraint on Compute Engine resources.
policyDelta field records additions and deletions of IAM bindings during SetIamPolicy API calls. It does not record runtime operational API calls (such as storage bucket access) or provide information about which user assumed a service account token.compute.setNewProjectDefaultToZonalDNSOnly constraint configures internal DNS behavior for new Compute Engine instances to isolate DNS failure domains. It has no connection to service account governance, credential exfiltration, or impersonation policies.policyDelta only populates when resource IAM policies are modified.compute.setNewProjectDefaultToZonalDNSOnly is an infrastructure availability control, not an access or credential management control.The primary requirement was to audit modifications to project-level IAM permission assignments while enforcing high-reliability internal DNS registration across newly provisioned Compute Engine projects.
Security engineers must distinguish between authorization configuration events (logged with policyDelta) and authentication delegation events (logged with serviceAccountDelegationInfo) when designing audit pipelines in Cloud Logging.
This option relies solely on the top-level principalEmail field in Cloud Audit Logs and enforces the iam.disableCrossProjectServiceAccountUsage organization policy constraint to restrict cross-project service account attachments.
protoPayload.authenticationInfo.principalEmail contains the email address of the impersonated service account itself, not the human user who assumed the identity. Relying on principalEmail alone makes it impossible to distinguish between automated workloads and user-initiated impersonation.iam.disableCrossProjectServiceAccountUsage prevents service accounts in one project from being attached to resources (such as Compute Engine instances) in another project. It does nothing to prevent users from creating and downloading static .json private keys within the local project.principalEmail only shows the active authenticated identity executing the specific API method.serviceAccountDelegationInfo nested array.iam.disableCrossProjectServiceAccountUsage governs cross-boundary resource binding, not key generation or credential lifecycles.The objective was to prevent resources in Project B from attaching a service account created in Project A, while auditing directly executed API calls from a non-impersonated service account.
When investigating security events involving service accounts, checking only principalEmail often leads investigators down a dead end, as all actions appear to originate from the shared service account identity without attribution to individual actors.
This solution pairs deep Cloud Audit Log inspection of the serviceAccountDelegationInfo metadata structure with the organization-wide policy constraint constraints/iam.disableServiceAccountKeyCreation to enforce identity traceability and eliminate static credential leakage.
generateAccessToken), Cloud Audit Logs record the impersonated service account in protoPayload.authenticationInfo.principalEmail. Crucially, the actual originating caller or sequence of delegates is populated in protoPayload.authenticationInfo.serviceAccountDelegationInfo, allowing forensic investigators to pinpoint the exact human user who initiated the action.iam.disableServiceAccountKeyCreation blocks developers and administrators from creating user-managed, downloadable RSA private keys (.json or .p12 files). This mandates the use of short-lived credential generation, identity federation, or direct impersonation patterns, removing long-lived static keys that could otherwise be leaked or stolen from developer workstations.Inspecting serviceAccountDelegationInfo is the only Google Cloud native logging mechanism that captures the full delegation lineage during service account impersonation. Combining this detective control with the preventive guardrail iam.disableServiceAccountKeyCreation achieves full zero-trust credential hygiene by replacing vulnerable static keys with short-lived, fully auditable impersonated credentials.
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