Google Professional Cloud Security Engineer Practice Test 88
Question 870
Security finds an unused Google Cloud API enabled in a high-sensitivity project. Which approach BEST meets the requirement while respecting the system constraints?
- Inventory enabled services and apply supported service-use IAM or organization restrictions.
- Configure a Cloud DNS response policy with controlled rules and appropriate VPC attachment.
- Configure supported Cloud Armor throttling or rate-based ban rules at suitable match scope.
- Remove an API link from Cloud Console favorites and assume the API is disabled for the project.
Explanation
Correct Answer
A:Inventory enabled services and apply supported service-use IAM or organization restrictions. Enabled service APIs and permission to call them are distinct controls. Verification should demonstrate that unapproved API enablement and access attempts are prevented while needed services remain operational.
Incorrect Answers
B:Configure a Cloud DNS response policy with controlled rules and appropriate VPC attachment. This primarily addresses Cloud DNS response policy filtering, not the specific API exposure restriction and service inventory decision. Here, enabled service APIs and permission to call them are distinct controls.
C:Configure supported Cloud Armor throttling or rate-based ban rules at suitable match scope. This primarily addresses Cloud Armor rate limiting and bot mitigation, not the specific API exposure restriction and service inventory decision. Here, enabled service APIs and permission to call them are distinct controls.
D:Remove an API link from Cloud Console favorites and assume the API is disabled for the project. This is an unsafe or ineffective shortcut for API exposure restriction and service inventory. Disabling an API used by dependent managed services can disrupt workloads.
Question 871
A regulated program needs to verify which Google Cloud services are in scope of a specific third-party assurance report. Which practical correction or implementation decision is MOST directly appropriate?
- Verify service inclusion, reporting period and customer responsibilities in supporting documents.
- Test raw-table denial, re-identification risk and audit evidence with separate researcher roles.
- Assume every beta API is compliant with every standard because another Google Cloud product has an audit report.
- Trace encrypted resources to key versions, regions and relevant IAM assignments.
Explanation
Correct Answer
A:Verify service inclusion, reporting period and customer responsibilities in supporting documents. The intended behavior can be checked because the architecture uses eligible services with customer-owned compensating controls documented.
Incorrect Answers
B:Test raw-table denial, re-identification risk and audit evidence with separate researcher roles. This could help Healthcare data privacy segmentation, but it does not resolve the Vendor shared-control contract and service eligibility case. Provider attestations cover specified services and periods, not every customer configuration or integration.
C:Assume every beta API is compliant with every standard because another Google Cloud product has an audit report. This would not correct the Vendor shared-control contract and service eligibility workflow. Assuming a vendor certificate transfers regulatory responsibility to the customer workload may produce audit gaps.
D:Trace encrypted resources to key versions, regions and relevant IAM assignments. This could help Encryption compliance and external key governance, but it does not resolve the Vendor shared-control contract and service eligibility case. Provider attestations cover specified services and periods, not every customer configuration or integration.
Question 872
An auditor needs evidence that an external key dependency was configured and monitored rather than merely promised. An engineer must explain the recommendation for Encryption compliance and external key governance. Which underlying principle is the MOST accurate?
- Compliance data boundaries include telemetry, backups and third-party processors as well as primary databases.
- Residency compliance depends on the full processing and backup path, not solely a displayed dataset name.
- Encryption compliance requires distinguishing key ownership from default provider encryption capabilities.
- Model inference endpoints are APIs that still require authorization, quotas and protected logging.
Explanation
Correct Answer
C:Encryption compliance requires distinguishing key ownership from default provider encryption capabilities. Therefore the implementation decision is to use compliant CMEK or EKM architecture and document key ownership, rotation and access controls.
Incorrect Answers
A:Calling default encryption customer-owned without actual customer key management is misleading. This describes the separate Cross-border logs and downstream data processors mechanism; the present case instead requires Encryption compliance and external key governance.
B:Calling default encryption customer-owned without actual customer key management is misleading. Residency compliance depends on the full processing and backup path, not solely a displayed dataset name.
D:Calling default encryption customer-owned without actual customer key management is misleading. This describes the separate Managed AI endpoint access controls mechanism; the present case instead requires Encryption compliance and external key governance.
Question 873
A regulated analytics job must protect data while it is processed in VM memory. After the recommended Confidential VM memory protection change is implemented, which observation MOST directly verifies that it works?
- Attestation and platform configuration show the expected confidential computing capability is enabled.
- The service respects external key availability and data-access behavior under revocation tests.
- Crypto operations use the intended hardware protection and service integration remains compatible.
- Authorized bucket principals retain access and object-specific ACL exceptions stop applying.
Explanation
Correct Answer
A:Attestation and platform configuration show the expected confidential computing capability is enabled. This directly tests whether the Confidential VM memory protection goal was met. Confidential Computing reduces exposure of data in use but does not eliminate the need for identity and encryption controls.
Incorrect Answers
B:The service respects external key availability and data-access behavior under revocation tests. This is evidence about External Key Manager custody, not direct proof of the required Confidential VM memory protection behavior. The relevant check is that attestation and platform configuration show the expected confidential computing capability is enabled.
C:Crypto operations use the intended hardware protection and service integration remains compatible. This is evidence about Cloud HSM versus software-protected keys, not direct proof of the required Confidential VM memory protection behavior. The relevant check is that attestation and platform configuration show the expected confidential computing capability is enabled.
D:Authorized bucket principals retain access and object-specific ACL exceptions stop applying. This is evidence about Cloud Storage uniform bucket-level permissions, not direct proof of the required Confidential VM memory protection behavior. The relevant check is that attestation and platform configuration show the expected confidential computing capability is enabled.
Question 874
A container registry stores application images that may include outdated vulnerable packages. Which approach BEST meets the requirement while respecting the system constraints?
- Enable Binary Authorization enforcement on GKE with an appropriate signed attestation policy.
- Set an image tag to secure and assume Artifact Registry automatically patches all installed libraries.
- Enable supported container vulnerability scanning and connect findings to release review.
- Scan infrastructure-as-code plans against approved security guardrails and require review before deployment.
Explanation
Correct Answer
C:Enable supported container vulnerability scanning and connect findings to release review. Image vulnerability scanning inspects artifacts but is distinct from deploy-time admission enforcement. Verification should demonstrate that build candidates expose relevant vulnerability findings and unapproved critical issues block promotion.
Incorrect Answers
A:Enable Binary Authorization enforcement on GKE with an appropriate signed attestation policy. This primarily addresses Binary Authorization GKE admission, not the specific Artifact Registry vulnerability scanning policy decision. Here, image vulnerability scanning inspects artifacts but is distinct from deploy-time admission enforcement.
B:Set an image tag to secure and assume Artifact Registry automatically patches all installed libraries. This is an unsafe or ineffective shortcut for Artifact Registry vulnerability scanning policy. Treating a successful image push as proof all dependencies are free of known CVEs may ship unsafe images.
D:Scan infrastructure-as-code plans against approved security guardrails and require review before deployment. This primarily addresses Infrastructure as code security validation, not the specific Artifact Registry vulnerability scanning policy decision. Here, image vulnerability scanning inspects artifacts but is distinct from deploy-time admission enforcement.
Question 875
Security needs to identify which principal read sensitive Cloud Storage objects. Which approach BEST meets the requirement while respecting the system constraints?
- Assign narrowly scoped Cloud Logging view access and separate log configuration permissions.
- Enable appropriate firewall policy rule logging and inspect effective rules for denied connections.
- Delete the Cloud Logging viewer role and assume data access audit events will automatically be recorded.
- Enable and configure supported Data Access audit logging where needed and verify permissions and retention.
Explanation
Correct Answer
D:Enable and configure supported Data Access audit logging where needed and verify permissions and retention. Data Access logs have different availability and configuration behavior from Admin Activity logs. Verification should demonstrate that authorized test reads produce the expected data access evidence while logging costs are understood.
Incorrect Answers
A:Assign narrowly scoped Cloud Logging view access and separate log configuration permissions. This primarily addresses Least privilege access to audit logs, not the specific Data Access Audit Logs enablement and cost decision. Here, data Access logs have different availability and configuration behavior from Admin Activity logs.
B:Enable appropriate firewall policy rule logging and inspect effective rules for denied connections. This primarily addresses Firewall rule logging and deny analysis, not the specific Data Access Audit Logs enablement and cost decision. Here, data Access logs have different availability and configuration behavior from Admin Activity logs.
C:Delete the Cloud Logging viewer role and assume data access audit events will automatically be recorded. This is an unsafe or ineffective shortcut for Data Access Audit Logs enablement and cost. Assuming all service data reads are logged by default may leave incident evidence gaps.
Question 876
A terminated integration still has a service account that should lose access without breaking other approved jobs. Which approach BEST meets the requirement while respecting the system constraints?
- Enforce the applicable organization policy that restricts service account key creation with tightly reviewed exceptions.
- Change the service account display name and assume all tokens immediately become invalid.
- Use GKE Workload Identity Federation and bind only the intended Kubernetes workload identity to the required resource.
- Inventory workloads using the identity and disable or suspend the affected service account with a recovery plan.
Explanation
Correct Answer
D:Inventory workloads using the identity and disable or suspend the affected service account with a recovery plan. Disabling an identity affects all callers using it, not just one label or attached role. Verification should demonstrate that unauthorized API calls stop and explicitly approved dependent workloads are migrated or remediated.
Incorrect Answers
A:Enforce the applicable organization policy that restricts service account key creation with tightly reviewed exceptions. This primarily addresses Service account key creation organization policy, not the specific Service account disabling and dependency mapping decision. Here, disabling an identity affects all callers using it, not just one label or attached role.
B:Change the service account display name and assume all tokens immediately become invalid. This is an unsafe or ineffective shortcut for Service account disabling and dependency mapping. Blindly deleting a shared service account can cause unplanned production outages.
C:Use GKE Workload Identity Federation and bind only the intended Kubernetes workload identity to the required resource. This primarily addresses GKE workload identity binding, not the specific Service account disabling and dependency mapping decision. Here, disabling an identity affects all callers using it, not just one label or attached role.
Question 877
A regulated financial dataset must remain in an approved country or geographic region. After the recommended Data residency and regionalization validation change is implemented, which observation MOST directly verifies that it works?
- Violation tests reject forbidden resource settings and policy ownership is documented.
- Verified resource metadata and data flows stay within the approved geographic policy boundary.
- Only explicitly authorized payment-processing flows reach in-scope resources.
- Security-key sign-in succeeds for enrolled administrators while unsupported fallback paths are governed.
Explanation
Correct Answer
B:Verified resource metadata and data flows stay within the approved geographic policy boundary. This directly tests whether the Data residency and regionalization validation goal was met. Residency compliance depends on the full processing and backup path, not solely a displayed dataset name.
Incorrect Answers
A:Violation tests reject forbidden resource settings and policy ownership is documented. This is evidence about Organization policy compliance control mapping, not direct proof of the required Data residency and regionalization validation behavior. The relevant check is that verified resource metadata and data flows stay within the approved geographic policy boundary.
C:Only explicitly authorized payment-processing flows reach in-scope resources. This is evidence about PCI workload network segmentation, not direct proof of the required Data residency and regionalization validation behavior. The relevant check is that verified resource metadata and data flows stay within the approved geographic policy boundary.
D: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 Data residency and regionalization validation behavior. The relevant check is that verified resource metadata and data flows stay within the approved geographic policy boundary.
Question 878
A new organization policy breaks legitimate service provisioning after rollout. Select TWO statements that correctly combine the Hierarchy-scoped exception and policy rollback method with evidence or its governing principle.
- Disable the entire organization policy set permanently to fix one failed deployment.
- Grant only the narrow permitted policy exception and retain documented rollback and audit approval.
- Use folders and project placement aligned with environment boundaries and inherited guardrails.
- Define and enforce an applicable custom organization policy constraint with supported resource rules.
- The specific approved project works while other descendants remain protected by the broader constraint.
Explanation
Correct Answers
B:Grant only the narrow permitted policy exception and retain documented rollback and audit approval. This is the intended action for Hierarchy-scoped exception and policy rollback.
E:The specific approved project works while other descendants remain protected by the broader constraint. This is directly observable validation of the Hierarchy-scoped exception and policy rollback result.
Incorrect Answers
A:Disable the entire organization policy set permanently to fix one failed deployment. This is not part of a safe or effective Hierarchy-scoped exception and policy rollback design. A blanket top-level policy reset can expose every child project to avoid one outage.
C:Use folders and project placement aligned with environment boundaries and inherited guardrails. This serves the different Project folder segmentation for environments objective, not the selected Hierarchy-scoped exception and policy rollback plan. Policy inheritance and exceptions must be understood before overriding organization or folder guardrails.
D:Define and enforce an applicable custom organization policy constraint with supported resource rules. This serves the different Custom organization policy on resource attributes objective, not the selected Hierarchy-scoped exception and policy rollback plan. Policy inheritance and exceptions must be understood before overriding organization or folder guardrails.
Question 879
A regulated program needs to verify which Google Cloud services are in scope of a specific third-party assurance report. Testing exposes this failure: Assuming a vendor certificate transfers regulatory responsibility to the customer workload may produce audit gaps. Which remediation should be applied FIRST?
- Restrict datasets and share only approved de-identified outputs with monitored access controls.
- Verify service inclusion, reporting period and customer responsibilities in supporting documents.
- Assume every beta API is compliant with every standard because another Google Cloud product has an audit report.
- Classify data and map each class to applicable access, encryption, monitoring and retention controls.
Explanation
Correct Answer
B:Verify service inclusion, reporting period and customer responsibilities in supporting documents. Confirmation requires seeing that the architecture uses eligible services with customer-owned compensating controls documented.
Incorrect Answers
A:Restrict datasets and share only approved de-identified outputs with monitored access controls. It addresses Healthcare data privacy segmentation, not the diagnosed Vendor shared-control contract and service eligibility failure. Assuming a vendor certificate transfers regulatory responsibility to the customer workload may produce audit gaps.
C:Assume every beta API is compliant with every standard because another Google Cloud product has an audit report. This retains the Vendor shared-control contract and service eligibility problem. Provider attestations cover specified services and periods, not every customer configuration or integration.
D:Classify data and map each class to applicable access, encryption, monitoring and retention controls. It addresses Sensitive data classification and policy labels, not the diagnosed Vendor shared-control contract and service eligibility failure. Assuming a vendor certificate transfers regulatory responsibility to the customer workload may produce audit gaps.
Question 880
An admin wants to know why a role bound on a parent folder affects a child project. Select TWO statements that correctly combine the Organization hierarchy and inherited roles method with evidence or its governing principle.
- Child project effective permissions and policy restrictions match the documented parent hierarchy.
- Design organization, folders and projects to reflect governance boundaries and inherited IAM needs.
- Assume every project starts with no inherited roles regardless of its parent folder.
- Configure the supported Compute Engine external-IP restriction organization policy and review project exceptions.
- Use supported organization policy domain-restricted sharing controls with approved identities or exceptions.
Explanation
Correct Answers
A:Child project effective permissions and policy restrictions match the documented parent hierarchy. This is directly observable validation of the Organization hierarchy and inherited roles result.
B:Design organization, folders and projects to reflect governance boundaries and inherited IAM needs. This is the intended action for Organization hierarchy and inherited roles.
Incorrect Answers
C:Assume every project starts with no inherited roles regardless of its parent folder. This is not part of a safe or effective Organization hierarchy and inherited roles design. Misplaced high-level grants can grant permissions to every descendant project.
D:Configure the supported Compute Engine external-IP restriction organization policy and review project exceptions. This serves the different Restricting external IPv4 addresses through org policy objective, not the selected Organization hierarchy and inherited roles plan. IAM grants propagate downward through the Google Cloud resource hierarchy unless constrained by relevant controls.
E:Use supported organization policy domain-restricted sharing controls with approved identities or exceptions. This serves the different Restricting allowed IAM member domains objective, not the selected Organization hierarchy and inherited roles plan. IAM grants propagate downward through the Google Cloud resource hierarchy unless constrained by relevant controls.