Google Professional Cloud Security Engineer Practice Test 69
Question 680
A partner must download one exported archive without receiving permanent bucket IAM membership. If the relevant Time-bounded Cloud Storage signed URLs safeguard is omitted, which outcome is the MOST directly associated failure?
- A widely forwarded valid signed URL can be used by others until expiry unless additional controls exist.
- Trusting all clients solely because they are inside the VPC may allow lateral impersonation.
- A dataset viewer role with no column protection may expose sensitive values.
- Ignoring legacy ACL consumers may break clients during migration.
Explanation
Correct Answer
A:A widely forwarded valid signed URL can be used by others until expiry unless additional controls exist. Signed URLs delegate bounded access through a signature rather than lasting IAM grants to each downloader. The corrective approach is to validate expiry, method scope and distribution restrictions with test downloaders.
Incorrect Answers
B:This failure pattern belongs chiefly to Mutual TLS for service-to-service identity; it is not the failure most directly tested in the Time-bounded Cloud Storage signed URLs situation.
C:This failure pattern belongs chiefly to BigQuery column-level policy tags and masking; it is not the failure most directly tested in the Time-bounded Cloud Storage signed URLs situation.
D:This failure pattern belongs chiefly to Cloud Storage uniform bucket-level permissions; it is not the failure most directly tested in the Time-bounded Cloud Storage signed URLs situation.
Question 681
A web tier must contact an API tier while database connections should originate only from the API tier. If the relevant N-tier east-west network segmentation safeguard is omitted, which outcome is the MOST directly associated failure?
- Designing a three-network hub by peering alone may leave intended routes unreachable.
- Advertising every private prefix without policy limits can enable lateral access from on-premises.
- One wide internal allow rule can turn a frontend breach into database reachability.
- Treating an allow-on-443 rule as deep content validation leaves application threats unexamined.
Explanation
Correct Answer
C:One wide internal allow rule can turn a frontend breach into database reachability. Lateral movement defenses require explicit east-west traffic restrictions independent of perimeter ingress. The corrective approach is to test an explicit flow matrix for allowed and denied source-destination pairs.
Incorrect Answers
A:Designing a three-network hub by peering alone may leave intended routes unreachable. This failure pattern belongs chiefly to VPC Network Peering transitivity limits; it is not the failure most directly tested in the N-tier east-west network segmentation situation. One wide internal allow rule can turn a frontend breach into database reachability.
B:This failure pattern belongs chiefly to Hybrid network segmentation policy placement; it is not the failure most directly tested in the N-tier east-west network segmentation situation.
D:Treating an allow-on-443 rule as deep content validation leaves application threats unexamined. This failure pattern belongs chiefly to Cloud NGFW application-layer inspection; it is not the failure most directly tested in the N-tier east-west network segmentation situation. One wide internal allow rule can turn a frontend breach into database reachability.
Question 682
A new service perimeter could block hundreds of cross-project BigQuery queries. If the relevant VPC Service Controls dry-run evaluation safeguard is omitted, which outcome is the MOST directly associated failure?
- Enforcing an untested perimeter can cause production data pipeline failures.
- One wide internal allow rule can turn a frontend breach into database reachability.
- A wildcard ingress policy can eliminate the intended restriction for untrusted callers.
- A DNS-only block leaves applications that connect directly to numeric addresses unaffected.
Explanation
Correct Answer
A:Enforcing an untested perimeter can cause production data pipeline failures. VPC Service Controls dry-run reports policy violations without blocking them. The corrective approach is to analyze dry-run denial logs and iteratively approve only required flows before enforcement.
Incorrect Answers
B:One wide internal allow rule can turn a frontend breach into database reachability. This failure pattern belongs chiefly to N-tier east-west network segmentation; it is not the failure most directly tested in the VPC Service Controls dry-run evaluation situation. Enforcing an untested perimeter can cause production data pipeline failures.
C:A wildcard ingress policy can eliminate the intended restriction for untrusted callers. This failure pattern belongs chiefly to VPC Service Controls ingress egress policy; it is not the failure most directly tested in the VPC Service Controls dry-run evaluation situation. Enforcing an untested perimeter can cause production data pipeline failures.
D:A DNS-only block leaves applications that connect directly to numeric addresses unaffected. This failure pattern belongs chiefly to Cloud DNS response policy filtering; it is not the failure most directly tested in the VPC Service Controls dry-run evaluation situation. Enforcing an untested perimeter can cause production data pipeline failures.
Question 683
An administrator needs stronger authentication for privileged Cloud Identity users than SMS-only codes. Which practical correction or implementation decision is MOST directly appropriate?
- Test policy enforcement and emergency recovery without leaving a broad MFA bypass.
- Test token/session lifecycle behavior for permitted accounts and common admin workflows.
- Assume a strong password completely replaces the need for multi-factor authentication.
- Validate signing certificates, recovery procedures and negative authentication cases in a pilot.
Explanation
Correct Answer
A:Test policy enforcement and emergency recovery without leaving a broad MFA bypass. The intended behavior can be checked because security-key sign-in succeeds for enrolled administrators while unsupported fallback paths are governed.
Incorrect Answers
B:Test token/session lifecycle behavior for permitted accounts and common admin workflows. This could help Session duration and reauthentication policy, but it does not resolve the Phishing-resistant multi-factor verification case. Phishing-resistant authenticators bind verification to the legitimate service origin.
C:Assume a strong password completely replaces the need for multi-factor authentication. This would not correct the Phishing-resistant multi-factor verification workflow. An easily phished one-time passcode may not stop real-time credential relay attacks.
D:Validate signing certificates, recovery procedures and negative authentication cases in a pilot. This could help Identity-provider failover and recovery testing, but it does not resolve the Phishing-resistant multi-factor verification case. Phishing-resistant authenticators bind verification to the legitimate service origin.
Question 684
A developer submits a pull request adding a dependency with a publicly disclosed critical flaw. Which approach BEST meets the requirement while respecting the system constraints?
- Integrate authenticated dependency or image scanning into CI with controlled fail policies.
- Configure a supported Security Health Analytics custom module or SCC posture detector with scoped rule logic.
- Enable Binary Authorization enforcement on GKE with an appropriate signed attestation policy.
- Log a ticket for a critical finding and claim CI is enforcing a block without a pipeline condition.
Explanation
Correct Answer
A:Integrate authenticated dependency or image scanning into CI with controlled fail policies. Shift-left scanning detects known issues during delivery but needs a managed exception process. Verification should demonstrate that vulnerable builds are stopped with traceable findings while accepted exceptions are documented.
Incorrect Answers
B:Configure a supported Security Health Analytics custom module or SCC posture detector with scoped rule logic. This primarily addresses Security Health Analytics custom finding, not the specific Continuous integration dependency security gate decision. Here, shift-left scanning detects known issues during delivery but needs a managed exception process.
C:Enable Binary Authorization enforcement on GKE with an appropriate signed attestation policy. This primarily addresses Binary Authorization GKE admission, not the specific Continuous integration dependency security gate decision. Here, shift-left scanning detects known issues during delivery but needs a managed exception process.
D:Log a ticket for a critical finding and claim CI is enforcing a block without a pipeline condition. This is an unsafe or ineffective shortcut for Continuous integration dependency security gate. Ignoring scan results until after deployment reduces time to remediate vulnerable releases.
Question 685
An assessor asks how to prevent a compromised public web tier from reaching the payment database directly. Select TWO statements that correctly combine the PCI workload network segmentation method with evidence or its governing principle.
- Declare network segmentation complete solely because payment resources use a different billing account.
- Select supported resource locations and data residency controls across storage, processing and retained evidence.
- Implement scoped network, identity and service perimeter segmentation with tested flow restrictions.
- Only explicitly authorized payment-processing flows reach in-scope resources.
- Restrict datasets and share only approved de-identified outputs with monitored access controls.
Explanation
Correct Answers
C:Implement scoped network, identity and service perimeter segmentation with tested flow restrictions. This is the intended action for PCI workload network segmentation.
D:Only explicitly authorized payment-processing flows reach in-scope resources. This is directly observable validation of the PCI workload network segmentation result.
Incorrect Answers
A:Declare network segmentation complete solely because payment resources use a different billing account. This is not part of a safe or effective PCI workload network segmentation design. A shared open network can pull unrelated workloads into the regulated assessment scope.
B:Select supported resource locations and data residency controls across storage, processing and retained evidence. This serves the different Data residency and regionalization validation objective, not the selected PCI workload network segmentation plan. PCI segmentation reduces scope and attack surface only when enforced and validated.
E:Restrict datasets and share only approved de-identified outputs with monitored access controls. This serves the different Healthcare data privacy segmentation objective, not the selected PCI workload network segmentation plan. PCI segmentation reduces scope and attack surface only when enforced and validated.
Question 686
A service project tries to create subnets that should be governed by the host networking team. An engineer must explain the recommendation for Shared VPC host and service project boundaries. Which underlying principle is the MOST accurate?
- Shared VPC separates centralized network ownership from application project resource ownership.
- VPC Network Peering does not provide transitive routing or automatic IAM sharing.
- Hybrid connectivity creates a route path but application and subnet firewall policy still governs permitted flows.
- PSC service attachments expose specific producer services rather than transitive access to the entire VPC.
Explanation
Correct Answer
A:Shared VPC separates centralized network ownership from application project resource ownership. Therefore the implementation decision is to configure Shared VPC with host and service projects and appropriate subnet-use IAM grants.
Incorrect Answers
B:VPC Network Peering does not provide transitive routing or automatic IAM sharing. This describes the separate VPC Network Peering transitivity limits mechanism; the present case instead requires Shared VPC host and service project boundaries. Granting service developers host-project Owner access undermines network isolation.
C:Hybrid connectivity creates a route path but application and subnet firewall policy still governs permitted flows. This describes the separate Hybrid network segmentation policy placement mechanism; the present case instead requires Shared VPC host and service project boundaries. Granting service developers host-project Owner access undermines network isolation.
D:PSC service attachments expose specific producer services rather than transitive access to the entire VPC. This describes the separate Private Service Connect service attachment publishing mechanism; the present case instead requires Shared VPC host and service project boundaries. Granting service developers host-project Owner access undermines network isolation.
Question 687
On-call engineers need emergency project administration for approved maintenance windows. After the recommended Privileged Access Manager just-in-time approval change is implemented, which observation MOST directly verifies that it works?
- Approved requests yield bounded temporary privileges and unapproved users cannot self-elevate.
- The intended task succeeds without granting administrative privileges to unrelated projects.
- Newly approved staff gain only intended access while departed workers lose it within the policy window.
- The identified rule explains successful and failed operations for the exact principal and resource.
Explanation
Correct Answer
A:Approved requests yield bounded temporary privileges and unapproved users cannot self-elevate. This directly tests whether the Privileged Access Manager just-in-time approval goal was met. Just-in-time privileged access reduces standing administrative exposure and preserves an approval record.
Incorrect Answers
B:The intended task succeeds without granting administrative privileges to unrelated projects. This is evidence about IAM least-privilege role scoping, not direct proof of the required Privileged Access Manager just-in-time approval behavior. The relevant check is that approved requests yield bounded temporary privileges and unapproved users cannot self-elevate.
C:Newly approved staff gain only intended access while departed workers lose it within the policy window. This is evidence about Cloud Identity user lifecycle automation, not direct proof of the required Privileged Access Manager just-in-time approval behavior. The relevant check is that approved requests yield bounded temporary privileges and unapproved users cannot self-elevate.
D:The identified rule explains successful and failed operations for the exact principal and resource. This is evidence about IAM effective permission troubleshooting, not direct proof of the required Privileged Access Manager just-in-time approval behavior. The relevant check is that approved requests yield bounded temporary privileges and unapproved users cannot self-elevate.
Question 688
A namespace administrator finds that east-west pod traffic is unrestricted by default. Testing exposes this failure: Writing a policy YAML in an unsupported or unenforced cluster does not create isolation. Which remediation should be applied FIRST?
- Bind workload-specific Kubernetes subjects to approved Google Cloud resource roles.
- Assume each Kubernetes namespace is a complete network firewall without any network policy.
- Validate implementation support, selectors and policy behavior with test pods.
- Scan infrastructure-as-code plans against approved security guardrails and require review before deployment.
Explanation
Correct Answer
C:Validate implementation support, selectors and policy behavior with test pods. Confirmation requires seeing that only permitted pod-to-pod paths work and unauthorized paths fail during connection tests.
Incorrect Answers
A:Bind workload-specific Kubernetes subjects to approved Google Cloud resource roles. It addresses GKE Workload Identity for deployment runtime, not the diagnosed GKE network policy for pod segmentation failure. Writing a policy YAML in an unsupported or unenforced cluster does not create isolation.
B:Assume each Kubernetes namespace is a complete network firewall without any network policy. This retains the GKE network policy for pod segmentation problem. Kubernetes network policies can restrict pod traffic when enforced by the cluster's networking implementation.
D:Scan infrastructure-as-code plans against approved security guardrails and require review before deployment. It addresses Infrastructure as code security validation, not the diagnosed GKE network policy for pod segmentation failure. Writing a policy YAML in an unsupported or unenforced cluster does not create isolation.
Question 689
Security must protect cloud console accounts from password theft and adversary-in-the-middle phishing. If the relevant Phishing-resistant multi-factor verification safeguard is omitted, which outcome is the MOST directly associated failure?
- Overbroad scopes or missing audience checks can expose unrelated APIs.
- An overly broad deny rule can block critical service agents and break production operations.
- An easily phished one-time passcode may not stop real-time credential relay attacks.
- Accepting a token intended for another resource can enable token substitution.
Explanation
Correct Answer
C:An easily phished one-time passcode may not stop real-time credential relay attacks. Phishing-resistant authenticators bind verification to the legitimate service origin. The corrective approach is to test policy enforcement and emergency recovery without leaving a broad MFA bypass.
Incorrect Answers
A:Overbroad scopes or missing audience checks can expose unrelated APIs. This failure pattern belongs chiefly to OAuth audience and minimum scopes; it is not the failure most directly tested in the Phishing-resistant multi-factor verification situation. An easily phished one-time passcode may not stop real-time credential relay attacks.
B: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 Phishing-resistant multi-factor verification situation. An easily phished one-time passcode may not stop real-time credential relay attacks.
D:Accepting a token intended for another resource can enable token substitution. This failure pattern belongs chiefly to SAML versus OAuth authentication purpose; it is not the failure most directly tested in the Phishing-resistant multi-factor verification situation. An easily phished one-time passcode may not stop real-time credential relay attacks.
Question 690
Regional managers share a BigQuery table but must see only their assigned geographic rows. Which approach BEST meets the requirement while respecting the system constraints?
- Run Sensitive Data Protection inspection using appropriate infoTypes and controlled discovery scope.
- Configure a supported BigQuery row access policy tied to approved identities and predicates.
- Add a region column to a table and assume BigQuery automatically hides other regions.
- Issue a supported signed URL with limited method, object, expiry and protected signing identity.
Explanation
Correct Answer
B:Configure a supported BigQuery row access policy tied to approved identities and predicates. Row access policies enforce table row restrictions independent of a user's optional SQL filter. Verification should demonstrate that the same query yields permitted rows for each test identity and denies or filters restricted rows.
Incorrect Answers
A:Run Sensitive Data Protection inspection using appropriate infoTypes and controlled discovery scope. This primarily addresses Sensitive Data Protection PII inspection, not the specific BigQuery row-level access policy decision. Here, row access policies enforce table row restrictions independent of a user's optional SQL filter.
C:Add a region column to a table and assume BigQuery automatically hides other regions. This is an unsafe or ineffective shortcut for BigQuery row-level access policy. Saving a filtered query in an analyst workspace does not enforce all later queries.
D:Issue a supported signed URL with limited method, object, expiry and protected signing identity. This primarily addresses Time-bounded Cloud Storage signed URLs, not the specific BigQuery row-level access policy decision. Here, row access policies enforce table row restrictions independent of a user's optional SQL filter.