Google Professional Cloud Security Engineer Practice Test 62
Question 610
A compromised application process attempts to obtain credentials from the VM metadata service. Which approach BEST meets the requirement while respecting the system constraints?
- Store approved secrets in Secret Manager versions and grant secret access only to intended workloads.
- Use dedicated least-privileged runtime identities and harden metadata access according to platform support.
- Assume hiding the metadata IP address in application comments prevents compromised code from reaching it.
- Configure appropriate BigQuery policy tags or data masking policies and targeted access roles.
Explanation
Correct Answer
B:Use dedicated least-privileged runtime identities and harden metadata access according to platform support. Metadata server tokens reflect attached workload identity and must be protected from untrusted code paths. Verification should demonstrate that the workload retains required API access without broad metadata-derived permissions.
Incorrect Answers
A:Store approved secrets in Secret Manager versions and grant secret access only to intended workloads. This primarily addresses Secret Manager versioning and least privilege, not the specific Compute metadata exposure hardening decision. Here, metadata server tokens reflect attached workload identity and must be protected from untrusted code paths.
C:Assume hiding the metadata IP address in application comments prevents compromised code from reaching it. This is an unsafe or ineffective shortcut for Compute metadata exposure hardening. An instance with Owner-level credentials makes metadata token theft especially damaging.
D:Configure appropriate BigQuery policy tags or data masking policies and targeted access roles. This primarily addresses BigQuery column-level policy tags and masking, not the specific Compute metadata exposure hardening decision. Here, metadata server tokens reflect attached workload identity and must be protected from untrusted code paths.
Question 611
A service project tries to create subnets that should be governed by the host networking team. Select TWO statements that correctly combine the Shared VPC host and service project boundaries method with evidence or its governing principle.
- Service-project instances attach to approved host subnets without receiving unnecessary network administrator roles.
- Configure ordinary VPC peering and claim it automatically creates Shared VPC host ownership.
- Apply VPC Service Controls perimeters to supported data services with least-privilege ingress and egress policies.
- Configure Shared VPC with host and service projects and appropriate subnet-use IAM grants.
- Attach a supported Access Context Manager access level to the relevant perimeter policy.
Explanation
Correct Answers
A:Service-project instances attach to approved host subnets without receiving unnecessary network administrator roles. This is directly observable validation of the Shared VPC host and service project boundaries result.
D:Configure Shared VPC with host and service projects and appropriate subnet-use IAM grants. This is the intended action for Shared VPC host and service project boundaries.
Incorrect Answers
B:Configure ordinary VPC peering and claim it automatically creates Shared VPC host ownership. This is not part of a safe or effective Shared VPC host and service project boundaries design. Granting service developers host-project Owner access undermines network isolation.
C:Apply VPC Service Controls perimeters to supported data services with least-privilege ingress and egress policies. This serves the different VPC Service Controls service perimeter objective, not the selected Shared VPC host and service project boundaries plan. Shared VPC separates centralized network ownership from application project resource ownership.
E:Attach a supported Access Context Manager access level to the relevant perimeter policy. This serves the different Access levels with perimeter identity trust objective, not the selected Shared VPC host and service project boundaries plan. Shared VPC separates centralized network ownership from application project resource ownership.
Question 612
A data owner needs assurance that in-use data protections do not replace storage and IAM controls. Testing exposes this failure: Assuming confidential memory automatically blocks malicious application code is unsafe. Which remediation should be applied FIRST?
- Configure supported Cloud Storage lifecycle rules with audited age and object conditions.
- Apply a suitable bucket retention policy and evaluate Bucket Lock only after approval.
- Test supported machine family, image compatibility and confidential mode evidence.
- Enable bucket CMEK and assume the application memory is now confidentially encrypted.
Explanation
Correct Answer
C:Test supported machine family, image compatibility and confidential mode evidence. Confirmation requires seeing that attestation and platform configuration show the expected confidential computing capability is enabled.
Incorrect Answers
A:Configure supported Cloud Storage lifecycle rules with audited age and object conditions. It addresses Cloud Storage object lifecycle transition, not the diagnosed Confidential VM memory protection failure. Assuming confidential memory automatically blocks malicious application code is unsafe.
B:Apply a suitable bucket retention policy and evaluate Bucket Lock only after approval. It addresses Cloud Storage retention policy and Bucket Lock, not the diagnosed Confidential VM memory protection failure. Assuming confidential memory automatically blocks malicious application code is unsafe.
D:Enable bucket CMEK and assume the application memory is now confidentially encrypted. This retains the Confidential VM memory protection problem. Confidential Computing reduces exposure of data in use but does not eliminate the need for identity and encryption controls.
Question 613
A company wants internal VMs to block resolution of known malicious hostnames. After the recommended Cloud DNS response policy filtering change is implemented, which observation MOST directly verifies that it works?
- Restricted clients receive the expected filtered response without affecting unrelated resolvers.
- Cross-perimeter attempts to restricted services are denied while required in-perimeter workflows work.
- Test traffic generates expected inspection findings and permitted requests still succeed.
- Packet tests and firewall logs show expected policy evaluation for allowed and blocked flows.
Explanation
Correct Answer
A:Restricted clients receive the expected filtered response without affecting unrelated resolvers. This directly tests whether the Cloud DNS response policy filtering goal was met. DNS response policies can override name resolution for attached networks but do not block all direct-IP communication.
Incorrect Answers
B:Cross-perimeter attempts to restricted services are denied while required in-perimeter workflows work. This is evidence about VPC Service Controls service perimeter, not direct proof of the required Cloud DNS response policy filtering behavior. The relevant check is that restricted clients receive the expected filtered response without affecting unrelated resolvers.
C:Test traffic generates expected inspection findings and permitted requests still succeed. This is evidence about Cloud NGFW application-layer inspection, not direct proof of the required Cloud DNS response policy filtering behavior. The relevant check is that restricted clients receive the expected filtered response without affecting unrelated resolvers.
D:Packet tests and firewall logs show expected policy evaluation for allowed and blocked flows. This is evidence about Hierarchical Cloud NGFW policy ordering, not direct proof of the required Cloud DNS response policy filtering behavior. The relevant check is that restricted clients receive the expected filtered response without affecting unrelated resolvers.
Question 614
A bucket owner wants to delete obsolete temporary exports automatically without removing retained legal evidence. Select TWO statements that correctly combine the Cloud Storage object lifecycle transition method with evidence or its governing principle.
- Follow approved key-version disable and destruction scheduling with dependency impact checks.
- Rename a bucket Archive and assume its objects automatically change storage class at day 30.
- Configure supported Cloud Storage lifecycle rules with audited age and object conditions.
- Test objects transition or expire according to policy while exempt legal artifacts are preserved.
- Apply a suitable bucket retention policy and evaluate Bucket Lock only after approval.
Explanation
Correct Answers
C:Configure supported Cloud Storage lifecycle rules with audited age and object conditions. This is the intended action for Cloud Storage object lifecycle transition.
D:Test objects transition or expire according to policy while exempt legal artifacts are preserved. This is directly observable validation of the Cloud Storage object lifecycle transition result.
Incorrect Answers
A:Follow approved key-version disable and destruction scheduling with dependency impact checks. This serves the different KMS key version destruction and restore window objective, not the selected Cloud Storage object lifecycle transition plan. Storage lifecycle rules automate object state changes under conditions separate from IAM authorization.
B:Rename a bucket Archive and assume its objects automatically change storage class at day 30. This is not part of a safe or effective Cloud Storage object lifecycle transition design. Broad delete rules can remove records required by retention policy.
E:Apply a suitable bucket retention policy and evaluate Bucket Lock only after approval. This serves the different Cloud Storage retention policy and Bucket Lock objective, not the selected Cloud Storage object lifecycle transition plan. Storage lifecycle rules automate object state changes under conditions separate from IAM authorization.
Question 615
A backend must reject a validly signed identity token issued for a different service audience. Which practical correction or implementation decision is MOST directly appropriate?
- Trust every signed bearer token regardless of audience and permitted OAuth scopes.
- Test token claims and authorization denial using a token issued for another client.
- Test token/session lifecycle behavior for permitted accounts and common admin workflows.
- Validate signing certificates, recovery procedures and negative authentication cases in a pilot.
Explanation
Correct Answer
B:Test token claims and authorization denial using a token issued for another client. The intended behavior can be checked because tokens for the wrong audience are rejected and users are not prompted for unrelated scopes.
Incorrect Answers
A:Trust every signed bearer token regardless of audience and permitted OAuth scopes. This would not correct the OAuth audience and minimum scopes workflow. Overbroad scopes or missing audience checks can expose unrelated APIs.
C: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 OAuth audience and minimum scopes case. Token validity includes intended recipient and authorization context, not just signature format.
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 OAuth audience and minimum scopes case. Token validity includes intended recipient and authorization context, not just signature format.
Question 616
A company keeps its primary dataset in one region but exports diagnostic logs to an overseas SIEM. Which approach BEST meets the requirement while respecting the system constraints?
- Assume geographic compliance is complete because the primary Cloud Storage bucket uses a regional location.
- Inventory downstream exports and enforce approved destination, redaction and retention rules.
- Map controls to documented incident runbooks, test outcomes and preserved audit logs.
- Configure supported Access Approval settings and authorized approvers for eligible services.
Explanation
Correct Answer
B:Inventory downstream exports and enforce approved destination, redaction and retention rules. Compliance data boundaries include telemetry, backups and third-party processors as well as primary databases. Verification should demonstrate that test log and data flows remain within documented processor and residency permissions.
Incorrect Answers
A:Assume geographic compliance is complete because the primary Cloud Storage bucket uses a regional location. This is an unsafe or ineffective shortcut for Cross-border logs and downstream data processors. Unreviewed log exports may leak personal data even when the primary dataset stays regional.
C:Map controls to documented incident runbooks, test outcomes and preserved audit logs. This primarily addresses SOC control evidence and incident workflow, not the specific Cross-border logs and downstream data processors decision. Here, compliance data boundaries include telemetry, backups and third-party processors as well as primary databases.
D:Configure supported Access Approval settings and authorized approvers for eligible services. This primarily addresses Access Approval Google support access, not the specific Cross-border logs and downstream data processors decision. Here, compliance data boundaries include telemetry, backups and third-party processors as well as primary databases.
Question 617
A company keeps its primary dataset in one region but exports diagnostic logs to an overseas SIEM. After the recommended Cross-border logs and downstream data processors change is implemented, which observation MOST directly verifies that it works?
- Test identities can query only their permitted log views and cannot alter audit collection.
- The inventory maps every regulated data path and assigns an accountable control owner.
- Test log and data flows remain within documented processor and residency permissions.
- A sample alert is triaged, escalated and closed with attributable decision and evidence.
Explanation
Correct Answer
C:Test log and data flows remain within documented processor and residency permissions. This directly tests whether the Cross-border logs and downstream data processors goal was met. Compliance data boundaries include telemetry, backups and third-party processors as well as primary databases.
Incorrect Answers
A:Test identities can query only their permitted log views and cannot alter audit collection. This is evidence about Least privilege access to audit logs, not direct proof of the required Cross-border logs and downstream data processors behavior. The relevant check is that test log and data flows remain within documented processor and residency permissions.
B:The inventory maps every regulated data path and assigns an accountable control owner. This is evidence about Regulatory scope inventory and boundaries, not direct proof of the required Cross-border logs and downstream data processors behavior. The relevant check is that test log and data flows remain within documented processor and residency permissions.
D:A sample alert is triaged, escalated and closed with attributable decision and evidence. This is evidence about SOC control evidence and incident workflow, not direct proof of the required Cross-border logs and downstream data processors behavior. The relevant check is that test log and data flows remain within documented processor and residency permissions.
Question 618
A company forwards selected security events to its external SIEM over approved channels. Which approach BEST meets the requirement while respecting the system constraints?
- Configure an aggregated log sink with appropriate inclusion filters and destination writer permissions.
- Paste raw production access tokens into SIEM logs to make troubleshooting easier.
- Configure a controlled Cloud Logging sink to an approved transport and filter event contents.
- Inspect Cloud Audit Logs Admin Activity entries with precise resource and caller filters.
Explanation
Correct Answer
C:Configure a controlled Cloud Logging sink to an approved transport and filter event contents. Log export requires authorized destination write paths, filters and governance beyond local logging. Verification should demonstrate that the SIEM receives the intended event types while restricted fields and destinations comply with policy.
Incorrect Answers
A:Configure an aggregated log sink with appropriate inclusion filters and destination writer permissions. This primarily addresses Organization aggregated log sink, not the specific External SIEM log export privacy decision. Here, log export requires authorized destination write paths, filters and governance beyond local logging.
B:Paste raw production access tokens into SIEM logs to make troubleshooting easier. This is an unsafe or ineffective shortcut for External SIEM log export privacy. Sending unfiltered audit records to an unapproved external endpoint may disclose sensitive data.
D:Inspect Cloud Audit Logs Admin Activity entries with precise resource and caller filters. This primarily addresses Admin Activity Audit Logs provenance, not the specific External SIEM log export privacy decision. Here, log export requires authorized destination write paths, filters and governance beyond local logging.
Question 619
A regulated organization wants customer approval before applicable Google personnel access customer data for support. If the relevant Access Approval Google support access safeguard is omitted, which outcome is the MOST directly associated failure?
- Unreviewed log exports may leak personal data even when the primary dataset stays regional.
- Sharing the underlying dataset viewer role can reveal more than the intended view.
- Calling default encryption customer-owned without actual customer key management is misleading.
- Assuming Access Approval controls every automated platform operation can misstate its scope.
Explanation
Correct Answer
D:Assuming Access Approval controls every automated platform operation can misstate its scope. Access Approval governs supported Google personnel access workflows and has documented coverage limitations. The corrective approach is to verify supported service coverage, approval routing and expired request behavior.
Incorrect Answers
A:This failure pattern belongs chiefly to Cross-border logs and downstream data processors; it is not the failure most directly tested in the Access Approval Google support access situation.
B:Sharing the underlying dataset viewer role can reveal more than the intended view. This failure pattern belongs chiefly to BigQuery authorized views; it is not the failure most directly tested in the Access Approval Google support access situation. Assuming Access Approval controls every automated platform operation can misstate its scope.
C:Calling default encryption customer-owned without actual customer key management is misleading. This failure pattern belongs chiefly to Encryption compliance and external key governance; it is not the failure most directly tested in the Access Approval Google support access situation. Assuming Access Approval controls every automated platform operation can misstate its scope.
Question 620
A security auditor must review log events without modifying sinks or retention rules. An engineer must explain the recommendation for Least privilege access to audit logs. Which underlying principle is the MOST accurate?
- SCC centralizes supported risk findings but still requires response processes and access configuration.
- Log viewer roles and sink or retention administration require distinct privileges.
- Guest OS patching remains an operational responsibility despite cloud-managed physical infrastructure.
- Security logging retention must be managed independently of application log generation.
Explanation
Correct Answer
B:Log viewer roles and sink or retention administration require distinct privileges. Therefore the implementation decision is to assign narrowly scoped Cloud Logging view access and separate log configuration permissions.
Incorrect Answers
A:SCC centralizes supported risk findings but still requires response processes and access configuration. This describes the separate Security Command Center centralized findings mechanism; the present case instead requires Least privilege access to audit logs. Giving all developers logging administrator and private-log access may expose sensitive audit metadata.
C:Guest OS patching remains an operational responsibility despite cloud-managed physical infrastructure. This describes the separate VM Manager patch orchestration mechanism; the present case instead requires Least privilege access to audit logs. Giving all developers logging administrator and private-log access may expose sensitive audit metadata.
D:Security logging retention must be managed independently of application log generation. This describes the separate Log bucket retention and immutable audit evidence mechanism; the present case instead requires Least privilege access to audit logs. Giving all developers logging administrator and private-log access may expose sensitive audit metadata.