Google Professional Cloud Security Engineer Practice Test 67
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.
Question 661
Security suspects stolen service account credentials are being used to mine cryptocurrency. After the recommended Event Threat Detection behavior monitoring change is implemented, which observation MOST directly verifies that it works?
- Log entries identify matching policy, direction, source, destination and disposition.
- Detection alerts identify the monitored flow and are routed to responsible responders.
- Simulated suspicious behavior produces a traceable finding without treating every normal request as malicious.
- Pipeline uploads and runtime pulls work only for approved repositories.
Explanation
Correct Answer
C:Simulated suspicious behavior produces a traceable finding without treating every normal request as malicious. This directly tests whether the Event Threat Detection behavior monitoring goal was met. Threat detection derives signals from audit and operational events, distinct from posture-only scanning.
Incorrect Answers
A:Log entries identify matching policy, direction, source, destination and disposition. This is evidence about Firewall rule logging and deny analysis, not direct proof of the required Event Threat Detection behavior monitoring behavior. The relevant check is that simulated suspicious behavior produces a traceable finding without treating every normal request as malicious.
B:Detection alerts identify the monitored flow and are routed to responsible responders. This is evidence about Cloud Intrusion Detection System alerts, not direct proof of the required Event Threat Detection behavior monitoring behavior. The relevant check is that simulated suspicious behavior produces a traceable finding without treating every normal request as malicious.
D:Pipeline uploads and runtime pulls work only for approved repositories. This is evidence about Artifact Registry repository IAM isolation, not direct proof of the required Event Threat Detection behavior monitoring behavior. The relevant check is that simulated suspicious behavior produces a traceable finding without treating every normal request as malicious.
Question 662
A contractor should access one HTTPS service only when identity and device conditions qualify. An engineer must explain the recommendation for Identity-Aware Proxy application access. Which underlying principle is the MOST accurate?
- DNS response policies can override name resolution for attached networks but do not block all direct-IP communication.
- A web proxy enforces application-aware outbound web policy rather than serving as inbound load balancing.
- IAP adds identity-based access enforcement before reaching supported applications.
- Access levels are contextual expressions that must be consumed by a policy to enforce a boundary.
Explanation
Correct Answer
C:IAP adds identity-based access enforcement before reaching supported applications. Therefore the implementation decision is to protect the supported backend with Identity-Aware Proxy and least-privilege IAP access grants.
Incorrect Answers
A:DNS response policies can override name resolution for attached networks but do not block all direct-IP communication. This describes the separate Cloud DNS response policy filtering mechanism; the present case instead requires Identity-Aware Proxy application access. Exposing a direct backend path may bypass the intended identity gate.
B:A web proxy enforces application-aware outbound web policy rather than serving as inbound load balancing. This describes the separate Secure Web Proxy outbound web egress mechanism; the present case instead requires Identity-Aware Proxy application access. Exposing a direct backend path may bypass the intended identity gate.
D:Access levels are contextual expressions that must be consumed by a policy to enforce a boundary. This describes the separate Access levels with perimeter identity trust mechanism; the present case instead requires Identity-Aware Proxy application access. Exposing a direct backend path may bypass the intended identity gate.
Question 663
A data center reaches Google APIs over Cloud Interconnect but should not traverse the open internet. After the recommended Private Google Access for on-premises change is implemented, which observation MOST directly verifies that it works?
- On-premises clients can reach supported APIs through the intended private Google connectivity path.
- Traffic remains encrypted and routes converge when a single tunnel or interface fails.
- Private workloads can reach supported Google APIs without an assigned external IP.
- Certificate validation and backend health checks succeed without sending protected data over unintended plaintext paths.
Explanation
Correct Answer
A:On-premises clients can reach supported APIs through the intended private Google connectivity path. This directly tests whether the Private Google Access for on-premises goal was met. On-premises Private Google Access requires routing and DNS integration beyond a VPC subnet checkbox.
Incorrect Answers
B:Traffic remains encrypted and routes converge when a single tunnel or interface fails. This is evidence about HA VPN encrypted hybrid tunnels, not direct proof of the required Private Google Access for on-premises behavior. The relevant check is that on-premises clients can reach supported APIs through the intended private Google connectivity path.
C:Private workloads can reach supported Google APIs without an assigned external IP. This is evidence about Private Google Access for internal VMs, not direct proof of the required Private Google Access for on-premises behavior. The relevant check is that on-premises clients can reach supported APIs through the intended private Google connectivity path.
D:Certificate validation and backend health checks succeed without sending protected data over unintended plaintext paths. This is evidence about HTTPS load balancer certificate and backend TLS, not direct proof of the required Private Google Access for on-premises behavior. The relevant check is that on-premises clients can reach supported APIs through the intended private Google connectivity path.
Question 664
An application database must not expose a public Cloud SQL endpoint to the internet. If the relevant Cloud SQL private IP and database authentication safeguard is omitted, which outcome is the MOST directly associated failure?
- Copying raw key bytes into an unencrypted text field undermines key custody.
- Publishing tokenization keys alongside datasets can permit re-identification.
- Scanning sensitive data into an openly shared findings table can create a second disclosure path.
- A project IAM grant alone does not necessarily authorize arbitrary SQL queries on every database.
Explanation
Correct Answer
D:A project IAM grant alone does not necessarily authorize arbitrary SQL queries on every database. Network connectivity and database-level authentication are separate enforcement layers. The corrective approach is to test private IP route, database roles and unauthorized connection attempts.
Incorrect Answers
A:This failure pattern belongs chiefly to Cloud KMS imported key material; it is not the failure most directly tested in the Cloud SQL private IP and database authentication situation.
B:This failure pattern belongs chiefly to Sensitive Data Protection deterministic de-identification; it is not the failure most directly tested in the Cloud SQL private IP and database authentication situation.
C:This failure pattern belongs chiefly to Sensitive Data Protection PII inspection; it is not the failure most directly tested in the Cloud SQL private IP and database authentication situation.
Question 665
VMs in a private subnet need to download package updates from public repositories without public IPs. If the relevant Cloud NAT outbound without inbound exposure safeguard is omitted, which outcome is the MOST directly associated failure?
- Using the private VIP indiscriminately can allow calls to services outside the intended restricted set.
- One misconfigured BGP peer can eliminate the claimed high-availability path.
- Allowing ingress from all subnet addresses can enable lateral movement across tiers.
- Treating Cloud NAT as inbound protection while allowing broad alternative ingress can leave exposure.
Explanation
Correct Answer
D:Treating Cloud NAT as inbound protection while allowing broad alternative ingress can leave exposure. Cloud NAT translates eligible outbound connections and is not an inbound proxy or firewall substitute. The corrective approach is to verify NAT logs, port availability and lack of public VM external IPs.
Incorrect Answers
A:This failure pattern belongs chiefly to Restricted Google APIs VIP for perimeters; it is not the failure most directly tested in the Cloud NAT outbound without inbound exposure situation.
B:This failure pattern belongs chiefly to HA VPN encrypted hybrid tunnels; it is not the failure most directly tested in the Cloud NAT outbound without inbound exposure situation.
C:This failure pattern belongs chiefly to VPC firewall stateful filtering; it is not the failure most directly tested in the Cloud NAT outbound without inbound exposure situation.
Question 666
A security team needs an approved sinkhole response for selected private network clients. Which practical correction or implementation decision is MOST directly appropriate?
- Assume blocking one domain in Cloud DNS also blocks every possible IP route to its service.
- Validate traffic aggregation keys, request volume windows and response codes under load.
- Test queries from associated and nonassociated networks and pair with network controls.
- Inspect certificate lifecycle, forwarding rule, backend service and health check settings.
Explanation
Correct Answer
C:Test queries from associated and nonassociated networks and pair with network controls. The intended behavior can be checked because restricted clients receive the expected filtered response without affecting unrelated resolvers.
Incorrect Answers
A:Assume blocking one domain in Cloud DNS also blocks every possible IP route to its service. This would not correct the Cloud DNS response policy filtering workflow. A DNS-only block leaves applications that connect directly to numeric addresses unaffected.
B:Validate traffic aggregation keys, request volume windows and response codes under load. This could help Cloud Armor rate limiting and bot mitigation, but it does not resolve the Cloud DNS response policy filtering case. DNS response policies can override name resolution for attached networks but do not block all direct-IP communication.
D:Inspect certificate lifecycle, forwarding rule, backend service and health check settings. This could help HTTPS load balancer certificate and backend TLS, but it does not resolve the Cloud DNS response policy filtering case. DNS response policies can override name resolution for attached networks but do not block all direct-IP communication.
Question 667
A merger introduces renamed users and nested groups that must retain correct cloud membership. Which practical correction or implementation decision is MOST directly appropriate?
- Test attribute conditions and IAM bindings with separate approved and rejected external subjects.
- Reconcile synchronization reports, exclusion rules and sample user memberships before enabling changes.
- Perform regular privileged-group recertification with exception tickets and negative access tests.
- Treat a successful SAML login as proof all directory users and groups have been synchronized.
Explanation
Correct Answer
B:Reconcile synchronization reports, exclusion rules and sample user memberships before enabling changes. The intended behavior can be checked because the scheduled synchronization creates and updates the intended users without unexpectedly deleting cloud identities.
Incorrect Answers
A:Test attribute conditions and IAM bindings with separate approved and rejected external subjects. This could help Workforce Identity Federation for external workers, but it does not resolve the Cloud Identity directory synchronization case. Directory synchronization maps authoritative identity sources into managed cloud accounts rather than granting IAM roles itself.
C:Perform regular privileged-group recertification with exception tickets and negative access tests. This could help Group-based provisioning audit trail, but it does not resolve the Cloud Identity directory synchronization case. Directory synchronization maps authoritative identity sources into managed cloud accounts rather than granting IAM roles itself.
D:Treat a successful SAML login as proof all directory users and groups have been synchronized. This would not correct the Cloud Identity directory synchronization workflow. Broad unreviewed deletion rules can disable legitimate cloud users during synchronization.
Question 668
An organization wants employees to authenticate through its existing SAML identity provider instead of separate cloud passwords. If the relevant SAML enterprise single sign-on safeguard is omitted, which outcome is the MOST directly associated failure?
- Broad unreviewed deletion rules can disable legitimate cloud users during synchronization.
- Routine use of shared super-admin credentials destroys accountability and enlarges blast radius.
- Incorrect NameID mapping or expired signing certificates can prevent legitimate employee login.
- Accepting a token intended for another resource can enable token substitution.
Explanation
Correct Answer
C:Incorrect NameID mapping or expired signing certificates can prevent legitimate employee login. SAML exchanges signed authentication assertions and requires coordinated trust configuration. The corrective approach is to validate SAML metadata, assertion audiences, user mapping and certificate rollover in a test cohort.
Incorrect Answers
A:Broad unreviewed deletion rules can disable legitimate cloud users during synchronization. This failure pattern belongs chiefly to Cloud Identity directory synchronization; it is not the failure most directly tested in the SAML enterprise single sign-on situation. Incorrect NameID mapping or expired signing certificates can prevent legitimate employee login.
B:Routine use of shared super-admin credentials destroys accountability and enlarges blast radius. This failure pattern belongs chiefly to Super administrator emergency access; it is not the failure most directly tested in the SAML enterprise single sign-on situation. Incorrect NameID mapping or expired signing certificates can prevent legitimate employee login.
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 SAML enterprise single sign-on situation. Incorrect NameID mapping or expired signing certificates can prevent legitimate employee login.
Question 669
Security needs a pipeline rule preventing unsafe cloud configurations before apply. Select TWO statements that correctly combine the Infrastructure as code security validation method with evidence or its governing principle.
- Configure appropriate organization policy monitoring or posture-management controls at scale.
- An intentionally unsafe plan fails the gate while a least-privilege revision passes.
- Scan infrastructure-as-code plans against approved security guardrails and require review before deployment.
- Trust every Terraform apply simply because its syntax is valid.
- Assign a dedicated minimum-privilege build service account with scoped artifact and secret permissions.
Explanation
Correct Answers
B:An intentionally unsafe plan fails the gate while a least-privilege revision passes. This is directly observable validation of the Infrastructure as code security validation result.
C:Scan infrastructure-as-code plans against approved security guardrails and require review before deployment. This is the intended action for Infrastructure as code security validation.
Incorrect Answers
A:Configure appropriate organization policy monitoring or posture-management controls at scale. This serves the different Custom organization policy drift monitoring objective, not the selected Infrastructure as code security validation plan. IaC policy validation can catch configuration drift earlier than production vulnerability alerts.
D:Trust every Terraform apply simply because its syntax is valid. This is not part of a safe or effective Infrastructure as code security validation design. A review comment without enforced CI policy can still permit unsafe infrastructure rollout.
E:Assign a dedicated minimum-privilege build service account with scoped artifact and secret permissions. This serves the different Secure Cloud Build execution identity objective, not the selected Infrastructure as code security validation plan. IaC policy validation can catch configuration drift earlier than production vulnerability alerts.
Question 670
A compliance officer wants to onboard new projects under a governed Assured Workloads folder. Which practical correction or implementation decision is MOST directly appropriate?
- Name an ordinary folder Assured and assume it automatically meets every government cloud regime.
- Conduct tabletop validation and sample ticket evidence against documented escalation targets.
- Test folder creation, resource restrictions and eligible personnel or support requirements.
- Trace data from ingestion through storage, analytics, backups and deletion.
Explanation
Correct Answer
C:Test folder creation, resource restrictions and eligible personnel or support requirements. The intended behavior can be checked because resources inherit applicable guardrails and environment evidence aligns with designated compliance profile.
Incorrect Answers
A:Name an ordinary folder Assured and assume it automatically meets every government cloud regime. This would not correct the Assured Workloads compliance resource boundary workflow. Placing an unreviewed project outside the required environment can defeat the scoped controls.
B:Conduct tabletop validation and sample ticket evidence against documented escalation targets. This could help SOC control evidence and incident workflow, but it does not resolve the Assured Workloads compliance resource boundary case. Assured Workloads provides configurable compliance guardrails but does not certify arbitrary workloads by mere association.
D:Trace data from ingestion through storage, analytics, backups and deletion. This could help Regulatory scope inventory and boundaries, but it does not resolve the Assured Workloads compliance resource boundary case. Assured Workloads provides configurable compliance guardrails but does not certify arbitrary workloads by mere association.