Google Professional Cloud Security Engineer Practice Test 19
Question 180
An administrator needs stronger authentication for privileged Cloud Identity users than SMS-only codes. Select TWO statements that correctly combine the Phishing-resistant multi-factor verification method with evidence or its governing principle.
- Assume a strong password completely replaces the need for multi-factor authentication.
- Security-key sign-in succeeds for enrolled administrators while unsupported fallback paths are governed.
- Select the protocol appropriate to identity federation versus delegated API authorization and validate claims.
- Validate token audience and issuer and request only the permissions necessary for the application.
- Enforce supported phishing-resistant 2-Step Verification options for eligible accounts and test recovery.
Explanation
Correct Answers
B:Security-key sign-in succeeds for enrolled administrators while unsupported fallback paths are governed. This is directly observable validation of the Phishing-resistant multi-factor verification result.
E:Enforce supported phishing-resistant 2-Step Verification options for eligible accounts and test recovery. This is the intended action for Phishing-resistant multi-factor verification.
Incorrect Answers
A:Assume a strong password completely replaces the need for multi-factor authentication. This is not part of a safe or effective Phishing-resistant multi-factor verification design. An easily phished one-time passcode may not stop real-time credential relay attacks.
C:Select the protocol appropriate to identity federation versus delegated API authorization and validate claims. This serves the different SAML versus OAuth authentication purpose objective, not the selected Phishing-resistant multi-factor verification plan. Phishing-resistant authenticators bind verification to the legitimate service origin.
D:Validate token audience and issuer and request only the permissions necessary for the application. This serves the different OAuth audience and minimum scopes objective, not the selected Phishing-resistant multi-factor verification plan. Phishing-resistant authenticators bind verification to the legitimate service origin.
Question 181
Application pods should reach a database service but not communicate with unrelated workloads. If the relevant GKE network policy for pod segmentation safeguard is omitted, which outcome is the MOST directly associated failure?
- Attaching broad roles to a common node identity magnifies container escape impact.
- Writing a policy YAML in an unsupported or unenforced cluster does not create isolation.
- A detector with the wrong scope can miss important projects or overwhelm responders with noise.
- Reviewing only bucket configuration does not establish who read a particular object.
Explanation
Correct Answer
B:Writing a policy YAML in an unsupported or unenforced cluster does not create isolation. Kubernetes network policies can restrict pod traffic when enforced by the cluster's networking implementation. The corrective approach is to validate implementation support, selectors and policy behavior with test pods.
Incorrect Answers
A:This failure pattern belongs chiefly to GKE Workload Identity for deployment runtime; it is not the failure most directly tested in the GKE network policy for pod segmentation situation.
C:This failure pattern belongs chiefly to Security Health Analytics custom finding; it is not the failure most directly tested in the GKE network policy for pod segmentation situation.
D:This failure pattern belongs chiefly to Cloud Storage audit trail for exfiltration; it is not the failure most directly tested in the GKE network policy for pod segmentation situation.
Question 182
A developer requests broad organization Owner permissions just to read one BigQuery dataset. Select THREE statements that correctly combine the IAM least-privilege role scoping method with evidence or its governing principle.
- IAM allow policy bindings determine which principals may act on resources within a hierarchy.
- Split deployment, access-policy editing and security evidence administration among distinct identities.
- The intended task succeeds without granting administrative privileges to unrelated projects.
- Enable uniform bucket-level access where appropriate and manage object access through IAM.
- Give organization Owner to any user who reports a single permission-denied error.
- Bind a suitable predefined or reviewed custom IAM role at the narrowest supported scope.
Explanation
Correct Answers
A:IAM allow policy bindings determine which principals may act on resources within a hierarchy. This explains why the implementation and evidence fit together.
C:The intended task succeeds without granting administrative privileges to unrelated projects. This is directly observable validation of the IAM least-privilege role scoping result.
F:Bind a suitable predefined or reviewed custom IAM role at the narrowest supported scope. This is the intended action for IAM least-privilege role scoping.
Incorrect Answers
B:Split deployment, access-policy editing and security evidence administration among distinct identities. This serves the different IAM separation of security duties objective, not the selected IAM least-privilege role scoping plan. IAM allow policy bindings determine which principals may act on resources within a hierarchy.
D:Enable uniform bucket-level access where appropriate and manage object access through IAM. This serves the different Cloud Storage ACL versus IAM with uniform access objective, not the selected IAM least-privilege role scoping plan. IAM allow policy bindings determine which principals may act on resources within a hierarchy.
E:Give organization Owner to any user who reports a single permission-denied error. This is not part of a safe or effective IAM least-privilege role scoping design. Broad primitive roles can expose multiple projects and protected datasets unnecessarily.
Question 183
A new service perimeter could block hundreds of cross-project BigQuery queries. Which approach BEST meets the requirement while respecting the system constraints?
- Put the proposed VPC Service Controls configuration in dry-run mode and inspect violations.
- Treat a dry-run violation log as proof the API request was actually blocked.
- Add narrowly scoped VPC Service Controls ingress or egress rules using principal and service operation constraints.
- Separate tiers using dedicated service identities, firewalls and narrow subnet boundaries.
Explanation
Correct Answer
A:Put the proposed VPC Service Controls configuration in dry-run mode and inspect violations. VPC Service Controls dry-run reports policy violations without blocking them. Verification should demonstrate that logs identify would-be denied API calls while existing workloads continue to operate.
Incorrect Answers
B:Treat a dry-run violation log as proof the API request was actually blocked. This is an unsafe or ineffective shortcut for VPC Service Controls dry-run evaluation. Enforcing an untested perimeter can cause production data pipeline failures.
C: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 Service Controls dry-run evaluation decision. Here, vPC Service Controls dry-run reports policy violations without blocking them.
D:Separate tiers using dedicated service identities, firewalls and narrow subnet boundaries. This primarily addresses N-tier east-west network segmentation, not the specific VPC Service Controls dry-run evaluation decision. Here, vPC Service Controls dry-run reports policy violations without blocking them.
Question 184
Security wants to identify legitimate dependency traffic before enforcing restrictions. Select TWO statements that correctly combine the VPC Service Controls dry-run evaluation method with evidence or its governing principle.
- Design direct supported connectivity and routes while recognizing VPC peering non-transitivity.
- Apply VPC Service Controls perimeters to supported data services with least-privilege ingress and egress policies.
- Put the proposed VPC Service Controls configuration in dry-run mode and inspect violations.
- Treat a dry-run violation log as proof the API request was actually blocked.
- Logs identify would-be denied API calls while existing workloads continue to operate.
Explanation
Correct Answers
C:Put the proposed VPC Service Controls configuration in dry-run mode and inspect violations. This is the intended action for VPC Service Controls dry-run evaluation.
E:Logs identify would-be denied API calls while existing workloads continue to operate. This is directly observable validation of the VPC Service Controls dry-run evaluation result.
Incorrect Answers
A:Design direct supported connectivity and routes while recognizing VPC peering non-transitivity. This serves the different VPC Network Peering transitivity limits objective, not the selected VPC Service Controls dry-run evaluation plan. VPC Service Controls dry-run reports policy violations without blocking them.
B: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 VPC Service Controls dry-run evaluation plan. VPC Service Controls dry-run reports policy violations without blocking them.
D:Treat a dry-run violation log as proof the API request was actually blocked. This is not part of a safe or effective VPC Service Controls dry-run evaluation design. Enforcing an untested perimeter can cause production data pipeline failures.
Question 185
A data owner needs assurance that in-use data protections do not replace storage and IAM controls. An engineer must explain the recommendation for Confidential VM memory protection. Which underlying principle is the MOST accurate?
- Confidential Computing reduces exposure of data in use but does not eliminate the need for identity and encryption controls.
- Cloud KMS separates administrative operations from cryptographic actions through IAM permissions.
- Metadata server tokens reflect attached workload identity and must be protected from untrusted code paths.
- Cloud EKM shifts external key custody and introduces dependency on external key-management availability.
Explanation
Correct Answer
A:Confidential Computing reduces exposure of data in use but does not eliminate the need for identity and encryption controls. Therefore the implementation decision is to choose supported Confidential VM or confidential computing configuration with appropriate machine and region.
Incorrect Answers
B:Assuming confidential memory automatically blocks malicious application code is unsafe. This describes the separate Cloud KMS crypto key role separation mechanism; the present case instead requires Confidential VM memory protection.
C:Assuming confidential memory automatically blocks malicious application code is unsafe. Metadata server tokens reflect attached workload identity and must be protected from untrusted code paths.
D:Assuming confidential memory automatically blocks malicious application code is unsafe. This describes the separate External Key Manager custody mechanism; the present case instead requires Confidential VM memory protection.
Question 186
Network engineers think Interconnect's private routing automatically satisfies application encryption policy. Select TWO statements that correctly combine the Cloud Interconnect transport and encryption method with evidence or its governing principle.
- Choose Cloud Interconnect for suitable dedicated connectivity and layer required encryption or MACsec where supported.
- Disable TLS on all internal applications because a Cloud Interconnect link is private.
- Throughput and circuit resilience meet requirements and traffic encryption is demonstrated separately.
- Configure supported restricted.googleapis.com DNS and routing where the perimeter design requires it.
- Configure Cloud NAT with appropriate gateway, addresses and subnet egress coverage.
Explanation
Correct Answers
A:Choose Cloud Interconnect for suitable dedicated connectivity and layer required encryption or MACsec where supported. This is the intended action for Cloud Interconnect transport and encryption.
C:Throughput and circuit resilience meet requirements and traffic encryption is demonstrated separately. This is directly observable validation of the Cloud Interconnect transport and encryption result.
Incorrect Answers
B:Disable TLS on all internal applications because a Cloud Interconnect link is private. This is not part of a safe or effective Cloud Interconnect transport and encryption design. Assuming every Interconnect circuit is automatically encrypted end to end can violate policy.
D:Configure supported restricted.googleapis.com DNS and routing where the perimeter design requires it. This serves the different Restricted Google APIs VIP for perimeters objective, not the selected Cloud Interconnect transport and encryption plan. Private transport connectivity is distinct from cryptographic confidentiality and encrypted tunnel requirements.
E:Configure Cloud NAT with appropriate gateway, addresses and subnet egress coverage. This serves the different Cloud NAT outbound without inbound exposure objective, not the selected Cloud Interconnect transport and encryption plan. Private transport connectivity is distinct from cryptographic confidentiality and encrypted tunnel requirements.
Question 187
A key owner needs new object writes to use an updated Cloud KMS primary key version. After the recommended Customer-managed key rotation policy change is implemented, which observation MOST directly verifies that it works?
- Supported resources use intended key custody and policy records explain default versus customer-managed behavior.
- Test identities receive masked or denied sensitive columns while authorized principals receive approved fields.
- Test users can administer key settings or decrypt only according to their distinct approved roles.
- New writes use the intended version and old encrypted data remains readable during planned migration.
Explanation
Correct Answer
D:New writes use the intended version and old encrypted data remains readable during planned migration. This directly tests whether the Customer-managed key rotation policy goal was met. Rotating a key typically changes the primary version for new operations and does not necessarily re-encrypt existing data.
Incorrect Answers
A:Supported resources use intended key custody and policy records explain default versus customer-managed behavior. This is evidence about Default at-rest encryption versus CMEK, not direct proof of the required Customer-managed key rotation policy behavior. The relevant check is that new writes use the intended version and old encrypted data remains readable during planned migration.
B:Test identities receive masked or denied sensitive columns while authorized principals receive approved fields. This is evidence about BigQuery column-level policy tags and masking, not direct proof of the required Customer-managed key rotation policy behavior. The relevant check is that new writes use the intended version and old encrypted data remains readable during planned migration.
C:Test users can administer key settings or decrypt only according to their distinct approved roles. This is evidence about Cloud KMS crypto key role separation, not direct proof of the required Customer-managed key rotation policy behavior. The relevant check is that new writes use the intended version and old encrypted data remains readable during planned migration.
Question 188
A privacy team wants the same protected identifier to join records without revealing original values. Select TWO statements that correctly combine the Sensitive Data Protection deterministic de-identification method with evidence or its governing principle.
- Configure a supported BigQuery row access policy tied to approved identities and predicates.
- Configure supported deterministic tokenization or cryptographic de-identification with restricted key access.
- Authorized datasets join on protected tokens while direct values remain excluded from analyst views.
- Publish a controlled authorized view or supported approved dataset access configuration.
- Replace names with sequential public row numbers and assume joins are automatically privacy-safe.
Explanation
Correct Answers
B:Configure supported deterministic tokenization or cryptographic de-identification with restricted key access. This is the intended action for Sensitive Data Protection deterministic de-identification.
C:Authorized datasets join on protected tokens while direct values remain excluded from analyst views. This is directly observable validation of the Sensitive Data Protection deterministic de-identification result.
Incorrect Answers
A:Configure a supported BigQuery row access policy tied to approved identities and predicates. This serves the different BigQuery row-level access policy objective, not the selected Sensitive Data Protection deterministic de-identification plan. Deterministic pseudonymization preserves matching patterns and is different from irreversible deletion.
D:Publish a controlled authorized view or supported approved dataset access configuration. This serves the different BigQuery authorized views objective, not the selected Sensitive Data Protection deterministic de-identification plan. Deterministic pseudonymization preserves matching patterns and is different from irreversible deletion.
E:Replace names with sequential public row numbers and assume joins are automatically privacy-safe. This is not part of a safe or effective Sensitive Data Protection deterministic de-identification design. Publishing tokenization keys alongside datasets can permit re-identification.
Question 189
A suspected lateral connection leaves no application logs but should appear in sampled network flow telemetry. An engineer must explain the recommendation for VPC Flow Logs traffic analysis. Which underlying principle is the MOST accurate?
- Firewall rule logging provides policy decision evidence distinct from basic network flow summaries.
- VPC Flow Logs summarize network traffic metadata rather than full decrypted application content.
- Kubernetes network policies can restrict pod traffic when enforced by the cluster's networking implementation.
- Containment, evidence preservation and recovery are coordinated security operations rather than one dashboard click.
Explanation
Correct Answer
B:VPC Flow Logs summarize network traffic metadata rather than full decrypted application content. Therefore the implementation decision is to configure supported VPC Flow Logs at intended subnet sampling and aggregation settings.
Incorrect Answers
A:Firewall rule logging provides policy decision evidence distinct from basic network flow summaries. This describes the separate Firewall rule logging and deny analysis mechanism; the present case instead requires VPC Flow Logs traffic analysis. Treating sampled flow metadata as complete packet capture may hide short or unobserved exchanges.
C:Kubernetes network policies can restrict pod traffic when enforced by the cluster's networking implementation. This describes the separate GKE network policy for pod segmentation mechanism; the present case instead requires VPC Flow Logs traffic analysis. Treating sampled flow metadata as complete packet capture may hide short or unobserved exchanges.
D:Containment, evidence preservation and recovery are coordinated security operations rather than one dashboard click. This describes the separate Incident response alert routing and containment mechanism; the present case instead requires VPC Flow Logs traffic analysis. Treating sampled flow metadata as complete packet capture may hide short or unobserved exchanges.
Question 190
An organization must import approved cryptographic key material generated outside Google Cloud. Which approach BEST meets the requirement while respecting the system constraints?
- Configure supported TLS trust-chain validation and modern transport security settings on each relevant hop.
- Use supported Cloud KMS import jobs and validate imported key version state under key policy.
- Select a supported Cloud HSM protection level for the relevant Cloud KMS key.
- Upload the raw master key into an unaudited Cloud Storage public bucket to enable import.
Explanation
Correct Answer
B:Use supported Cloud KMS import jobs and validate imported key version state under key policy. Imported key material requires compatible algorithms and a protected import workflow. Verification should demonstrate that imported versions are usable only by authorized services and key origin records remain traceable.
Incorrect Answers
A:Configure supported TLS trust-chain validation and modern transport security settings on each relevant hop. This primarily addresses TLS certificate trust and cipher policy, not the specific Cloud KMS imported key material decision. Here, imported key material requires compatible algorithms and a protected import workflow.
C:Select a supported Cloud HSM protection level for the relevant Cloud KMS key. This primarily addresses Cloud HSM versus software-protected keys, not the specific Cloud KMS imported key material decision. Here, imported key material requires compatible algorithms and a protected import workflow.
D:Upload the raw master key into an unaudited Cloud Storage public bucket to enable import. This is an unsafe or ineffective shortcut for Cloud KMS imported key material. Copying raw key bytes into an unencrypted text field undermines key custody.