Google Professional Cloud Security Engineer Practice Test 43
Question 420
A Cloud Build pipeline should publish signed artifacts without access to production secrets it never uses. Which approach BEST meets the requirement while respecting the system constraints?
- Configure trusted attestors and require valid attestations bound to the specific image digest.
- Enable and validate applicable Shielded VM secure boot, vTPM and integrity monitoring controls.
- Use an organization Owner principal for every build so configuration never fails.
- Assign a dedicated minimum-privilege build service account with scoped artifact and secret permissions.
Explanation
Correct Answer
D:Assign a dedicated minimum-privilege build service account with scoped artifact and secret permissions. Build-time identities are privileged actors in the software supply chain and require least privilege. Verification should demonstrate that build logs show permitted operations and deny unexpected production resource access.
Incorrect Answers
A:Configure trusted attestors and require valid attestations bound to the specific image digest. This primarily addresses Binary Authorization attestor chain of custody, not the specific Secure Cloud Build execution identity decision. Here, build-time identities are privileged actors in the software supply chain and require least privilege.
B:Enable and validate applicable Shielded VM secure boot, vTPM and integrity monitoring controls. This primarily addresses Shielded VM secure boot integrity, not the specific Secure Cloud Build execution identity decision. Here, build-time identities are privileged actors in the software supply chain and require least privilege.
C:Use an organization Owner principal for every build so configuration never fails. This is an unsafe or ineffective shortcut for Secure Cloud Build execution identity. An overprivileged builder can modify deployment images, secrets and policies beyond its intended pipeline.
Question 421
A VM boots a tampered bootloader after an unauthorized base image modification. Which approach BEST meets the requirement while respecting the system constraints?
- Enable and validate applicable Shielded VM secure boot, vTPM and integrity monitoring controls.
- Configure appropriate organization policy monitoring or posture-management controls at scale.
- Assume enabling OS Login automatically verifies bootloader cryptographic integrity.
- Scan infrastructure-as-code plans against approved security guardrails and require review before deployment.
Explanation
Correct Answer
A:Enable and validate applicable Shielded VM secure boot, vTPM and integrity monitoring controls. Shielded VM features protect portions of the boot process but do not replace guest patching or IAM. Verification should demonstrate that vM integrity events flag unexpected boot changes and approved images pass boot checks.
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 Shielded VM secure boot integrity decision. Here, shielded VM features protect portions of the boot process but do not replace guest patching or IAM.
C:Assume enabling OS Login automatically verifies bootloader cryptographic integrity. This is an unsafe or ineffective shortcut for Shielded VM secure boot integrity. Disabling integrity monitoring can hide unauthorized boot image changes.
D:Scan infrastructure-as-code plans against approved security guardrails and require review before deployment. This primarily addresses Infrastructure as code security validation, not the specific Shielded VM secure boot integrity decision. Here, shielded VM features protect portions of the boot process but do not replace guest patching or IAM.
Question 422
A governance team wants privileged researchers to access raw values but others to receive masked values. Which practical correction or implementation decision is MOST directly appropriate?
- Rename the column email_hash and assume plaintext column contents are automatically masked.
- Validate expiry, method scope and distribution restrictions with test downloaders.
- Test base-table denial and authorized-view results with a separate partner identity.
- Verify policy tag IAM and query behavior for masked versus privileged personas.
Explanation
Correct Answer
D:Verify policy tag IAM and query behavior for masked versus privileged personas. The intended behavior can be checked because test identities receive masked or denied sensitive columns while authorized principals receive approved fields.
Incorrect Answers
A:Rename the column email_hash and assume plaintext column contents are automatically masked. This would not correct the BigQuery column-level policy tags and masking workflow. A dataset viewer role with no column protection may expose sensitive values.
B:Validate expiry, method scope and distribution restrictions with test downloaders. This could help Time-bounded Cloud Storage signed URLs, but it does not resolve the BigQuery column-level policy tags and masking case. Column-level policy tags and data masking govern sensitive columns separately from general dataset access.
C:Test base-table denial and authorized-view results with a separate partner identity. This could help BigQuery authorized views, but it does not resolve the BigQuery column-level policy tags and masking case. Column-level policy tags and data masking govern sensitive columns separately from general dataset access.
Question 423
An exception team requests one legacy key while security requires default prevention elsewhere. An engineer must explain the recommendation for Service account key creation organization policy. Which underlying principle is the MOST accurate?
- Disabling an identity affects all callers using it, not just one label or attached role.
- Organization policy can reduce credential attack surface independently of IAM permissions.
- Identity groups and IAM inheritance require separate checks for effective access.
- Workload federation exchanges external workload identity assertions for short-lived Google credentials.
Explanation
Correct Answer
B:Organization policy can reduce credential attack surface independently of IAM permissions. Therefore the implementation decision is to enforce the applicable organization policy that restricts service account key creation with tightly reviewed exceptions.
Incorrect Answers
A:Disabling an identity affects all callers using it, not just one label or attached role. This describes the separate Service account disabling and dependency mapping mechanism; the present case instead requires Service account key creation organization policy. Broad exemptions undermine a policy intended to eliminate long-lived machine credentials.
C:Identity groups and IAM inheritance require separate checks for effective access. This describes the separate Group-based provisioning audit trail mechanism; the present case instead requires Service account key creation organization policy. Broad exemptions undermine a policy intended to eliminate long-lived machine credentials.
D:Workload federation exchanges external workload identity assertions for short-lived Google credentials. This describes the separate Workload Identity Federation for CI systems mechanism; the present case instead requires Service account key creation organization policy. Broad exemptions undermine a policy intended to eliminate long-lived machine credentials.
Question 424
A developer requests broad organization Owner permissions just to read one BigQuery dataset. An engineer must explain the recommendation for IAM least-privilege role scoping. Which underlying principle is the MOST accurate?
- Access levels describe contextual trust conditions and must be attached to an enforcing service policy.
- Policy inheritance and exceptions must be understood before overriding organization or folder guardrails.
- Usage-based IAM recommendations can highlight excess privilege but need contextual validation.
- IAM allow policy bindings determine which principals may act on resources within a hierarchy.
Explanation
Correct Answer
D:IAM allow policy bindings determine which principals may act on resources within a hierarchy. Therefore the implementation decision is to bind a suitable predefined or reviewed custom IAM role at the narrowest supported scope.
Incorrect Answers
A:Broad primitive roles can expose multiple projects and protected datasets unnecessarily. Access levels describe contextual trust conditions and must be attached to an enforcing service policy.
B:Broad primitive roles can expose multiple projects and protected datasets unnecessarily. Policy inheritance and exceptions must be understood before overriding organization or folder guardrails.
C:Broad primitive roles can expose multiple projects and protected datasets unnecessarily. Usage-based IAM recommendations can highlight excess privilege but need contextual validation.
Question 425
A remote worker is denied because a contextual access level does not match the request. Testing exposes this failure: Merely creating a named access level provides no effective network restriction. Which remediation should be applied FIRST?
- Add narrowly scoped VPC Service Controls ingress or egress rules using principal and service operation constraints.
- Configure Shared VPC with host and service projects and appropriate subnet-use IAM grants.
- Check policy attachments, device posture, corporate IP ranges and denial logs.
- Put the phrase trusted-device into a service account display name and assume Access Context Manager grants access.
Explanation
Correct Answer
C:Check policy attachments, device posture, corporate IP ranges and denial logs. Confirmation requires seeing that access succeeds only from intended device and network contexts with policy logs explaining decisions.
Incorrect Answers
A:Add narrowly scoped VPC Service Controls ingress or egress rules using principal and service operation constraints. It addresses VPC Service Controls ingress egress policy, not the diagnosed Access levels with perimeter identity trust failure. Merely creating a named access level provides no effective network restriction.
B:Configure Shared VPC with host and service projects and appropriate subnet-use IAM grants. It addresses Shared VPC host and service project boundaries, not the diagnosed Access levels with perimeter identity trust failure. Merely creating a named access level provides no effective network restriction.
D:Put the phrase trusted-device into a service account display name and assume Access Context Manager grants access. This retains the Access levels with perimeter identity trust problem. Access levels are contextual expressions that must be consumed by a policy to enforce a boundary.
Question 426
A governance team wants privileged researchers to access raw values but others to receive masked values. Select THREE statements that correctly combine the BigQuery column-level policy tags and masking method with evidence or its governing principle.
- Use dedicated least-privileged runtime identities and harden metadata access according to platform support.
- Issue a supported signed URL with limited method, object, expiry and protected signing identity.
- Configure appropriate BigQuery policy tags or data masking policies and targeted access roles.
- Test identities receive masked or denied sensitive columns while authorized principals receive approved fields.
- Column-level policy tags and data masking govern sensitive columns separately from general dataset access.
- Rename the column email_hash and assume plaintext column contents are automatically masked.
Explanation
Correct Answers
C:Configure appropriate BigQuery policy tags or data masking policies and targeted access roles. This is the intended action for BigQuery column-level policy tags and masking.
D:Test identities receive masked or denied sensitive columns while authorized principals receive approved fields. This is directly observable validation of the BigQuery column-level policy tags and masking result.
E:Column-level policy tags and data masking govern sensitive columns separately from general dataset access. This explains why the implementation and evidence fit together.
Incorrect Answers
A:Use dedicated least-privileged runtime identities and harden metadata access according to platform support. This serves the different Compute metadata exposure hardening objective, not the selected BigQuery column-level policy tags and masking plan. Column-level policy tags and data masking govern sensitive columns separately from general dataset access.
B:Issue a supported signed URL with limited method, object, expiry and protected signing identity. This serves the different Time-bounded Cloud Storage signed URLs objective, not the selected BigQuery column-level policy tags and masking plan. Column-level policy tags and data masking govern sensitive columns separately from general dataset access.
F:Rename the column email_hash and assume plaintext column contents are automatically masked. This is not part of a safe or effective BigQuery column-level policy tags and masking design. A dataset viewer role with no column protection may expose sensitive values.
Question 427
An archive must move older objects to a cheaper class after a defined age. Which approach BEST meets the requirement while respecting the system constraints?
- Configure supported Cloud Storage lifecycle rules with audited age and object conditions.
- Distinguish Google-managed default at-rest encryption from services configured with supported CMEK.
- Select a supported Cloud HSM protection level for the relevant Cloud KMS key.
- Rename a bucket Archive and assume its objects automatically change storage class at day 30.
Explanation
Correct Answer
A:Configure supported Cloud Storage lifecycle rules with audited age and object conditions. Storage lifecycle rules automate object state changes under conditions separate from IAM authorization. Verification should demonstrate that test objects transition or expire according to policy while exempt legal artifacts are preserved.
Incorrect Answers
B:Distinguish Google-managed default at-rest encryption from services configured with supported CMEK. This primarily addresses Default at-rest encryption versus CMEK, not the specific Cloud Storage object lifecycle transition decision. Here, storage lifecycle rules automate object state changes under conditions separate from IAM authorization.
C:Select a supported Cloud HSM protection level for the relevant Cloud KMS key. This primarily addresses Cloud HSM versus software-protected keys, not the specific Cloud Storage object lifecycle transition decision. Here, storage lifecycle rules automate object state changes under conditions separate from IAM authorization.
D:Rename a bucket Archive and assume its objects automatically change storage class at day 30. This is an unsafe or ineffective shortcut for Cloud Storage object lifecycle transition. Broad delete rules can remove records required by retention policy.
Question 428
A research contractor needs aggregate results but must not browse raw health identifiers. An engineer must explain the recommendation for Healthcare data privacy segmentation. Which underlying principle is the MOST accurate?
- Healthcare privacy controls require data minimization, authorization and auditability regardless of infrastructure encryption.
- Build-time identities are privileged actors in the software supply chain and require least privilege.
- Scoping is based on actual data and connected system boundaries rather than arbitrary project names.
- Legal preservation and ordinary object lifecycle deletion are separate data governance requirements.
Explanation
Correct Answer
A:Healthcare privacy controls require data minimization, authorization and auditability regardless of infrastructure encryption. Therefore the implementation decision is to restrict datasets and share only approved de-identified outputs with monitored access controls.
Incorrect Answers
B:Relying on at-rest encryption while exposing raw datasets to all researchers violates least privilege. This describes the separate Secure Cloud Build execution identity mechanism; the present case instead requires Healthcare data privacy segmentation.
C:Relying on at-rest encryption while exposing raw datasets to all researchers violates least privilege. Scoping is based on actual data and connected system boundaries rather than arbitrary project names.
D:Relying on at-rest encryption while exposing raw datasets to all researchers violates least privilege. This describes the separate Legal hold versus lifecycle delete mechanism; the present case instead requires Healthcare data privacy segmentation.
Question 429
A team wants to know whether a signature for image A can authorize a modified image B. Which practical correction or implementation decision is MOST directly appropriate?
- Validate rule conditions, scanning coverage and remediation workflow in a test project.
- Rebuild and modify the test image to confirm signature enforcement and approver separation.
- Test secure boot compatibility and review VM integrity monitoring events.
- Publish the attestor signing key in source control so every developer can self-approve releases.
Explanation
Correct Answer
B:Rebuild and modify the test image to confirm signature enforcement and approver separation. The intended behavior can be checked because the expected digest deploys with a valid attestation while altered bytes are rejected.
Incorrect Answers
A:Validate rule conditions, scanning coverage and remediation workflow in a test project. This could help Security Health Analytics custom finding, but it does not resolve the Binary Authorization attestor chain of custody case. Image digest attestations authorize precisely identified artifacts rather than unrelated mutable labels.
C:Test secure boot compatibility and review VM integrity monitoring events. This could help Shielded VM secure boot integrity, but it does not resolve the Binary Authorization attestor chain of custody case. Image digest attestations authorize precisely identified artifacts rather than unrelated mutable labels.
D:Publish the attestor signing key in source control so every developer can self-approve releases. This would not correct the Binary Authorization attestor chain of custody workflow. Signing only a repository name cannot prove integrity of a changed image digest.
Question 430
Cardholder systems must be isolated from general employee development networks. After the recommended PCI workload network segmentation change is implemented, which observation MOST directly verifies that it works?
- Eligible temporary data expires while protected records reject premature deletion.
- Only explicitly authorized payment-processing flows reach in-scope resources.
- Vulnerable builds are stopped with traceable findings while accepted exceptions are documented.
- Ownership records distinguish customer guest patching and IAM tasks from Google-managed facilities and hardware.
Explanation
Correct Answer
B:Only explicitly authorized payment-processing flows reach in-scope resources. This directly tests whether the PCI workload network segmentation goal was met. PCI segmentation reduces scope and attack surface only when enforced and validated.
Incorrect Answers
A:Eligible temporary data expires while protected records reject premature deletion. This is evidence about Legal hold versus lifecycle delete, not direct proof of the required PCI workload network segmentation behavior. The relevant check is that only explicitly authorized payment-processing flows reach in-scope resources.
C:Vulnerable builds are stopped with traceable findings while accepted exceptions are documented. This is evidence about Continuous integration dependency security gate, not direct proof of the required PCI workload network segmentation behavior. The relevant check is that only explicitly authorized payment-processing flows reach in-scope resources.
D:Ownership records distinguish customer guest patching and IAM tasks from Google-managed facilities and hardware. This is evidence about Cloud shared responsibility service boundaries, not direct proof of the required PCI workload network segmentation behavior. The relevant check is that only explicitly authorized payment-processing flows reach in-scope resources.