Google Professional Cloud Security Engineer Practice Test 66
Question 650
A compliance reviewer must prove new finance employees received only their assigned Cloud Identity group permissions. After the recommended Group-based provisioning audit trail change is implemented, which observation MOST directly verifies that it works?
- Unauthorized API calls stop and explicitly approved dependent workloads are migrated or remediated.
- The scheduled synchronization creates and updates the intended users without unexpectedly deleting cloud identities.
- Emergency accounts can regain administrative access during an identity-provider outage without being used routinely.
- The group audit trail explains each addition or removal and no unapproved current member remains.
Explanation
Correct Answer
D:The group audit trail explains each addition or removal and no unapproved current member remains. This directly tests whether the Group-based provisioning audit trail goal was met. Identity groups and IAM inheritance require separate checks for effective access.
Incorrect Answers
A:Unauthorized API calls stop and explicitly approved dependent workloads are migrated or remediated. This is evidence about Service account disabling and dependency mapping, not direct proof of the required Group-based provisioning audit trail behavior. The relevant check is that the group audit trail explains each addition or removal and no unapproved current member remains.
B:The scheduled synchronization creates and updates the intended users without unexpectedly deleting cloud identities. This is evidence about Cloud Identity directory synchronization, not direct proof of the required Group-based provisioning audit trail behavior. The relevant check is that the group audit trail explains each addition or removal and no unapproved current member remains.
C:Emergency accounts can regain administrative access during an identity-provider outage without being used routinely. This is evidence about Super administrator emergency access, not direct proof of the required Group-based provisioning audit trail behavior. The relevant check is that the group audit trail explains each addition or removal and no unapproved current member remains.
Question 651
A private application intermittently fails because a higher-priority firewall deny rule matches. If the relevant Firewall rule logging and deny analysis safeguard is omitted, which outcome is the MOST directly associated failure?
- A detector with the wrong scope can miss important projects or overwhelm responders with noise.
- A log sink lacking destination write permission can silently fail central collection.
- Without accurate priority and match review an unrelated allow rule may not resolve a deny.
- Assuming all service data reads are logged by default may leave incident evidence gaps.
Explanation
Correct Answer
C:Without accurate priority and match review an unrelated allow rule may not resolve a deny. Firewall rule logging provides policy decision evidence distinct from basic network flow summaries. The corrective approach is to reproduce a blocked connection and correlate rule logs with effective policy.
Incorrect Answers
A:This failure pattern belongs chiefly to Security Health Analytics custom finding; it is not the failure most directly tested in the Firewall rule logging and deny analysis situation.
B:This failure pattern belongs chiefly to Organization aggregated log sink; it is not the failure most directly tested in the Firewall rule logging and deny analysis situation.
D:This failure pattern belongs chiefly to Data Access Audit Logs enablement and cost; it is not the failure most directly tested in the Firewall rule logging and deny analysis situation.
Question 652
HR onboarding must automatically create employees and disable accounts after approved termination. After the recommended Cloud Identity user lifecycle automation change is implemented, which observation MOST directly verifies that it works?
- Reduced grants preserve necessary calls and clearly document exceptions for rare operations.
- Approved external subjects obtain federated console or API access while unmapped identities are denied.
- Emergency accounts can regain administrative access during an identity-provider outage without being used routinely.
- Newly approved staff gain only intended access while departed workers lose it within the policy window.
Explanation
Correct Answer
D:Newly approved staff gain only intended access while departed workers lose it within the policy window. This directly tests whether the Cloud Identity user lifecycle automation goal was met. Lifecycle controls must revoke identity and group privileges rather than depend solely on removing a laptop.
Incorrect Answers
A:Reduced grants preserve necessary calls and clearly document exceptions for rare operations. This is evidence about Policy Intelligence permission recommendations, not direct proof of the required Cloud Identity user lifecycle automation behavior. The relevant check is that newly approved staff gain only intended access while departed workers lose it within the policy window.
B:Approved external subjects obtain federated console or API access while unmapped identities are denied. This is evidence about Workforce Identity Federation for external workers, not direct proof of the required Cloud Identity user lifecycle automation behavior. The relevant check is that newly approved staff gain only intended access while departed workers lose it within the policy window.
C:Emergency accounts can regain administrative access during an identity-provider outage without being used routinely. This is evidence about Super administrator emergency access, not direct proof of the required Cloud Identity user lifecycle automation behavior. The relevant check is that newly approved staff gain only intended access while departed workers lose it within the policy window.
Question 653
A regulated team needs one role for workload management and another for IAM grants. An engineer must explain the recommendation for IAM separation of security duties. Which underlying principle is the MOST accurate?
- IAM grants propagate downward through the Google Cloud resource hierarchy unless constrained by relevant controls.
- Separation of duties limits privilege escalation and tampering with oversight controls.
- IAM allow policy bindings determine which principals may act on resources within a hierarchy.
- Usage-based IAM recommendations can highlight excess privilege but need contextual validation.
Explanation
Correct Answer
B:Separation of duties limits privilege escalation and tampering with oversight controls. Therefore the implementation decision is to split deployment, access-policy editing and security evidence administration among distinct identities.
Incorrect Answers
A:IAM grants propagate downward through the Google Cloud resource hierarchy unless constrained by relevant controls. This describes the separate Organization hierarchy and inherited roles mechanism; the present case instead requires IAM separation of security duties. Granting developers project Owner may also let them modify the controls evaluating their work.
C:IAM allow policy bindings determine which principals may act on resources within a hierarchy. This describes the separate IAM least-privilege role scoping mechanism; the present case instead requires IAM separation of security duties. Granting developers project Owner may also let them modify the controls evaluating their work.
D:Usage-based IAM recommendations can highlight excess privilege but need contextual validation. This describes the separate Policy Intelligence permission recommendations mechanism; the present case instead requires IAM separation of security duties. Granting developers project Owner may also let them modify the controls evaluating their work.
Question 654
A GitHub Actions pipeline must push artifacts without storing a long-lived Google service account key. If the relevant Workload Identity Federation for CI systems safeguard is omitted, which outcome is the MOST directly associated failure?
- A provider trusting every repository or AWS role can open artifact publishing to attackers.
- Granting sensitive cloud permissions to every node can let unrelated pods inherit excessive access.
- Broad exemptions undermine a policy intended to eliminate long-lived machine credentials.
- Unverified group automation may silently grant inherited IAM roles to unintended principals.
Explanation
Correct Answer
A:A provider trusting every repository or AWS role can open artifact publishing to attackers. Workload federation exchanges external workload identity assertions for short-lived Google credentials. The corrective approach is to verify issuer, audience, attribute mapping and condition against good and bad test tokens.
Incorrect Answers
B:This failure pattern belongs chiefly to GKE workload identity binding; it is not the failure most directly tested in the Workload Identity Federation for CI systems situation.
C:This failure pattern belongs chiefly to Service account key creation organization policy; it is not the failure most directly tested in the Workload Identity Federation for CI systems situation.
D:This failure pattern belongs chiefly to Programmatic group membership governance; it is not the failure most directly tested in the Workload Identity Federation for CI systems situation.
Question 655
A contractor's contract ends while their group grants access to restricted projects. An engineer must explain the recommendation for Cloud Identity user lifecycle automation. Which underlying principle is the MOST accurate?
- Identity groups and IAM inheritance require separate checks for effective access.
- Lifecycle controls must revoke identity and group privileges rather than depend solely on removing a laptop.
- Impersonation is an explicit IAM privilege and issues temporary credentials for another principal.
- Super administrators have organization-wide identity privileges that require heightened protection and auditing.
Explanation
Correct Answer
B:Lifecycle controls must revoke identity and group privileges rather than depend solely on removing a laptop. Therefore the implementation decision is to integrate the authoritative lifecycle source with managed user provisioning, group removal and deprovisioning controls.
Incorrect Answers
A:Orphan accounts and retained group memberships can expose projects after employment ends. Identity groups and IAM inheritance require separate checks for effective access.
C:Orphan accounts and retained group memberships can expose projects after employment ends. This describes the separate Service account impersonation and token creation mechanism; the present case instead requires Cloud Identity user lifecycle automation.
D:Orphan accounts and retained group memberships can expose projects after employment ends. This describes the separate Super administrator emergency access mechanism; the present case instead requires Cloud Identity user lifecycle automation.
Question 656
A production project requests an emergency exception to a centrally enforced policy. After the recommended Hierarchy-scoped exception and policy rollback change is implemented, which observation MOST directly verifies that it works?
- Unapproved VMs cannot acquire public IP addresses while approved exceptions are recorded.
- The specific approved project works while other descendants remain protected by the broader constraint.
- Approved requests yield bounded temporary privileges and unapproved users cannot self-elevate.
- Child project effective permissions and policy restrictions match the documented parent hierarchy.
Explanation
Correct Answer
B:The specific approved project works while other descendants remain protected by the broader constraint. This directly tests whether the Hierarchy-scoped exception and policy rollback goal was met. Policy inheritance and exceptions must be understood before overriding organization or folder guardrails.
Incorrect Answers
A:Unapproved VMs cannot acquire public IP addresses while approved exceptions are recorded. This is evidence about Restricting external IPv4 addresses through org policy, not direct proof of the required Hierarchy-scoped exception and policy rollback behavior. The relevant check is that the specific approved project works while other descendants remain protected by the broader constraint.
C:Approved requests yield bounded temporary privileges and unapproved users cannot self-elevate. This is evidence about Privileged Access Manager just-in-time approval, not direct proof of the required Hierarchy-scoped exception and policy rollback behavior. The relevant check is that the specific approved project works while other descendants remain protected by the broader constraint.
D:Child project effective permissions and policy restrictions match the documented parent hierarchy. This is evidence about Organization hierarchy and inherited roles, not direct proof of the required Hierarchy-scoped exception and policy rollback behavior. The relevant check is that the specific approved project works while other descendants remain protected by the broader constraint.
Question 657
Security wants evidence for why some cross-project connections are rejected. Which practical correction or implementation decision is MOST directly appropriate?
- Test logging coverage for chosen services and handle high-volume sink budgeting.
- Validate logs for a known policy change and protect log access from the actor being audited.
- Reproduce a blocked connection and correlate rule logs with effective policy.
- Change a VM hostname and assume the firewall priority order changes automatically.
Explanation
Correct Answer
C:Reproduce a blocked connection and correlate rule logs with effective policy. The intended behavior can be checked because log entries identify matching policy, direction, source, destination and disposition.
Incorrect Answers
A:Test logging coverage for chosen services and handle high-volume sink budgeting. This could help Data Access Audit Logs enablement and cost, but it does not resolve the Firewall rule logging and deny analysis case. Firewall rule logging provides policy decision evidence distinct from basic network flow summaries.
B:Validate logs for a known policy change and protect log access from the actor being audited. This could help Admin Activity Audit Logs provenance, but it does not resolve the Firewall rule logging and deny analysis case. Firewall rule logging provides policy decision evidence distinct from basic network flow summaries.
D:Change a VM hostname and assume the firewall priority order changes automatically. This would not correct the Firewall rule logging and deny analysis workflow. Without accurate priority and match review an unrelated allow rule may not resolve a deny.
Question 658
A team wants to know whether a signature for image A can authorize a modified image B. Select THREE statements that correctly combine the Binary Authorization attestor chain of custody method with evidence or its governing principle.
- Publish the attestor signing key in source control so every developer can self-approve releases.
- Image digest attestations authorize precisely identified artifacts rather than unrelated mutable labels.
- Use supported VM Manager patch jobs and compliance views with approved maintenance scheduling.
- Configure trusted attestors and require valid attestations bound to the specific image digest.
- The expected digest deploys with a valid attestation while altered bytes are rejected.
- Configure a supported Security Health Analytics custom module or SCC posture detector with scoped rule logic.
Explanation
Correct Answers
B:Image digest attestations authorize precisely identified artifacts rather than unrelated mutable labels. This explains why the implementation and evidence fit together.
D:Configure trusted attestors and require valid attestations bound to the specific image digest. This is the intended action for Binary Authorization attestor chain of custody.
E:The expected digest deploys with a valid attestation while altered bytes are rejected. This is directly observable validation of the Binary Authorization attestor chain of custody result.
Incorrect Answers
A:Publish the attestor signing key in source control so every developer can self-approve releases. This is not part of a safe or effective Binary Authorization attestor chain of custody design. Signing only a repository name cannot prove integrity of a changed image digest.
C:Use supported VM Manager patch jobs and compliance views with approved maintenance scheduling. This serves the different VM Manager patch orchestration objective, not the selected Binary Authorization attestor chain of custody plan. Image digest attestations authorize precisely identified artifacts rather than unrelated mutable labels.
F:Configure a supported Security Health Analytics custom module or SCC posture detector with scoped rule logic. This serves the different Security Health Analytics custom finding objective, not the selected Binary Authorization attestor chain of custody plan. Image digest attestations authorize precisely identified artifacts rather than unrelated mutable labels.
Question 659
A control owner needs reproducible evidence rather than screenshots of one administrator's current console. Testing exposes this failure: Saving only a final green dashboard screenshot may miss earlier violations. Which remediation should be applied FIRST?
- Reconcile policy changes, findings, tickets and logs for the sampled time period.
- Map controls to documented incident runbooks, test outcomes and preserved audit logs.
- Backdate one Cloud Console screenshot and call it continuous quarterly access-review evidence.
- Review available Access Transparency logs alongside Cloud Audit Logs for the appropriate services.
Explanation
Correct Answer
A:Reconcile policy changes, findings, tickets and logs for the sampled time period. Confirmation requires seeing that evidence samples demonstrate control operation across the review period and are tamper resistant.
Incorrect Answers
B:Map controls to documented incident runbooks, test outcomes and preserved audit logs. It addresses SOC control evidence and incident workflow, not the diagnosed Audit evidence collection and attestation failure. Saving only a final green dashboard screenshot may miss earlier violations.
C:Backdate one Cloud Console screenshot and call it continuous quarterly access-review evidence. This retains the Audit evidence collection and attestation problem. Continuous control effectiveness requires time-based evidence, not a one-time static claim.
D:Review available Access Transparency logs alongside Cloud Audit Logs for the appropriate services. It addresses Access Transparency provider audit visibility, not the diagnosed Audit evidence collection and attestation failure. Saving only a final green dashboard screenshot may miss earlier violations.
Question 660
A GKE cluster must run only approved container images built by its controlled pipeline. Which approach BEST meets the requirement while respecting the system constraints?
- Enable Binary Authorization enforcement on GKE with an appropriate signed attestation policy.
- Configure appropriate organization policy monitoring or posture-management controls at scale.
- Bind workload-specific Kubernetes subjects to approved Google Cloud resource roles.
- Rename a malicious image to approved:latest and assume its tag is equivalent to a signed attestation.
Explanation
Correct Answer
A:Enable Binary Authorization enforcement on GKE with an appropriate signed attestation policy. Binary Authorization checks deployment policy and attestation against image identity rather than trusting a mutable tag. Verification should demonstrate that images lacking required attestations are rejected at deployment while approved digests are allowed.
Incorrect Answers
B:Configure appropriate organization policy monitoring or posture-management controls at scale. This primarily addresses Custom organization policy drift monitoring, not the specific Binary Authorization GKE admission decision. Here, binary Authorization checks deployment policy and attestation against image identity rather than trusting a mutable tag.
C:Bind workload-specific Kubernetes subjects to approved Google Cloud resource roles. This primarily addresses GKE Workload Identity for deployment runtime, not the specific Binary Authorization GKE admission decision. Here, binary Authorization checks deployment policy and attestation against image identity rather than trusting a mutable tag.
D:Rename a malicious image to approved:latest and assume its tag is equivalent to a signed attestation. This is an unsafe or ineffective shortcut for Binary Authorization GKE admission. Without deploy enforcement a registry push alone may let unreviewed images run.