Google Professional Cloud Security Engineer Practice Test 27
Question 260
A company needs to distinguish provider access evidence from customer API read activity. Which practical correction or implementation decision is MOST directly appropriate?
- Trace encrypted resources to key versions, regions and relevant IAM assignments.
- Trace data from ingestion through storage, analytics, backups and deletion.
- Map event coverage and permissions to the relevant provider support event and data scope.
- Assume all Google Cloud workload application requests are Access Transparency provider events.
Explanation
Correct Answer
C:Map event coverage and permissions to the relevant provider support event and data scope. The intended behavior can be checked because provider-related access entries and customer administrative events are categorized correctly.
Incorrect Answers
A: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 Access Transparency provider audit visibility case. Access Transparency provides visibility into certain Google personnel interactions and differs from customer Audit Logs.
B:Trace data from ingestion through storage, analytics, backups and deletion. This could help Regulatory scope inventory and boundaries, but it does not resolve the Access Transparency provider audit visibility case. Access Transparency provides visibility into certain Google personnel interactions and differs from customer Audit Logs.
D:Assume all Google Cloud workload application requests are Access Transparency provider events. This would not correct the Access Transparency provider audit visibility workflow. Treating a missing transparency event as proof no customer account accessed data is incorrect.
Question 261
An exception team requests one legacy key while security requires default prevention elsewhere. Testing exposes this failure: Broad exemptions undermine a policy intended to eliminate long-lived machine credentials. Which remediation should be applied FIRST?
- Separate service account creation, service account user and IAM policy administration privileges.
- Test key-creation denial in representative child projects and audit exceptions.
- Inventory workloads using the identity and disable or suspend the affected service account with a recovery plan.
- Rename a service account to no-key and assume downloading its private key becomes impossible.
Explanation
Correct Answer
B:Test key-creation denial in representative child projects and audit exceptions. Confirmation requires seeing that unapproved principals cannot create new user-managed keys and documented exceptions are traceable.
Incorrect Answers
A:Separate service account creation, service account user and IAM policy administration privileges. It addresses Scoped permission for service account creation, not the diagnosed Service account key creation organization policy failure. Broad exemptions undermine a policy intended to eliminate long-lived machine credentials.
C: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 creation organization policy failure. Broad exemptions undermine a policy intended to eliminate long-lived machine credentials.
D:Rename a service account to no-key and assume downloading its private key becomes impossible. This retains the Service account key creation organization policy problem. Organization policy can reduce credential attack surface independently of IAM permissions.
Question 262
A domain registrar has not published the DS record for a DNSSEC-signed managed zone. Which practical correction or implementation decision is MOST directly appropriate?
- Enable DNSSEC and claim client-to-resolver queries are now private and encrypted.
- Inventory forwarding rules, NAT paths, routes and service endpoint exposure.
- Verify DNSKEY, DS and RRSIG chain before and after key rotation.
- Test proxy routing, inspection policy and client fail-closed behavior under outage.
Explanation
Correct Answer
C:Verify DNSKEY, DS and RRSIG chain before and after key rotation. The intended behavior can be checked because validators confirm signed answers and delegation does not break legitimate name resolution.
Incorrect Answers
A:Enable DNSSEC and claim client-to-resolver queries are now private and encrypted. This would not correct the Cloud DNSSEC authoritative zone protection workflow. Incorrect DS rollover can cause validating resolvers to reject legitimate zone responses.
B:Inventory forwarding rules, NAT paths, routes and service endpoint exposure. This could help Private versus public endpoint design, but it does not resolve the Cloud DNSSEC authoritative zone protection case. DNSSEC authenticates DNS data integrity but does not encrypt DNS queries or content.
D:Test proxy routing, inspection policy and client fail-closed behavior under outage. This could help Secure Web Proxy outbound web egress, but it does not resolve the Cloud DNSSEC authoritative zone protection case. DNSSEC authenticates DNS data integrity but does not encrypt DNS queries or content.
Question 263
A key designer must select protection level without confusing it with application-level encryption scope. Which practical correction or implementation decision is MOST directly appropriate?
- Check protection level, cryptographic algorithm and service support before key creation.
- Put hardware-backed in the key description and assume that changes a software key into an HSM key.
- Verify retention test cases and stakeholder approvals before locking policy settings.
- Test certificate expiry, hostname checks and backend TLS under expected client behavior.
Explanation
Correct Answer
A:Check protection level, cryptographic algorithm and service support before key creation. The intended behavior can be checked because crypto operations use the intended hardware protection and service integration remains compatible.
Incorrect Answers
B:Put hardware-backed in the key description and assume that changes a software key into an HSM key. This would not correct the Cloud HSM versus software-protected keys workflow. Claiming every generic software key meets a hardware custody mandate can fail review.
C:Verify retention test cases and stakeholder approvals before locking policy settings. This could help Cloud Storage retention policy and Bucket Lock, but it does not resolve the Cloud HSM versus software-protected keys case. HSM-backed KMS keys provide a different protection level than software-protected keys.
D:Test certificate expiry, hostname checks and backend TLS under expected client behavior. This could help TLS certificate trust and cipher policy, but it does not resolve the Cloud HSM versus software-protected keys case. HSM-backed KMS keys provide a different protection level than software-protected keys.
Question 264
A security team needs an approved sinkhole response for selected private network clients. An engineer must explain the recommendation for Cloud DNS response policy filtering. Which underlying principle is the MOST accurate?
- Cloud NAT translates eligible outbound connections and is not an inbound proxy or firewall substitute.
- Private addressing changes routability but does not independently confer application authorization.
- Edge rate controls mitigate abusive request volume but do not replace application authentication.
- DNS response policies can override name resolution for attached networks but do not block all direct-IP communication.
Explanation
Correct Answer
D:DNS response policies can override name resolution for attached networks but do not block all direct-IP communication. Therefore the implementation decision is to configure a Cloud DNS response policy with controlled rules and appropriate VPC attachment.
Incorrect Answers
A:A DNS-only block leaves applications that connect directly to numeric addresses unaffected. Cloud NAT translates eligible outbound connections and is not an inbound proxy or firewall substitute.
B:A DNS-only block leaves applications that connect directly to numeric addresses unaffected. Private addressing changes routability but does not independently confer application authorization.
C:A DNS-only block leaves applications that connect directly to numeric addresses unaffected. Edge rate controls mitigate abusive request volume but do not replace application authentication.
Question 265
HR onboarding must automatically create employees and disable accounts after approved termination. Which approach BEST meets the requirement while respecting the system constraints?
- Configure Cloud Identity third-party SAML SSO with validated signing certificate and identity attributes.
- Integrate the authoritative lifecycle source with managed user provisioning, group removal and deprovisioning controls.
- Configure Workforce Identity Federation pools, identity provider mappings and least-privilege IAM bindings.
- Disable an employee's email forwarding while leaving all Google Cloud group memberships active.
Explanation
Correct Answer
B:Integrate the authoritative lifecycle source with managed user provisioning, group removal and deprovisioning controls. Lifecycle controls must revoke identity and group privileges rather than depend solely on removing a laptop. Verification should demonstrate that newly approved staff gain only intended access while departed workers lose it within the policy window.
Incorrect Answers
A:Configure Cloud Identity third-party SAML SSO with validated signing certificate and identity attributes. This primarily addresses SAML enterprise single sign-on, not the specific Cloud Identity user lifecycle automation decision. Here, lifecycle controls must revoke identity and group privileges rather than depend solely on removing a laptop.
C:Configure Workforce Identity Federation pools, identity provider mappings and least-privilege IAM bindings. This primarily addresses Workforce Identity Federation for external workers, not the specific Cloud Identity user lifecycle automation decision. Here, lifecycle controls must revoke identity and group privileges rather than depend solely on removing a laptop.
D:Disable an employee's email forwarding while leaving all Google Cloud group memberships active. This is an unsafe or ineffective shortcut for Cloud Identity user lifecycle automation. Orphan accounts and retained group memberships can expose projects after employment ends.
Question 266
Records must be protected from deletion before an immutable retention period ends. After the recommended Cloud Storage retention policy and Bucket Lock change is implemented, which observation MOST directly verifies that it works?
- Both sides authenticate the expected certificate chain and unauthorized service identities are denied.
- Encrypted identifiers follow the required format and only approved services can reverse them.
- Untrusted certificates fail while approved service connections negotiate authenticated encryption.
- Deletion before retention expiry is rejected and protected retention settings cannot be casually shortened.
Explanation
Correct Answer
D:Deletion before retention expiry is rejected and protected retention settings cannot be casually shortened. This directly tests whether the Cloud Storage retention policy and Bucket Lock goal was met. Locked retention policies can enforce immutability even against privileged operators.
Incorrect Answers
A:Both sides authenticate the expected certificate chain and unauthorized service identities are denied. This is evidence about Mutual TLS for service-to-service identity, not direct proof of the required Cloud Storage retention policy and Bucket Lock behavior. The relevant check is that deletion before retention expiry is rejected and protected retention settings cannot be casually shortened.
B:Encrypted identifiers follow the required format and only approved services can reverse them. This is evidence about Format-preserving encryption data handling, not direct proof of the required Cloud Storage retention policy and Bucket Lock behavior. The relevant check is that deletion before retention expiry is rejected and protected retention settings cannot be casually shortened.
C:Untrusted certificates fail while approved service connections negotiate authenticated encryption. This is evidence about TLS certificate trust and cipher policy, not direct proof of the required Cloud Storage retention policy and Bucket Lock behavior. The relevant check is that deletion before retention expiry is rejected and protected retention settings cannot be casually shortened.
Question 267
A company separates finance production, shared operations and development projects for governance. Which approach BEST meets the requirement while respecting the system constraints?
- 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.
- Change a project display name to Production and assume it moves into the production folder.
- Design organization, folders and projects to reflect governance boundaries and inherited IAM needs.
Explanation
Correct Answer
A:Use folders and project placement aligned with environment boundaries and inherited guardrails. Resource hierarchy shapes both inheritance and administrative blast radius. Verification should demonstrate that tests confirm production policies apply only to intended descendants and sandbox exceptions remain scoped.
Incorrect Answers
B:Define and enforce an applicable custom organization policy constraint with supported resource rules. This primarily addresses Custom organization policy on resource attributes, not the specific Project folder segmentation for environments decision. Here, resource hierarchy shapes both inheritance and administrative blast radius.
C:Change a project display name to Production and assume it moves into the production folder. This is an unsafe or ineffective shortcut for Project folder segmentation for environments. Putting development projects in a production folder can impose unintended controls and privileges.
D:Design organization, folders and projects to reflect governance boundaries and inherited IAM needs. This primarily addresses Organization hierarchy and inherited roles, not the specific Project folder segmentation for environments decision. Here, resource hierarchy shapes both inheritance and administrative blast radius.
Question 268
A public website needs centrally managed TLS termination with healthy private backends. If the relevant HTTPS load balancer certificate and backend TLS safeguard is omitted, which outcome is the MOST directly associated failure?
- A broad deny condition can block valid customers and an unassociated policy protects nothing.
- Terminating TLS at the edge does not automatically encrypt every load balancer-to-backend hop.
- Disabling an API used by dependent managed services can disrupt workloads.
- Allowing ingress from all subnet addresses can enable lateral movement across tiers.
Explanation
Correct Answer
B:Terminating TLS at the edge does not automatically encrypt every load balancer-to-backend hop. Frontend TLS and backend TLS are separate transport protection design choices. The corrective approach is to inspect certificate lifecycle, forwarding rule, backend service and health check settings.
Incorrect Answers
A:This failure pattern belongs chiefly to Cloud Armor WAF rule precedence; it is not the failure most directly tested in the HTTPS load balancer certificate and backend TLS situation.
C:This failure pattern belongs chiefly to API exposure restriction and service inventory; it is not the failure most directly tested in the HTTPS load balancer certificate and backend TLS situation.
D:This failure pattern belongs chiefly to VPC firewall stateful filtering; it is not the failure most directly tested in the HTTPS load balancer certificate and backend TLS situation.
Question 269
Regulators require supported storage resources to comply with a company-specific configuration predicate. If the relevant Custom organization policy on resource attributes safeguard is omitted, which outcome is the MOST directly associated failure?
- A faulty global SSO switch without recovery may lock out administrators.
- An overly permissive domain exception can enable unauthorized external role assignments.
- Untested constraints may unexpectedly block service integrations and maintenance.
- A blanket top-level policy reset can expose every child project to avoid one outage.
Explanation
Correct Answer
C:Untested constraints may unexpectedly block service integrations and maintenance. Custom organization constraints restrict supported resource configurations using explicit evaluated rules. The corrective approach is to deploy policy changes incrementally and validate expected deny results in representative projects.
Incorrect Answers
A:A faulty global SSO switch without recovery may lock out administrators. This failure pattern belongs chiefly to Identity-provider failover and recovery testing; it is not the failure most directly tested in the Custom organization policy on resource attributes situation. Untested constraints may unexpectedly block service integrations and maintenance.
B:An overly permissive domain exception can enable unauthorized external role assignments. This failure pattern belongs chiefly to Restricting allowed IAM member domains; it is not the failure most directly tested in the Custom organization policy on resource attributes situation. Untested constraints may unexpectedly block service integrations and maintenance.
D:A blanket top-level policy reset can expose every child project to avoid one outage. This failure pattern belongs chiefly to Hierarchy-scoped exception and policy rollback; it is not the failure most directly tested in the Custom organization policy on resource attributes situation. Untested constraints may unexpectedly block service integrations and maintenance.
Question 270
A merger introduces renamed users and nested groups that must retain correct cloud membership. Select TWO statements that correctly combine the Cloud Identity directory synchronization method with evidence or its governing principle.
- The scheduled synchronization creates and updates the intended users without unexpectedly deleting cloud identities.
- Use supported Cloud Identity Groups APIs with narrowly scoped permissions and review group change logs.
- Treat a successful SAML login as proof all directory users and groups have been synchronized.
- Configure Workforce Identity Federation pools, identity provider mappings and least-privilege IAM bindings.
- Configure Google Cloud Directory Sync with scoped mapping rules and validate dry-run changes.
Explanation
Correct Answers
A:The scheduled synchronization creates and updates the intended users without unexpectedly deleting cloud identities. This is directly observable validation of the Cloud Identity directory synchronization result.
E:Configure Google Cloud Directory Sync with scoped mapping rules and validate dry-run changes. This is the intended action for Cloud Identity directory synchronization.
Incorrect Answers
B:Use supported Cloud Identity Groups APIs with narrowly scoped permissions and review group change logs. This serves the different Programmatic group membership governance objective, not the selected Cloud Identity directory synchronization plan. Directory synchronization maps authoritative identity sources into managed cloud accounts rather than granting IAM roles itself.
C:Treat a successful SAML login as proof all directory users and groups have been synchronized. This is not part of a safe or effective Cloud Identity directory synchronization design. Broad unreviewed deletion rules can disable legitimate cloud users during synchronization.
D:Configure Workforce Identity Federation pools, identity provider mappings and least-privilege IAM bindings. This serves the different Workforce Identity Federation for external workers objective, not the selected Cloud Identity directory synchronization plan. Directory synchronization maps authoritative identity sources into managed cloud accounts rather than granting IAM roles itself.