Google Professional Cloud Security Engineer Practice Test 48
Question 470
A Cloud Run service needs a payment token that is periodically rotated. If the relevant Secret Manager versioning and least privilege safeguard is omitted, which outcome is the MOST directly associated failure?
- No audit trail makes prompt injection or misuse difficult to reconstruct.
- A project IAM grant alone does not necessarily authorize arbitrary SQL queries on every database.
- Shared plaintext tokens in source repositories remain exposed after workload deployment.
- Publishing tokenization keys alongside datasets can permit re-identification.
Explanation
Correct Answer
C:Shared plaintext tokens in source repositories remain exposed after workload deployment. Secrets are governed objects with IAM and version lifecycle; runtime variables alone are not a secret vault. The corrective approach is to verify secret-access audit events, version disablement and consumer refresh.
Incorrect Answers
A:No audit trail makes prompt injection or misuse difficult to reconstruct. This failure pattern belongs chiefly to AI model monitoring and abuse investigations; it is not the failure most directly tested in the Secret Manager versioning and least privilege situation. Shared plaintext tokens in source repositories remain exposed after workload deployment.
B:This failure pattern belongs chiefly to Cloud SQL private IP and database authentication; it is not the failure most directly tested in the Secret Manager versioning and least privilege situation.
D:Publishing tokenization keys alongside datasets can permit re-identification. This failure pattern belongs chiefly to Sensitive Data Protection deterministic de-identification; it is not the failure most directly tested in the Secret Manager versioning and least privilege situation. Shared plaintext tokens in source repositories remain exposed after workload deployment.
Question 471
Risk owners need findings to close only after the underlying policy is corrected. Which practical correction or implementation decision is MOST directly appropriate?
- Test retention policy on sample logs and document privileged change approvals.
- Verify configuration after remediation and compare detection timestamp and status.
- Test synthetic traffic and validate sampling implications and log analysis filters.
- Rename a finding resolved and assume allUsers lost access to its Cloud Storage bucket.
Explanation
Correct Answer
B:Verify configuration after remediation and compare detection timestamp and status. The intended behavior can be checked because the resource passes a subsequent posture assessment and the finding reflects updated state.
Incorrect Answers
A:Test retention policy on sample logs and document privileged change approvals. This could help Log bucket retention and immutable audit evidence, but it does not resolve the Security Health Analytics remediation workflow case. Posture findings describe detected conditions and do not equal an enforcement or repair action.
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 Security Health Analytics remediation workflow case. Posture findings describe detected conditions and do not equal an enforcement or repair action.
D:Rename a finding resolved and assume allUsers lost access to its Cloud Storage bucket. This would not correct the Security Health Analytics remediation workflow workflow. Marking a finding reviewed without fixing the source resource leaves the exposure.
Question 472
A key designer must select protection level without confusing it with application-level encryption scope. Select TWO statements that correctly combine the Cloud HSM versus software-protected keys method with evidence or its governing principle.
- Distinguish Google-managed default at-rest encryption from services configured with supported CMEK.
- Crypto operations use the intended hardware protection and service integration remains compatible.
- Select a supported Cloud HSM protection level for the relevant Cloud KMS key.
- Put hardware-backed in the key description and assume that changes a software key into an HSM key.
- Configure supported TLS trust-chain validation and modern transport security settings on each relevant hop.
Explanation
Correct Answers
B:Crypto operations use the intended hardware protection and service integration remains compatible. This is directly observable validation of the Cloud HSM versus software-protected keys result.
C:Select a supported Cloud HSM protection level for the relevant Cloud KMS key. This is the intended action for Cloud HSM versus software-protected keys.
Incorrect Answers
A:Distinguish Google-managed default at-rest encryption from services configured with supported CMEK. This serves the different Default at-rest encryption versus CMEK objective, not the selected Cloud HSM versus software-protected keys plan. HSM-backed KMS keys provide a different protection level than software-protected keys.
D:Put hardware-backed in the key description and assume that changes a software key into an HSM key. This is not part of a safe or effective Cloud HSM versus software-protected keys design. Claiming every generic software key meets a hardware custody mandate can fail review.
E:Configure supported TLS trust-chain validation and modern transport security settings on each relevant hop. This serves the different TLS certificate trust and cipher policy objective, not the selected Cloud HSM versus software-protected keys plan. HSM-backed KMS keys provide a different protection level than software-protected keys.
Question 473
A service in a private VPC times out contacting a Google managed API despite having correct IAM. After the recommended Private connectivity choice and API access troubleshooting change is implemented, which observation MOST directly verifies that it works?
- On-premises clients can reach supported APIs through the intended private Google connectivity path.
- Packet flow, DNS, routes and IAM checks confirm the chosen method reaches exactly the target service.
- DNS lookup and API traffic use the restricted VIP while unsupported services are handled intentionally.
- Tests show the caller has both sufficient resource permissions and a permitted perimeter path.
Explanation
Correct Answer
B:Packet flow, DNS, routes and IAM checks confirm the chosen method reaches exactly the target service. This directly tests whether the Private connectivity choice and API access troubleshooting goal was met. Private connectivity mechanisms solve different routing and service exposure problems and are not interchangeable.
Incorrect Answers
A:On-premises clients can reach supported APIs through the intended private Google connectivity path. This is evidence about Private Google Access for on-premises, not direct proof of the required Private connectivity choice and API access troubleshooting behavior. The relevant check is that packet flow, DNS, routes and IAM checks confirm the chosen method reaches exactly the target service.
C:DNS lookup and API traffic use the restricted VIP while unsupported services are handled intentionally. This is evidence about Restricted Google APIs VIP for perimeters, not direct proof of the required Private connectivity choice and API access troubleshooting behavior. The relevant check is that packet flow, DNS, routes and IAM checks confirm the chosen method reaches exactly the target service.
D:Tests show the caller has both sufficient resource permissions and a permitted perimeter path. This is evidence about VPC Service Controls versus IAM authorization, not direct proof of the required Private connectivity choice and API access troubleshooting behavior. The relevant check is that packet flow, DNS, routes and IAM checks confirm the chosen method reaches exactly the target service.
Question 474
Application developers can deploy services but must not disable centralized audit logs. After the recommended IAM separation of security duties change is implemented, which observation MOST directly verifies that it works?
- Operators can execute approved tasks but cannot grant themselves unrelated security-admin privileges.
- Unauthorized API calls stop and explicitly approved dependent workloads are migrated or remediated.
- The prohibited operation is denied despite applicable allow bindings and legitimate exceptions remain functional.
- The intended task succeeds without granting administrative privileges to unrelated projects.
Explanation
Correct Answer
A:Operators can execute approved tasks but cannot grant themselves unrelated security-admin privileges. This directly tests whether the IAM separation of security duties goal was met. Separation of duties limits privilege escalation and tampering with oversight controls.
Incorrect Answers
B:Unauthorized API calls stop and explicitly approved dependent workloads are migrated or remediated. This is evidence about Service account disabling and dependency mapping, not direct proof of the required IAM separation of security duties behavior. The relevant check is that operators can execute approved tasks but cannot grant themselves unrelated security-admin privileges.
C:The prohibited operation is denied despite applicable allow bindings and legitimate exceptions remain functional. This is evidence about IAM Deny policy enforcement, not direct proof of the required IAM separation of security duties behavior. The relevant check is that operators can execute approved tasks but cannot grant themselves unrelated security-admin privileges.
D:The intended task succeeds without granting administrative privileges to unrelated projects. This is evidence about IAM least-privilege role scoping, not direct proof of the required IAM separation of security duties behavior. The relevant check is that operators can execute approved tasks but cannot grant themselves unrelated security-admin privileges.
Question 475
A procurement team selects a managed service and assumes its certifications cover the company's custom application controls. If the relevant Vendor shared-control contract and service eligibility safeguard is omitted, which outcome is the MOST directly associated failure?
- Saving only a final green dashboard screenshot may miss earlier violations.
- Ignoring legacy ACL consumers may break clients during migration.
- Assuming a vendor certificate transfers regulatory responsibility to the customer workload may produce audit gaps.
- A shared open network can pull unrelated workloads into the regulated assessment scope.
Explanation
Correct Answer
C:Assuming a vendor certificate transfers regulatory responsibility to the customer workload may produce audit gaps. Provider attestations cover specified services and periods, not every customer configuration or integration. The corrective approach is to verify service inclusion, reporting period and customer responsibilities in supporting documents.
Incorrect Answers
A:This failure pattern belongs chiefly to Audit evidence collection and attestation; it is not the failure most directly tested in the Vendor shared-control contract and service eligibility situation.
B:This failure pattern belongs chiefly to Cloud Storage uniform bucket-level permissions; it is not the failure most directly tested in the Vendor shared-control contract and service eligibility situation.
D:This failure pattern belongs chiefly to PCI workload network segmentation; it is not the failure most directly tested in the Vendor shared-control contract and service eligibility situation.
Question 476
A private GKE node requests Google API access through internal network egress. Which practical correction or implementation decision is MOST directly appropriate?
- Test tunnel failure and BGP route convergence without assuming a single active path is enough.
- Assign a public IP to every VM simply to let it query Cloud Storage.
- Test API hostname resolution and reachability from a VM with no external IP.
- Test service compatibility, DNS resolution and required API methods from protected clients.
Explanation
Correct Answer
C:Test API hostname resolution and reachability from a VM with no external IP. The intended behavior can be checked because private workloads can reach supported Google APIs without an assigned external IP.
Incorrect Answers
A:Test tunnel failure and BGP route convergence without assuming a single active path is enough. This could help HA VPN encrypted hybrid tunnels, but it does not resolve the Private Google Access for internal VMs case. Private Google Access supports API reachability for suitable private-resource networking contexts.
B:Assign a public IP to every VM simply to let it query Cloud Storage. This would not correct the Private Google Access for internal VMs workflow. Assuming Cloud NAT is mandatory for every Google API access pattern can add needless public egress.
D:Test service compatibility, DNS resolution and required API methods from protected clients. This could help Restricted Google APIs VIP for perimeters, but it does not resolve the Private Google Access for internal VMs case. Private Google Access supports API reachability for suitable private-resource networking contexts.
Question 477
A customer needs producer approval before a consumer endpoint connects to a shared service. Select TWO statements that correctly combine the Private Service Connect service attachment publishing method with evidence or its governing principle.
- Approved consumer endpoints connect privately while unauthorized projects cannot create effective connections.
- Treat PSC service attachment creation as a license to route every subnet in the provider VPC.
- Publish a supported PSC service attachment with consumer acceptance policy and internal load balancer.
- Design Private Google Access for on-premises hosts with approved routes and private or restricted VIP DNS.
- Configure HA VPN with redundant interfaces and Cloud Router BGP sessions across supported gateways.
Explanation
Correct Answers
A:Approved consumer endpoints connect privately while unauthorized projects cannot create effective connections. This is directly observable validation of the Private Service Connect service attachment publishing result.
C:Publish a supported PSC service attachment with consumer acceptance policy and internal load balancer. This is the intended action for Private Service Connect service attachment publishing.
Incorrect Answers
B:Treat PSC service attachment creation as a license to route every subnet in the provider VPC. This is not part of a safe or effective Private Service Connect service attachment publishing design. An all-consumer publish policy may expose internal service connectivity beyond the contract.
D:Design Private Google Access for on-premises hosts with approved routes and private or restricted VIP DNS. This serves the different Private Google Access for on-premises objective, not the selected Private Service Connect service attachment publishing plan. PSC service attachments expose specific producer services rather than transitive access to the entire VPC.
E:Configure HA VPN with redundant interfaces and Cloud Router BGP sessions across supported gateways. This serves the different HA VPN encrypted hybrid tunnels objective, not the selected Private Service Connect service attachment publishing plan. PSC service attachments expose specific producer services rather than transitive access to the entire VPC.
Question 478
A temporary vendor should read a project only until the contract expiration date. Which approach BEST meets the requirement while respecting the system constraints?
- Put an expiration timestamp in a user's display name and assume IAM enforces it.
- Use supported IAM Conditions expressions with the correct resource and time attributes.
- Evaluate IAM Recommender and Policy Intelligence findings against actual workload use and required operations.
- Bind a suitable predefined or reviewed custom IAM role at the narrowest supported scope.
Explanation
Correct Answer
B:Use supported IAM Conditions expressions with the correct resource and time attributes. IAM Conditions refine allow bindings with evaluated contextual attributes rather than granting permanent unconditional access. Verification should demonstrate that access succeeds while condition is true and fails after expiry or outside the supported resource scope.
Incorrect Answers
A:Put an expiration timestamp in a user's display name and assume IAM enforces it. This is an unsafe or ineffective shortcut for Conditional IAM access restrictions. A malformed condition or unsupported attribute may broaden or unexpectedly block access.
C:Evaluate IAM Recommender and Policy Intelligence findings against actual workload use and required operations. This primarily addresses Policy Intelligence permission recommendations, not the specific Conditional IAM access restrictions decision. Here, iAM Conditions refine allow bindings with evaluated contextual attributes rather than granting permanent unconditional access.
D:Bind a suitable predefined or reviewed custom IAM role at the narrowest supported scope. This primarily addresses IAM least-privilege role scoping, not the specific Conditional IAM access restrictions decision. Here, iAM Conditions refine allow bindings with evaluated contextual attributes rather than granting permanent unconditional access.
Question 479
A team needs to check whether a batch membership update accidentally granted cloud access to external users. An engineer must explain the recommendation for Programmatic group membership governance. Which underlying principle is the MOST accurate?
- Managing authorization through groups can simplify changes but group administration itself is privileged.
- Super administrators have organization-wide identity privileges that require heightened protection and auditing.
- Directory synchronization maps authoritative identity sources into managed cloud accounts rather than granting IAM roles itself.
- Group-based IAM reduces binding sprawl but relies on trustworthy group membership governance.
Explanation
Correct Answer
A:Managing authorization through groups can simplify changes but group administration itself is privileged. Therefore the implementation decision is to use supported Cloud Identity Groups APIs with narrowly scoped permissions and review group change logs.
Incorrect Answers
B:Super administrators have organization-wide identity privileges that require heightened protection and auditing. This describes the separate Super administrator emergency access mechanism; the present case instead requires Programmatic group membership governance. Unverified group automation may silently grant inherited IAM roles to unintended principals.
C:Directory synchronization maps authoritative identity sources into managed cloud accounts rather than granting IAM roles itself. This describes the separate Cloud Identity directory synchronization mechanism; the present case instead requires Programmatic group membership governance. Unverified group automation may silently grant inherited IAM roles to unintended principals.
D:Group-based IAM reduces binding sprawl but relies on trustworthy group membership governance. This describes the separate Group-based IAM authorization mechanism; the present case instead requires Programmatic group membership governance. Unverified group automation may silently grant inherited IAM roles to unintended principals.
Question 480
Security needs to identify which principal read sensitive Cloud Storage objects. If the relevant Data Access Audit Logs enablement and cost safeguard is omitted, which outcome is the MOST directly associated failure?
- Marking a finding reviewed without fixing the source resource leaves the exposure.
- A log sink lacking destination write permission can silently fail central collection.
- Attaching broad roles to a common node identity magnifies container escape impact.
- Assuming all service data reads are logged by default may leave incident evidence gaps.
Explanation
Correct Answer
D:Assuming all service data reads are logged by default may leave incident evidence gaps. Data Access logs have different availability and configuration behavior from Admin Activity logs. The corrective approach is to test logging coverage for chosen services and handle high-volume sink budgeting.
Incorrect Answers
A:This failure pattern belongs chiefly to Security Health Analytics remediation workflow; it is not the failure most directly tested in the Data Access Audit Logs enablement and cost situation.
B:This failure pattern belongs chiefly to Organization aggregated log sink; it is not the failure most directly tested in the Data Access Audit Logs enablement and cost situation.
C:This failure pattern belongs chiefly to GKE Workload Identity for deployment runtime; it is not the failure most directly tested in the Data Access Audit Logs enablement and cost situation.