Google Professional Cloud Security Engineer Practice Test 2
Question 10
An old key remains active after engineers migrated to managed runtime identity. Testing exposes this failure: Rotating only a repository secret variable leaves an already leaked key valid. Which remediation should be applied FIRST?
- Validate key disablement through audit logs and test legitimate replacement authentication.
- Create distinct runtime service accounts and bind task-specific roles at the smallest supported scope.
- Remove the public Git commit and assume the exposed key cannot be copied or used.
- Inventory workloads using the identity and disable or suspend the affected service account with a recovery plan.
Explanation
Correct Answer
A:Validate key disablement through audit logs and test legitimate replacement authentication. Confirmation requires seeing that the leaked key can no longer authenticate and supported workloads still operate using their new identity.
Incorrect Answers
B:Create distinct runtime service accounts and bind task-specific roles at the smallest supported scope. It addresses Service account per-workload identity design, not the diagnosed Service account key inventory and exposure response failure. Rotating only a repository secret variable leaves an already leaked key valid.
C:Remove the public Git commit and assume the exposed key cannot be copied or used. This retains the Service account key inventory and exposure response problem. Long-lived service account keys are exportable credentials that require strict inventory and incident response.
D:Inventory workloads using the identity and disable or suspend the affected service account with a recovery plan. It addresses Service account disabling and dependency mapping, not the diagnosed Service account key inventory and exposure response failure. Rotating only a repository secret variable leaves an already leaked key valid.
Question 11
Security wants inspection visibility beyond high-level VPC flow metadata for one controlled segment. Which practical correction or implementation decision is MOST directly appropriate?
- Verify selected traffic, scope, cost and collector access under the incident runbook.
- Test supported detectors and route critical findings to an incident queue.
- Test synthetic traffic and validate sampling implications and log analysis filters.
- Assume VPC Flow Logs contain identical full packet contents to a Packet Mirroring collector.
Explanation
Correct Answer
A:Verify selected traffic, scope, cost and collector access under the incident runbook. The intended behavior can be checked because collector evidence captures authorized mirrored traffic from the intended interfaces.
Incorrect Answers
B:Test supported detectors and route critical findings to an incident queue. This could help Security Command Center centralized findings, but it does not resolve the Packet Mirroring for intrusion investigation case. Packet Mirroring copies network packets to authorized collectors and can expose sensitive traffic.
C:Test synthetic traffic and validate sampling implications and log analysis filters. This could help VPC Flow Logs traffic analysis, but it does not resolve the Packet Mirroring for intrusion investigation case. Packet Mirroring copies network packets to authorized collectors and can expose sensitive traffic.
D:Assume VPC Flow Logs contain identical full packet contents to a Packet Mirroring collector. This would not correct the Packet Mirroring for intrusion investigation workflow. Mirroring all production traffic to an untrusted collector creates a new exfiltration risk.
Question 12
A protected project needs to allow one approved outside service account to invoke a specified API. If the relevant VPC Service Controls ingress egress policy safeguard is omitted, which outcome is the MOST directly associated failure?
- 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.
- Assigning an internal IP while retaining an exposed public load balancer can leave ingress available.
- Allowing ingress from all subnet addresses can enable lateral movement across tiers.
Explanation
Correct Answer
B:A wildcard ingress policy can eliminate the intended restriction for untrusted callers. Ingress and egress policies define controlled exceptions around restricted service perimeter boundaries. The corrective approach is to use dry-run method traces and negative tests before approving exceptions.
Incorrect Answers
A: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 ingress egress policy situation.
C:This failure pattern belongs chiefly to Private versus public endpoint design; it is not the failure most directly tested in the VPC Service Controls ingress egress policy situation.
D:Allowing ingress from all subnet addresses can enable lateral movement across tiers. This failure pattern belongs chiefly to VPC firewall stateful filtering; it is not the failure most directly tested in the VPC Service Controls ingress egress policy situation. A wildcard ingress policy can eliminate the intended restriction for untrusted callers.
Question 13
Investigators need packet-flow metadata to explain unexpected egress from a private subnet. Which approach BEST meets the requirement while respecting the system constraints?
- Configure supported VPC Flow Logs at intended subnet sampling and aggregation settings.
- Enable VPC Flow Logs and assume TLS payload contents are now recorded in plaintext.
- Run an approved incident playbook to scope impact, restrict compromised credentials and preserve logs.
- Configure Cloud Logging bucket retention controls and appropriate restricted management privileges.
Explanation
Correct Answer
A:Configure supported VPC Flow Logs at intended subnet sampling and aggregation settings. VPC Flow Logs summarize network traffic metadata rather than full decrypted application content. Verification should demonstrate that expected source-destination flow metadata appears without claiming every packet payload is captured.
Incorrect Answers
B:Enable VPC Flow Logs and assume TLS payload contents are now recorded in plaintext. This is an unsafe or ineffective shortcut for VPC Flow Logs traffic analysis. Treating sampled flow metadata as complete packet capture may hide short or unobserved exchanges.
C:Run an approved incident playbook to scope impact, restrict compromised credentials and preserve logs. This primarily addresses Incident response alert routing and containment, not the specific VPC Flow Logs traffic analysis decision. Here, vPC Flow Logs summarize network traffic metadata rather than full decrypted application content.
D:Configure Cloud Logging bucket retention controls and appropriate restricted management privileges. This primarily addresses Log bucket retention and immutable audit evidence, not the specific VPC Flow Logs traffic analysis decision. Here, vPC Flow Logs summarize network traffic metadata rather than full decrypted application content.
Question 14
A subnet needs to permit application tier traffic only from the reverse proxy tier. Which approach BEST meets the requirement while respecting the system constraints?
- Apply VPC Service Controls perimeters to supported data services with least-privilege ingress and egress policies.
- Create an ingress TCP rule and assume it must separately allow every response packet as unrelated egress.
- Define least-privilege stateful VPC firewall ingress and egress controls for the intended connections.
- Add narrowly scoped VPC Service Controls ingress or egress rules using principal and service operation constraints.
Explanation
Correct Answer
C:Define least-privilege stateful VPC firewall ingress and egress controls for the intended connections. VPC firewalls evaluate directional connection initiation with stateful return traffic handling. Verification should demonstrate that connection tests show approved initiation and return flows while disallowed initiations fail.
Incorrect Answers
A:Apply VPC Service Controls perimeters to supported data services with least-privilege ingress and egress policies. This primarily addresses VPC Service Controls service perimeter, not the specific VPC firewall stateful filtering decision. Here, vPC firewalls evaluate directional connection initiation with stateful return traffic handling.
B:Create an ingress TCP rule and assume it must separately allow every response packet as unrelated egress. This is an unsafe or ineffective shortcut for VPC firewall stateful filtering. Allowing ingress from all subnet addresses can enable lateral movement across tiers.
D:Add narrowly scoped VPC Service Controls ingress or egress rules using principal and service operation constraints. This primarily addresses VPC Service Controls ingress egress policy, not the specific VPC firewall stateful filtering decision. Here, vPC firewalls evaluate directional connection initiation with stateful return traffic handling.
Question 15
A team is confused because return packets are allowed despite a directional ingress rule. Which practical correction or implementation decision is MOST directly appropriate?
- Analyze dry-run denial logs and iteratively approve only required flows before enforcement.
- Create an ingress TCP rule and assume it must separately allow every response packet as unrelated egress.
- Check route exchange and add the appropriate direct or supported transit architecture.
- Inspect effective rules, connection state and VPC Flow Logs for both traffic directions.
Explanation
Correct Answer
D:Inspect effective rules, connection state and VPC Flow Logs for both traffic directions. The intended behavior can be checked because connection tests show approved initiation and return flows while disallowed initiations fail.
Incorrect Answers
A:Analyze dry-run denial logs and iteratively approve only required flows before enforcement. This could help VPC Service Controls dry-run evaluation, but it does not resolve the VPC firewall stateful filtering case. VPC firewalls evaluate directional connection initiation with stateful return traffic handling.
B:Create an ingress TCP rule and assume it must separately allow every response packet as unrelated egress. This would not correct the VPC firewall stateful filtering workflow. Allowing ingress from all subnet addresses can enable lateral movement across tiers.
C:Check route exchange and add the appropriate direct or supported transit architecture. This could help VPC Network Peering transitivity limits, but it does not resolve the VPC firewall stateful filtering case. VPC firewalls evaluate directional connection initiation with stateful return traffic handling.
Question 16
A hybrid workload uses the wrong DNS mapping and Google API calls take an unintended route. An engineer must explain the recommendation for Private Google Access for on-premises. Which underlying principle is the MOST accurate?
- Private Service Connect provides controlled private connectivity to supported services and APIs.
- On-premises Private Google Access requires routing and DNS integration beyond a VPC subnet checkbox.
- Edge rate controls mitigate abusive request volume but do not replace application authentication.
- Restricted Google APIs endpoints narrow accessible Google API services when correctly routed.
Explanation
Correct Answer
B:On-premises Private Google Access requires routing and DNS integration beyond a VPC subnet checkbox. Therefore the implementation decision is to design Private Google Access for on-premises hosts with approved routes and private or restricted VIP DNS.
Incorrect Answers
A:Private Service Connect provides controlled private connectivity to supported services and APIs. This describes the separate Private Service Connect Google APIs endpoints mechanism; the present case instead requires Private Google Access for on-premises. Mapping API hostnames to ordinary public IPs may bypass the intended private access design.
C:Edge rate controls mitigate abusive request volume but do not replace application authentication. This describes the separate Cloud Armor rate limiting and bot mitigation mechanism; the present case instead requires Private Google Access for on-premises. Mapping API hostnames to ordinary public IPs may bypass the intended private access design.
D:Restricted Google APIs endpoints narrow accessible Google API services when correctly routed. This describes the separate Restricted Google APIs VIP for perimeters mechanism; the present case instead requires Private Google Access for on-premises. Mapping API hostnames to ordinary public IPs may bypass the intended private access design.
Question 17
A security engineer must relate suspicious signature alerts to specific affected network segments. Which practical correction or implementation decision is MOST directly appropriate?
- Exercise credential revocation, incident timeline and recovery in a safe tabletop.
- Assume Cloud IDS automatically blocks every threat even when no enforcement rule is configured.
- Generate safe test signatures and correlate Cloud IDS findings with flow context.
- Reproduce a controlled object read to validate log generation and principal attribution.
Explanation
Correct Answer
C:Generate safe test signatures and correlate Cloud IDS findings with flow context. The intended behavior can be checked because detection alerts identify the monitored flow and are routed to responsible responders.
Incorrect Answers
A:Exercise credential revocation, incident timeline and recovery in a safe tabletop. This could help Incident response alert routing and containment, but it does not resolve the Cloud Intrusion Detection System alerts case. Cloud IDS observes replicated network traffic for threats but does not inherently replace blocking firewall controls.
B:Assume Cloud IDS automatically blocks every threat even when no enforcement rule is configured. This would not correct the Cloud Intrusion Detection System alerts workflow. Deploying IDS without mirroring relevant traffic can result in little detection coverage.
D:Reproduce a controlled object read to validate log generation and principal attribution. This could help Cloud Storage audit trail for exfiltration, but it does not resolve the Cloud Intrusion Detection System alerts case. Cloud IDS observes replicated network traffic for threats but does not inherently replace blocking firewall controls.
Question 18
An organization wants employees to authenticate through its existing SAML identity provider instead of separate cloud passwords. After the recommended SAML enterprise single sign-on change is implemented, which observation MOST directly verifies that it works?
- Membership changes match approved source records and unexpected external identities are rejected.
- Test users complete sign-in through the designated provider and break-glass access remains available.
- The scheduled synchronization creates and updates the intended users without unexpectedly deleting cloud identities.
- Access succeeds while condition is true and fails after expiry or outside the supported resource scope.
Explanation
Correct Answer
B:Test users complete sign-in through the designated provider and break-glass access remains available. This directly tests whether the SAML enterprise single sign-on goal was met. SAML exchanges signed authentication assertions and requires coordinated trust configuration.
Incorrect Answers
A:Membership changes match approved source records and unexpected external identities are rejected. This is evidence about Programmatic group membership governance, not direct proof of the required SAML enterprise single sign-on behavior. The relevant check is that test users complete sign-in through the designated provider and break-glass access remains available.
C: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 SAML enterprise single sign-on behavior. The relevant check is that test users complete sign-in through the designated provider and break-glass access remains available.
D:Access succeeds while condition is true and fails after expiry or outside the supported resource scope. This is evidence about Conditional IAM access restrictions, not direct proof of the required SAML enterprise single sign-on behavior. The relevant check is that test users complete sign-in through the designated provider and break-glass access remains available.
Question 19
Workload VMs must visit only approved external SaaS URLs while maintaining audited egress. If the relevant Secure Web Proxy outbound web egress safeguard is omitted, which outcome is the MOST directly associated failure?
- An IAM role alone does not confine data copied through permitted APIs to untrusted projects.
- Assuming a lower-priority allow overrides a higher-priority deny may leave an exposure or outage.
- Bypassing the proxy with direct egress defeats approved destination filtering.
- An all-subnet ingress rule exposes unrelated instances to the same port.
Explanation
Correct Answer
C:Bypassing the proxy with direct egress defeats approved destination filtering. A web proxy enforces application-aware outbound web policy rather than serving as inbound load balancing. The corrective approach is to test proxy routing, inspection policy and client fail-closed behavior under outage.
Incorrect Answers
A:This failure pattern belongs chiefly to VPC Service Controls service perimeter; it is not the failure most directly tested in the Secure Web Proxy outbound web egress situation.
B:This failure pattern belongs chiefly to Hierarchical Cloud NGFW policy ordering; it is not the failure most directly tested in the Secure Web Proxy outbound web egress situation.
D:An all-subnet ingress rule exposes unrelated instances to the same port. This failure pattern belongs chiefly to Cloud NGFW targeted service account rules; it is not the failure most directly tested in the Secure Web Proxy outbound web egress situation. Bypassing the proxy with direct egress defeats approved destination filtering.
Question 20
A security auditor must review log events without modifying sinks or retention rules. Select TWO statements that correctly combine the Least privilege access to audit logs method with evidence or its governing principle.
- Assign narrowly scoped Cloud Logging view access and separate log configuration permissions.
- Grant project Owner solely to let a contractor search one audit log.
- Correlate supported Cloud Storage Data Access logs with IAM bindings and network context.
- Configure supported Cloud IDS endpoints and Packet Mirroring paths for the intended traffic.
- Test identities can query only their permitted log views and cannot alter audit collection.
Explanation
Correct Answers
A:Assign narrowly scoped Cloud Logging view access and separate log configuration permissions. This is the intended action for Least privilege access to audit logs.
E:Test identities can query only their permitted log views and cannot alter audit collection. This is directly observable validation of the Least privilege access to audit logs result.
Incorrect Answers
B:Grant project Owner solely to let a contractor search one audit log. This is not part of a safe or effective Least privilege access to audit logs design. Giving all developers logging administrator and private-log access may expose sensitive audit metadata.
C:Correlate supported Cloud Storage Data Access logs with IAM bindings and network context. This serves the different Cloud Storage audit trail for exfiltration objective, not the selected Least privilege access to audit logs plan. Log viewer roles and sink or retention administration require distinct privileges.
D:Configure supported Cloud IDS endpoints and Packet Mirroring paths for the intended traffic. This serves the different Cloud Intrusion Detection System alerts objective, not the selected Least privilege access to audit logs plan. Log viewer roles and sink or retention administration require distinct privileges.