Google Professional Cloud Security Engineer Practice Test 21
Question 200
An internal application requests broad Google API scopes solely to read a small approved dataset. Which approach BEST meets the requirement while respecting the system constraints?
- Configure supported account session controls and reauthentication policies for sensitive user groups.
- Trust every signed bearer token regardless of audience and permitted OAuth scopes.
- Stage authentication changes with a fallback path and monitored test accounts before enforcement.
- Validate token audience and issuer and request only the permissions necessary for the application.
Explanation
Correct Answer
D:Validate token audience and issuer and request only the permissions necessary for the application. Token validity includes intended recipient and authorization context, not just signature format. Verification should demonstrate that tokens for the wrong audience are rejected and users are not prompted for unrelated scopes.
Incorrect Answers
A:Configure supported account session controls and reauthentication policies for sensitive user groups. This primarily addresses Session duration and reauthentication policy, not the specific OAuth audience and minimum scopes decision. Here, token validity includes intended recipient and authorization context, not just signature format.
B:Trust every signed bearer token regardless of audience and permitted OAuth scopes. This is an unsafe or ineffective shortcut for OAuth audience and minimum scopes. Overbroad scopes or missing audience checks can expose unrelated APIs.
C:Stage authentication changes with a fallback path and monitored test accounts before enforcement. This primarily addresses Identity-provider failover and recovery testing, not the specific OAuth audience and minimum scopes decision. Here, token validity includes intended recipient and authorization context, not just signature format.
Question 201
A transformation pipeline must preserve a defined character alphabet while securing values. Which practical correction or implementation decision is MOST directly appropriate?
- Validate format rules, deterministic behavior where required and cryptographic key permissions.
- Inventory object ACL behavior, test IAM transitions and apply public access prevention where required.
- Verify policy tag IAM and query behavior for masked versus privileged personas.
- Replace the last digit of the identifier and call it strong format-preserving encryption.
Explanation
Correct Answer
A:Validate format rules, deterministic behavior where required and cryptographic key permissions. The intended behavior can be checked because encrypted identifiers follow the required format and only approved services can reverse them.
Incorrect Answers
B:Inventory object ACL behavior, test IAM transitions and apply public access prevention where required. This could help Cloud Storage uniform bucket-level permissions, but it does not resolve the Format-preserving encryption data handling case. Format-preserving encryption retains structural constraints but is not the same as plain-text masking.
C:Verify policy tag IAM and query behavior for masked versus privileged personas. This could help BigQuery column-level policy tags and masking, but it does not resolve the Format-preserving encryption data handling case. Format-preserving encryption retains structural constraints but is not the same as plain-text masking.
D:Replace the last digit of the identifier and call it strong format-preserving encryption. This would not correct the Format-preserving encryption data handling workflow. Poor tweak or key management can weaken confidentiality and cause inconsistent decryptability.
Question 202
Central security needs to deny unauthorized internet egress across several VPC projects. After the recommended Hierarchical Cloud NGFW policy ordering change is implemented, which observation MOST directly verifies that it works?
- Packet tests and firewall logs show expected policy evaluation for allowed and blocked flows.
- Approved workloads receive valid certificates and unauthorized principals cannot issue new ones.
- Only approved cross-boundary calls succeed and unrelated principals remain denied.
- Restricted clients receive the expected filtered response without affecting unrelated resolvers.
Explanation
Correct Answer
A:Packet tests and firewall logs show expected policy evaluation for allowed and blocked flows. This directly tests whether the Hierarchical Cloud NGFW policy ordering goal was met. Hierarchical firewall policies can govern descendant networks independently of local VPC rule intent.
Incorrect Answers
B:Approved workloads receive valid certificates and unauthorized principals cannot issue new ones. This is evidence about Certificate Authority Service private PKI, not direct proof of the required Hierarchical Cloud NGFW policy ordering behavior. The relevant check is that packet tests and firewall logs show expected policy evaluation for allowed and blocked flows.
C:Only approved cross-boundary calls succeed and unrelated principals remain denied. This is evidence about VPC Service Controls ingress egress policy, not direct proof of the required Hierarchical Cloud NGFW policy ordering behavior. The relevant check is that packet tests and firewall logs show expected policy evaluation for allowed and blocked flows.
D:Restricted clients receive the expected filtered response without affecting unrelated resolvers. This is evidence about Cloud DNS response policy filtering, not direct proof of the required Hierarchical Cloud NGFW policy ordering behavior. The relevant check is that packet tests and firewall logs show expected policy evaluation for allowed and blocked flows.
Question 203
An application requires key usage to stop when an external approval service revokes the key. Select TWO statements that correctly combine the External Key Manager custody method with evidence or its governing principle.
- The service respects external key availability and data-access behavior under revocation tests.
- Use supported Cloud External Key Manager integration and design for external availability and permission boundaries.
- Assume a Google default encryption key can be revoked from an unrelated external key server.
- Select a supported Cloud HSM protection level for the relevant Cloud KMS key.
- Separate key administration permissions from cryptographic use and decryption permissions.
Explanation
Correct Answers
A:The service respects external key availability and data-access behavior under revocation tests. This is directly observable validation of the External Key Manager custody result.
B:Use supported Cloud External Key Manager integration and design for external availability and permission boundaries. This is the intended action for External Key Manager custody.
Incorrect Answers
C:Assume a Google default encryption key can be revoked from an unrelated external key server. This is not part of a safe or effective External Key Manager custody design. Unavailable external keys can make protected cloud data inaccessible even when IAM allows access.
D:Select a supported Cloud HSM protection level for the relevant Cloud KMS key. This serves the different Cloud HSM versus software-protected keys objective, not the selected External Key Manager custody plan. Cloud EKM shifts external key custody and introduces dependency on external key-management availability.
E:Separate key administration permissions from cryptographic use and decryption permissions. This serves the different Cloud KMS crypto key role separation objective, not the selected External Key Manager custody plan. Cloud EKM shifts external key custody and introduces dependency on external key-management availability.
Question 204
A data export must remove sensitive strings while preserving surrounding diagnostic context. Testing exposes this failure: Overly broad or incomplete detectors can destroy useful logs or leave sensitive fields exposed. Which remediation should be applied FIRST?
- Issue a supported signed URL with limited method, object, expiry and protected signing identity.
- Run Sensitive Data Protection inspection using appropriate infoTypes and controlled discovery scope.
- Use a public regex that matches only one test phone number and certify all patient data sanitized.
- Test precision and recall with representative known and unknown PII formats.
Explanation
Correct Answer
D:Test precision and recall with representative known and unknown PII formats. Confirmation requires seeing that output removes intended values and controlled inspection confirms no exposed matches in sample logs.
Incorrect Answers
A:Issue a supported signed URL with limited method, object, expiry and protected signing identity. It addresses Time-bounded Cloud Storage signed URLs, not the diagnosed Sensitive Data Protection inspection redaction failure. Overly broad or incomplete detectors can destroy useful logs or leave sensitive fields exposed.
B:Run Sensitive Data Protection inspection using appropriate infoTypes and controlled discovery scope. It addresses Sensitive Data Protection PII inspection, not the diagnosed Sensitive Data Protection inspection redaction failure. Overly broad or incomplete detectors can destroy useful logs or leave sensitive fields exposed.
C:Use a public regex that matches only one test phone number and certify all patient data sanitized. This retains the Sensitive Data Protection inspection redaction problem. Redaction obscures selected content but requires correct detector configuration and validation.
Question 205
A security engineer needs to let one analyst view logs in a single project. If the relevant IAM least-privilege role scoping safeguard is omitted, which outcome is the MOST directly associated failure?
- A malformed condition or unsupported attribute may broaden or unexpectedly block access.
- Orphan accounts and retained group memberships can expose projects after employment ends.
- An overly broad deny rule can block critical service agents and break production operations.
- Broad primitive roles can expose multiple projects and protected datasets unnecessarily.
Explanation
Correct Answer
D:Broad primitive roles can expose multiple projects and protected datasets unnecessarily. IAM allow policy bindings determine which principals may act on resources within a hierarchy. The corrective approach is to use Policy Troubleshooter and negative tests to verify effective role scope.
Incorrect Answers
A:A malformed condition or unsupported attribute may broaden or unexpectedly block access. This failure pattern belongs chiefly to Conditional IAM access restrictions; it is not the failure most directly tested in the IAM least-privilege role scoping situation. Broad primitive roles can expose multiple projects and protected datasets unnecessarily.
B:Orphan accounts and retained group memberships can expose projects after employment ends. This failure pattern belongs chiefly to Cloud Identity user lifecycle automation; it is not the failure most directly tested in the IAM least-privilege role scoping situation. Broad primitive roles can expose multiple projects and protected datasets unnecessarily.
C:An overly broad deny rule can block critical service agents and break production operations. This failure pattern belongs chiefly to IAM Deny policy enforcement; it is not the failure most directly tested in the IAM least-privilege role scoping situation. Broad primitive roles can expose multiple projects and protected datasets unnecessarily.
Question 206
An analyst wants automated detection of anomalous API activity rather than reviewing every audit event manually. Select TWO statements that correctly combine the Event Threat Detection behavior monitoring method with evidence or its governing principle.
- Simulated suspicious behavior produces a traceable finding without treating every normal request as malicious.
- Set a project label to event-threat-detection and assume threat monitoring is active.
- Enable appropriate firewall policy rule logging and inspect effective rules for denied connections.
- Enable and tune supported Event Threat Detection signals using eligible security telemetry.
- Configure Cloud Logging bucket retention controls and appropriate restricted management privileges.
Explanation
Correct Answers
A:Simulated suspicious behavior produces a traceable finding without treating every normal request as malicious. This is directly observable validation of the Event Threat Detection behavior monitoring result.
D:Enable and tune supported Event Threat Detection signals using eligible security telemetry. This is the intended action for Event Threat Detection behavior monitoring.
Incorrect Answers
B:Set a project label to event-threat-detection and assume threat monitoring is active. This is not part of a safe or effective Event Threat Detection behavior monitoring design. Disabling relevant audit data can limit the ability to reconstruct malicious behavior.
C:Enable appropriate firewall policy rule logging and inspect effective rules for denied connections. This serves the different Firewall rule logging and deny analysis objective, not the selected Event Threat Detection behavior monitoring plan. Threat detection derives signals from audit and operational events, distinct from posture-only scanning.
E:Configure Cloud Logging bucket retention controls and appropriate restricted management privileges. This serves the different Log bucket retention and immutable audit evidence objective, not the selected Event Threat Detection behavior monitoring plan. Threat detection derives signals from audit and operational events, distinct from posture-only scanning.
Question 207
An application team discovers a service account JSON key committed to a shared repository. If the relevant Service account key inventory and exposure response safeguard is omitted, which outcome is the MOST directly associated failure?
- Granting sensitive cloud permissions to every node can let unrelated pods inherit excessive access.
- An overly permissive domain exception can enable unauthorized external role assignments.
- Broad exemptions undermine a policy intended to eliminate long-lived machine credentials.
- Rotating only a repository secret variable leaves an already leaked key valid.
Explanation
Correct Answer
D:Rotating only a repository secret variable leaves an already leaked key valid. Long-lived service account keys are exportable credentials that require strict inventory and incident response. The corrective approach is to validate key disablement through audit logs and test legitimate replacement authentication.
Incorrect Answers
A:This failure pattern belongs chiefly to GKE workload identity binding; it is not the failure most directly tested in the Service account key inventory and exposure response situation.
B:This failure pattern belongs chiefly to Restricting allowed IAM member domains; it is not the failure most directly tested in the Service account key inventory and exposure response situation.
C:This failure pattern belongs chiefly to Service account key creation organization policy; it is not the failure most directly tested in the Service account key inventory and exposure response situation.
Question 208
A governance team wants privileged researchers to access raw values but others to receive masked values. An engineer must explain the recommendation for BigQuery column-level policy tags and masking. Which underlying principle is the MOST accurate?
- Signed URLs delegate bounded access through a signature rather than lasting IAM grants to each downloader.
- Column-level policy tags and data masking govern sensitive columns separately from general dataset access.
- Prompt-injection defenses require trusted instruction boundaries and downstream authorization, not only content filters.
- Minimization and lifecycle governance reduce residual sensitive-data exposure beyond IAM encryption.
Explanation
Correct Answer
B:Column-level policy tags and data masking govern sensitive columns separately from general dataset access. Therefore the implementation decision is to configure appropriate BigQuery policy tags or data masking policies and targeted access roles.
Incorrect Answers
A:Signed URLs delegate bounded access through a signature rather than lasting IAM grants to each downloader. This describes the separate Time-bounded Cloud Storage signed URLs mechanism; the present case instead requires BigQuery column-level policy tags and masking. A dataset viewer role with no column protection may expose sensitive values.
C:Prompt-injection defenses require trusted instruction boundaries and downstream authorization, not only content filters. This describes the separate Prompt injection and retrieved data boundary mechanism; the present case instead requires BigQuery column-level policy tags and masking. A dataset viewer role with no column protection may expose sensitive values.
D:Minimization and lifecycle governance reduce residual sensitive-data exposure beyond IAM encryption. This describes the separate Sensitive data retention and data lifecycle mechanism; the present case instead requires BigQuery column-level policy tags and masking. A dataset viewer role with no column protection may expose sensitive values.
Question 209
A security team needs to limit what privileges an exposed workload identity could use. Which practical correction or implementation decision is MOST directly appropriate?
- Test direct table SQL and alternative query paths for each intended regional principal.
- Verify policy tag IAM and query behavior for masked versus privileged personas.
- Test workload permissions, request paths and software isolation under least privilege.
- Assume hiding the metadata IP address in application comments prevents compromised code from reaching it.
Explanation
Correct Answer
C:Test workload permissions, request paths and software isolation under least privilege. The intended behavior can be checked because the workload retains required API access without broad metadata-derived permissions.
Incorrect Answers
A:Test direct table SQL and alternative query paths for each intended regional principal. This could help BigQuery row-level access policy, but it does not resolve the Compute metadata exposure hardening case. Metadata server tokens reflect attached workload identity and must be protected from untrusted code paths.
B:Verify policy tag IAM and query behavior for masked versus privileged personas. This could help BigQuery column-level policy tags and masking, but it does not resolve the Compute metadata exposure hardening case. Metadata server tokens reflect attached workload identity and must be protected from untrusted code paths.
D:Assume hiding the metadata IP address in application comments prevents compromised code from reaching it. This would not correct the Compute metadata exposure hardening workflow. An instance with Owner-level credentials makes metadata token theft especially damaging.
Question 210
A service account can read a resource in project A but fails in project B despite similar role names. Which approach BEST meets the requirement while respecting the system constraints?
- Grant resource roles to centrally governed groups and separately control membership administration.
- Automatically add project Editor whenever a user reports permission denied without inspecting policy.
- Split deployment, access-policy editing and security evidence administration among distinct identities.
- Inspect effective policies with Policy Troubleshooter, Policy Analyzer and relevant audit logs.
Explanation
Correct Answer
D:Inspect effective policies with Policy Troubleshooter, Policy Analyzer and relevant audit logs. Effective IAM authorization depends on inheritance, permission, conditions and explicit deny interactions. Verification should demonstrate that the identified rule explains successful and failed operations for the exact principal and resource.
Incorrect Answers
A:Grant resource roles to centrally governed groups and separately control membership administration. This primarily addresses Group-based IAM authorization, not the specific IAM effective permission troubleshooting decision. Here, effective IAM authorization depends on inheritance, permission, conditions and explicit deny interactions.
B:Automatically add project Editor whenever a user reports permission denied without inspecting policy. This is an unsafe or ineffective shortcut for IAM effective permission troubleshooting. Guessing from only the project IAM screen may overlook higher-level policies.
C:Split deployment, access-policy editing and security evidence administration among distinct identities. This primarily addresses IAM separation of security duties, not the specific IAM effective permission troubleshooting decision. Here, effective IAM authorization depends on inheritance, permission, conditions and explicit deny interactions.