Google Professional Cloud Security Engineer Practice Test 38
Question 370
A deployed GKE pod needs to access one Cloud Storage bucket but not node-level credentials. After the recommended GKE Workload Identity for deployment runtime change is implemented, which observation MOST directly verifies that it works?
- The selected instances install approved updates and show patch compliance and failures.
- Only the intended pods access the bucket without exporting long-lived private service keys.
- An intentionally unsafe plan fails the gate while a least-privilege revision passes.
- Expected source-destination flow metadata appears without claiming every packet payload is captured.
Explanation
Correct Answer
B:Only the intended pods access the bucket without exporting long-lived private service keys. This directly tests whether the GKE Workload Identity for deployment runtime goal was met. Runtime workload identity scopes cloud permissions to pods and service accounts rather than entire hosts.
Incorrect Answers
A:The selected instances install approved updates and show patch compliance and failures. This is evidence about VM Manager patch orchestration, not direct proof of the required GKE Workload Identity for deployment runtime behavior. The relevant check is that only the intended pods access the bucket without exporting long-lived private service keys.
C:An intentionally unsafe plan fails the gate while a least-privilege revision passes. This is evidence about Infrastructure as code security validation, not direct proof of the required GKE Workload Identity for deployment runtime behavior. The relevant check is that only the intended pods access the bucket without exporting long-lived private service keys.
D:Expected source-destination flow metadata appears without claiming every packet payload is captured. This is evidence about VPC Flow Logs traffic analysis, not direct proof of the required GKE Workload Identity for deployment runtime behavior. The relevant check is that only the intended pods access the bucket without exporting long-lived private service keys.
Question 371
A service in a private subnet needs HTTP and HTTPS proxy filtering by destination. An engineer must explain the recommendation for Secure Web Proxy outbound web egress. Which underlying principle is the MOST accurate?
- Enabled service APIs and permission to call them are distinct controls.
- Access levels are contextual expressions that must be consumed by a policy to enforce a boundary.
- A web proxy enforces application-aware outbound web policy rather than serving as inbound load balancing.
- Private CA service manages certificate issuance trust independently of external web DNS registration.
Explanation
Correct Answer
C:A web proxy enforces application-aware outbound web policy rather than serving as inbound load balancing. Therefore the implementation decision is to configure Secure Web Proxy policies and route supported client web traffic through the intended proxy.
Incorrect Answers
A:Enabled service APIs and permission to call them are distinct controls. This describes the separate API exposure restriction and service inventory mechanism; the present case instead requires Secure Web Proxy outbound web egress. Bypassing the proxy with direct egress defeats approved destination filtering.
B: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 Secure Web Proxy outbound web egress. Bypassing the proxy with direct egress defeats approved destination filtering.
D:Private CA service manages certificate issuance trust independently of external web DNS registration. This describes the separate Certificate Authority Service private PKI mechanism; the present case instead requires Secure Web Proxy outbound web egress. Bypassing the proxy with direct egress defeats approved destination filtering.
Question 372
An application team discovers a service account JSON key committed to a shared repository. Which approach BEST meets the requirement while respecting the system constraints?
- Separate service account creation, service account user and IAM policy administration privileges.
- Configure a Workload Identity Federation pool and provider with audience and attribute restrictions.
- Identify the affected key, revoke or disable it under incident procedures and replace it with short-lived identity.
- Remove the public Git commit and assume the exposed key cannot be copied or used.
Explanation
Correct Answer
C:Identify the affected key, revoke or disable it under incident procedures and replace it with short-lived identity. Long-lived service account keys are exportable credentials that require strict inventory and incident response. Verification should demonstrate that the leaked key can no longer authenticate and supported workloads still operate using their new identity.
Incorrect Answers
A:Separate service account creation, service account user and IAM policy administration privileges. This primarily addresses Scoped permission for service account creation, not the specific Service account key inventory and exposure response decision. Here, long-lived service account keys are exportable credentials that require strict inventory and incident response.
B:Configure a Workload Identity Federation pool and provider with audience and attribute restrictions. This primarily addresses Workload Identity Federation for CI systems, not the specific Service account key inventory and exposure response decision. Here, long-lived service account keys are exportable credentials that require strict inventory and incident response.
D:Remove the public Git commit and assume the exposed key cannot be copied or used. This is an unsafe or ineffective shortcut for Service account key inventory and exposure response. Rotating only a repository secret variable leaves an already leaked key valid.
Question 373
Cardholder systems must be isolated from general employee development networks. Which approach BEST meets the requirement while respecting the system constraints?
- Declare network segmentation complete solely because payment resources use a different billing account.
- Review available Access Transparency logs alongside Cloud Audit Logs for the appropriate services.
- Compare official service compliance scope, customer contract terms and workload-specific requirements.
- Implement scoped network, identity and service perimeter segmentation with tested flow restrictions.
Explanation
Correct Answer
D:Implement scoped network, identity and service perimeter segmentation with tested flow restrictions. PCI segmentation reduces scope and attack surface only when enforced and validated. Verification should demonstrate that only explicitly authorized payment-processing flows reach in-scope resources.
Incorrect Answers
A:Declare network segmentation complete solely because payment resources use a different billing account. This is an unsafe or ineffective shortcut for PCI workload network segmentation. A shared open network can pull unrelated workloads into the regulated assessment scope.
B:Review available Access Transparency logs alongside Cloud Audit Logs for the appropriate services. This primarily addresses Access Transparency provider audit visibility, not the specific PCI workload network segmentation decision. Here, pCI segmentation reduces scope and attack surface only when enforced and validated.
C:Compare official service compliance scope, customer contract terms and workload-specific requirements. This primarily addresses Vendor shared-control contract and service eligibility, not the specific PCI workload network segmentation decision. Here, pCI segmentation reduces scope and attack surface only when enforced and validated.
Question 374
An organization needs intrusion prevention signatures on selected traffic paths. Select TWO statements that correctly combine the Cloud NGFW application-layer inspection method with evidence or its governing principle.
- Test traffic generates expected inspection findings and permitted requests still succeed.
- Assume every encrypted payload is automatically inspected merely because a port-based rule exists.
- Configure the proper external HTTPS load balancer certificates and backend protocol settings.
- Configure supported Cloud NGFW layer 7 inspection and TLS handling where supported.
- Configure supported Cloud Armor throttling or rate-based ban rules at suitable match scope.
Explanation
Correct Answers
A:Test traffic generates expected inspection findings and permitted requests still succeed. This is directly observable validation of the Cloud NGFW application-layer inspection result.
D:Configure supported Cloud NGFW layer 7 inspection and TLS handling where supported. This is the intended action for Cloud NGFW application-layer inspection.
Incorrect Answers
B:Assume every encrypted payload is automatically inspected merely because a port-based rule exists. This is not part of a safe or effective Cloud NGFW application-layer inspection design. Treating an allow-on-443 rule as deep content validation leaves application threats unexamined.
C:Configure the proper external HTTPS load balancer certificates and backend protocol settings. This serves the different HTTPS load balancer certificate and backend TLS objective, not the selected Cloud NGFW application-layer inspection plan. Network layer firewall rules alone do not inspect application content inside flows.
E:Configure supported Cloud Armor throttling or rate-based ban rules at suitable match scope. This serves the different Cloud Armor rate limiting and bot mitigation objective, not the selected Cloud NGFW application-layer inspection plan. Network layer firewall rules alone do not inspect application content inside flows.
Question 375
A cluster operator is concerned that unrelated namespaces share the same node IAM permissions. An engineer must explain the recommendation for GKE Workload Identity for deployment runtime. Which underlying principle is the MOST accurate?
- Preventive guardrails and detective drift monitoring complement each other across cloud projects.
- Artifact Registry permissions can be scoped independently from global project administrative access.
- Runtime workload identity scopes cloud permissions to pods and service accounts rather than entire hosts.
- Data Access logs have different availability and configuration behavior from Admin Activity logs.
Explanation
Correct Answer
C:Runtime workload identity scopes cloud permissions to pods and service accounts rather than entire hosts. Therefore the implementation decision is to bind workload-specific Kubernetes subjects to approved Google Cloud resource roles.
Incorrect Answers
A:Preventive guardrails and detective drift monitoring complement each other across cloud projects. This describes the separate Custom organization policy drift monitoring mechanism; the present case instead requires GKE Workload Identity for deployment runtime. Attaching broad roles to a common node identity magnifies container escape impact.
B:Artifact Registry permissions can be scoped independently from global project administrative access. This describes the separate Artifact Registry repository IAM isolation mechanism; the present case instead requires GKE Workload Identity for deployment runtime. Attaching broad roles to a common node identity magnifies container escape impact.
D:Data Access logs have different availability and configuration behavior from Admin Activity logs. This describes the separate Data Access Audit Logs enablement and cost mechanism; the present case instead requires GKE Workload Identity for deployment runtime. Attaching broad roles to a common node identity magnifies container escape impact.
Question 376
An organization wants to let external workforce users access Google Cloud with their existing OIDC credentials. Which practical correction or implementation decision is MOST directly appropriate?
- Test joiner, mover and leaver workflows with time-stamped audit evidence.
- Issue JSON service account keys to every external employee as the preferred interactive sign-in solution.
- Test attribute conditions and IAM bindings with separate approved and rejected external subjects.
- Validate SAML metadata, assertion audiences, user mapping and certificate rollover in a test cohort.
Explanation
Correct Answer
C:Test attribute conditions and IAM bindings with separate approved and rejected external subjects. The intended behavior can be checked because approved external subjects obtain federated console or API access while unmapped identities are denied.
Incorrect Answers
A:Test joiner, mover and leaver workflows with time-stamped audit evidence. This could help Cloud Identity user lifecycle automation, but it does not resolve the Workforce Identity Federation for external workers case. Workforce Identity Federation handles human identities from external IdPs and is distinct from workload federation.
B:Issue JSON service account keys to every external employee as the preferred interactive sign-in solution. This would not correct the Workforce Identity Federation for external workers workflow. Reusing one broad principal mapping for every contractor can grant unauthorized access.
D:Validate SAML metadata, assertion audiences, user mapping and certificate rollover in a test cohort. This could help SAML enterprise single sign-on, but it does not resolve the Workforce Identity Federation for external workers case. Workforce Identity Federation handles human identities from external IdPs and is distinct from workload federation.
Question 377
A response team needs to contain an active compromised workload while preserving forensic evidence. An engineer must explain the recommendation for Incident response alert routing and containment. Which underlying principle is the MOST accurate?
- Cloud IDS observes replicated network traffic for threats but does not inherently replace blocking firewall controls.
- Aggregated sinks centralize eligible descendant logs but need correct scope and sink writer identity access.
- Image digest attestations authorize precisely identified artifacts rather than unrelated mutable labels.
- Containment, evidence preservation and recovery are coordinated security operations rather than one dashboard click.
Explanation
Correct Answer
D:Containment, evidence preservation and recovery are coordinated security operations rather than one dashboard click. Therefore the implementation decision is to run an approved incident playbook to scope impact, restrict compromised credentials and preserve logs.
Incorrect Answers
A:Deleting resources and logs before evidence collection can undermine root-cause analysis. Cloud IDS observes replicated network traffic for threats but does not inherently replace blocking firewall controls.
B:Deleting resources and logs before evidence collection can undermine root-cause analysis. Aggregated sinks centralize eligible descendant logs but need correct scope and sink writer identity access.
C:Deleting resources and logs before evidence collection can undermine root-cause analysis. Image digest attestations authorize precisely identified artifacts rather than unrelated mutable labels.
Question 378
A business wants to prevent employees from granting project roles to arbitrary outside identities. Which approach BEST meets the requirement while respecting the system constraints?
- Configure a Cloud DNS domain and assume IAM sharing is restricted to its email suffix.
- Use supported organization policy domain-restricted sharing controls with approved identities or exceptions.
- Grant only the narrow permitted policy exception and retain documented rollback and audit approval.
- Configure the supported Compute Engine external-IP restriction organization policy and review project exceptions.
Explanation
Correct Answer
B:Use supported organization policy domain-restricted sharing controls with approved identities or exceptions. Domain-restricted sharing guardrails constrain identity grants separately from resource firewalls. Verification should demonstrate that unapproved external principals cannot be added to controlled IAM policies.
Incorrect Answers
A:Configure a Cloud DNS domain and assume IAM sharing is restricted to its email suffix. This is an unsafe or ineffective shortcut for Restricting allowed IAM member domains. An overly permissive domain exception can enable unauthorized external role assignments.
C:Grant only the narrow permitted policy exception and retain documented rollback and audit approval. This primarily addresses Hierarchy-scoped exception and policy rollback, not the specific Restricting allowed IAM member domains decision. Here, domain-restricted sharing guardrails constrain identity grants separately from resource firewalls.
D:Configure the supported Compute Engine external-IP restriction organization policy and review project exceptions. This primarily addresses Restricting external IPv4 addresses through org policy, not the specific Restricting allowed IAM member domains decision. Here, domain-restricted sharing guardrails constrain identity grants separately from resource firewalls.
Question 379
A newly deployed enterprise identity provider starts rejecting users because its trust certificate expired. After the recommended Identity-provider failover and recovery testing change is implemented, which observation MOST directly verifies that it works?
- Security-key sign-in succeeds for enrolled administrators while unsupported fallback paths are governed.
- Controlled test logins work after the change and emergency recovery stays documented.
- Requests that satisfy the access level are eligible while unmatched contexts are rejected by the consuming policy.
- Old privileged sessions expire according to policy and authorized workers can reauthenticate.
Explanation
Correct Answer
B:Controlled test logins work after the change and emergency recovery stays documented. This directly tests whether the Identity-provider failover and recovery testing goal was met. Authentication availability and security policy must be tested together before a global rollout.
Incorrect Answers
A:Security-key sign-in succeeds for enrolled administrators while unsupported fallback paths are governed. This is evidence about Phishing-resistant multi-factor verification, not direct proof of the required Identity-provider failover and recovery testing behavior. The relevant check is that controlled test logins work after the change and emergency recovery stays documented.
C:Requests that satisfy the access level are eligible while unmatched contexts are rejected by the consuming policy. This is evidence about Access Context Manager access levels, not direct proof of the required Identity-provider failover and recovery testing behavior. The relevant check is that controlled test logins work after the change and emergency recovery stays documented.
D:Old privileged sessions expire according to policy and authorized workers can reauthenticate. This is evidence about Session duration and reauthentication policy, not direct proof of the required Identity-provider failover and recovery testing behavior. The relevant check is that controlled test logins work after the change and emergency recovery stays documented.
Question 380
A financial auditor requests evidence about actions Google personnel took while accessing supported customer environments. After the recommended Access Transparency provider audit visibility change is implemented, which observation MOST directly verifies that it works?
- Provider-related access entries and customer administrative events are categorized correctly.
- The leaked key can no longer authenticate and supported workloads still operate using their new identity.
- Authorized investigators retrieve allowed aggregate values while raw patient fields remain denied.
- Evidence samples demonstrate control operation across the review period and are tamper resistant.
Explanation
Correct Answer
A:Provider-related access entries and customer administrative events are categorized correctly. This directly tests whether the Access Transparency provider audit visibility goal was met. Access Transparency provides visibility into certain Google personnel interactions and differs from customer Audit Logs.
Incorrect Answers
B:The leaked key can no longer authenticate and supported workloads still operate using their new identity. This is evidence about Service account key inventory and exposure response, not direct proof of the required Access Transparency provider audit visibility behavior. The relevant check is that provider-related access entries and customer administrative events are categorized correctly.
C:Authorized investigators retrieve allowed aggregate values while raw patient fields remain denied. This is evidence about Healthcare data privacy segmentation, not direct proof of the required Access Transparency provider audit visibility behavior. The relevant check is that provider-related access entries and customer administrative events are categorized correctly.
D:Evidence samples demonstrate control operation across the review period and are tamper resistant. This is evidence about Audit evidence collection and attestation, not direct proof of the required Access Transparency provider audit visibility behavior. The relevant check is that provider-related access entries and customer administrative events are categorized correctly.