Google Professional Cloud Architect Practice Test 26
Question 250
At Community farming platform, the gcloud project configuration workload has a documented risk: engineers repeatedly use their personal projects when running deployment scripts. The review found that shell history shows wrong active project and accidental unrelated resource creation. The architecture must also ensure that deployments must target designated staging projects only. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Run deployment automation in isolated configuration environments
- Inspect gcloud configuration, account identity and project context
- Assume whatever project is active in Cloud Shell is always staging
- Use explicit project arguments, scoped identities and scripted preflight checks
Explanation
Correct Answer
B:
Inspect gcloud configuration, account identity and project context is the appropriate diagnostic because the observation—shell history shows wrong active project and accidental unrelated resource creation—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (engineers repeatedly use their personal projects when running deployment scripts) before the design is approved.
Incorrect Answers
A:
The alternative “Run deployment automation in isolated configuration environments” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, shell history shows wrong active project and accidental unrelated resource creation. The option “Inspect gcloud configuration, account identity and project context” instead addresses the requested root-cause evidence.
C:
Ambient CLI context can target the wrong project. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that deployments must target designated staging projects only.
D:
The alternative “Use explicit project arguments, scoped identities and scripted preflight checks” is target architecture selection; it does not establish why the observed path failed. In the reported observation, shell history shows wrong active project and accidental unrelated resource creation. The option “Inspect gcloud configuration, account identity and project context” instead addresses the requested root-cause evidence.
Question 251
Consider Regional trucking marketplace and its custom business metrics workload. The issue is that application metrics show 200 responses even as delivery confirmations are silently dropped; the current observation is that business reconciliation finds missing delivery events despite healthy pods. The team must ensure that the service must confirm each accepted shipment within five minutes. The team has completed discovery. Which preventive or corrective architecture is most appropriate?
- Publish business delivery-success metrics and SLOs with trace correlation
- Compare infrastructure telemetry with event-level customer outcome metrics
- Use only VM CPU to measure whether shipments were delivered
- Track unconfirmed shipments and processing delay by customer cohort
Explanation
Correct Answer
A:
Publish business delivery-success metrics and SLOs with trace correlation targets the underlying issue (application metrics show 200 responses even as delivery confirmations are silently dropped) rather than merely reporting symptoms. It also preserves the required outcome (the service must confirm each accepted shipment within five minutes), which a target-state design must satisfy.
Incorrect Answers
B:
The alternative “Compare infrastructure telemetry with event-level customer outcome metrics” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, business reconciliation finds missing delivery events despite healthy pods. The option “Publish business delivery-success metrics and SLOs with trace correlation” instead addresses the requested architecture selection.
C:
Healthy CPU is not evidence of successful business transactions. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that the service must confirm each accepted shipment within five minutes.
D:
The alternative “Track unconfirmed shipments and processing delay by customer cohort” measures results without defining the preventive design now required. In the reported observation, business reconciliation finds missing delivery events despite healthy pods. The option “Publish business delivery-success metrics and SLOs with trace correlation” instead addresses the requested architecture selection.
Question 252
Municipal tax office plans to update database migration testing. Investigators found that comparison shows several tax invoices differ by one cent after import, consistent with the reported problem that an automated migration passes row counts even though currency fields lose decimal precision. The response must satisfy the requirement that legal tax computations require exact financial arithmetic. The security and reliability teams dispute the root cause. Which evidence-gathering action is justified now?
- Accept equal row count as proof that amounts are unchanged
- Define deterministic money-type mappings and financial invariant tests
- Inspect source column types, transformation rules and reconciliation coverage
- Apply migration fixes to a representative historical subset first
Explanation
Correct Answer
C:
Inspect source column types, transformation rules and reconciliation coverage is the appropriate diagnostic because the observation—comparison shows several tax invoices differ by one cent after import—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (an automated migration passes row counts even though currency fields lose decimal precision) before the design is approved.
Incorrect Answers
A:
Row totals cannot detect corrupted financial values. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that legal tax computations require exact financial arithmetic.
B:
The alternative “Define deterministic money-type mappings and financial invariant tests” is target architecture selection; it does not establish why the observed path failed. In the reported observation, comparison shows several tax invoices differ by one cent after import. The option “Inspect source column types, transformation rules and reconciliation coverage” instead addresses the requested root-cause evidence.
D:
The alternative “Apply migration fixes to a representative historical subset first” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, comparison shows several tax invoices differ by one cent after import. The option “Inspect source column types, transformation rules and reconciliation coverage” instead addresses the requested root-cause evidence.
Question 253
The Terraform landing zone rollout environment at Community public library faces this issue: new projects require approved security settings but Terraform changes are applied directly from laptops. Supporting evidence shows that audit finds mutable local state and unreviewed IAM grants. The architect must preserve the requirement that public catalog availability must not be interrupted by infrastructure drift. Which migration or rollout step best manages risk, dependencies and reversibility?
- Use remote protected Terraform state and policy-controlled plans
- Apply reviewed Terraform changes by staged projects with rollback
- Give all engineers full project Owner for local Terraform apply
- Monitor manual drift and denied policy changes
Explanation
Correct Answer
B:
Apply reviewed Terraform changes by staged projects with rollback is a controlled means to introduce the approved architecture while meeting the requirement that public catalog availability must not be interrupted by infrastructure drift. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Use remote protected Terraform state and policy-controlled plans” describes the chosen design, but not how it is introduced safely. In the reported observation, audit finds mutable local state and unreviewed IAM grants. The option “Apply reviewed Terraform changes by staged projects with rollback” instead addresses the requested controlled implementation.
C:
Unreviewed broad changes negate controlled infrastructure rollout. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that public catalog availability must not be interrupted by infrastructure drift.
D:
The alternative “Monitor manual drift and denied policy changes” addresses later monitoring rather than the actual controlled deployment. In the reported observation, audit finds mutable local state and unreviewed IAM grants. The option “Apply reviewed Terraform changes by staged projects with rollback” instead addresses the requested controlled implementation.
Question 254
Case study: State licensing agency: multi-vendor service ownership
State licensing agency relies on multi-vendor service ownership to deliver its operational commitments. The current architectural problem is that two suppliers both claim the other owns an expired security certificate. The team has recorded this evidence: contract maps have no accountable production certificate owner. Any proposed response must preserve the requirement that public licensing cannot lose authentication on renewal day.
The multi-vendor service ownership environment at State licensing agency faces this issue: two suppliers both claim the other owns an expired security certificate. Supporting evidence shows that contract maps have no accountable production certificate owner. The architect must preserve the requirement that public licensing cannot lose authentication on renewal day. What test must pass before the business accepts the remediated architecture?
- Wait for whichever supplier notices expiry first
- Rehearse certificate rollover with both suppliers and verify successful login
- Map contractual RACI, certificate dependencies and escalation paths
- Introduce shared change calendar and renewal notifications
Explanation
Correct Answer
B:
Rehearse certificate rollover with both suppliers and verify successful login is a direct acceptance test of the path implicated by contract maps have no accountable production certificate owner. It checks that the original risk (two suppliers both claim the other owns an expired security certificate) has actually been controlled and tests that permitted operations still meet the requirement that public licensing cannot lose authentication on renewal day.
Incorrect Answers
A:
Unassigned renewal responsibility causes preventable outages. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that public licensing cannot lose authentication on renewal day.
C:
The alternative “Map contractual RACI, certificate dependencies and escalation paths” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, contract maps have no accountable production certificate owner. The option “Rehearse certificate rollover with both suppliers and verify successful login” instead addresses the requested acceptance verification.
D:
The alternative “Introduce shared change calendar and renewal notifications” documents change execution but not its operational acceptance result. In the reported observation, contract maps have no accountable production certificate owner. The option “Rehearse certificate rollover with both suppliers and verify successful login” instead addresses the requested acceptance verification.
Question 255
Case study: Financial records archive: legacy batch identity
Financial records archive relies on legacy batch identity to deliver its operational commitments. The current architectural problem is that migration plan provisions new service accounts without mapping on-prem scheduled-job permissions. The team has recorded this evidence: audit reveals a shared service password embedded in payroll scripts. Any proposed response must preserve the requirement that regulatory evidence must retain actor attribution after migration.
Consider Financial records archive and its legacy batch identity workload. The issue is that migration plan provisions new service accounts without mapping on-prem scheduled-job permissions; the current observation is that audit reveals a shared service password embedded in payroll scripts. The team must ensure that regulatory evidence must retain actor attribution after migration. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Use separate workload identities and short-lived credentials with compatible batch roles
- Move scheduled tasks one at a time while invalidating shared passwords safely
- Copy shared plaintext service passwords into cloud VM metadata
- Inventory job identities, secrets, execution ownership and privileged file access
Explanation
Correct Answer
D:
Inventory job identities, secrets, execution ownership and privileged file access is the appropriate diagnostic because the observation—audit reveals a shared service password embedded in payroll scripts—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (migration plan provisions new service accounts without mapping on-prem scheduled-job permissions) before the design is approved.
Incorrect Answers
A:
The alternative “Use separate workload identities and short-lived credentials with compatible batch roles” is target architecture selection; it does not establish why the observed path failed. In the reported observation, audit reveals a shared service password embedded in payroll scripts. The option “Inventory job identities, secrets, execution ownership and privileged file access” instead addresses the requested root-cause evidence.
B:
The alternative “Move scheduled tasks one at a time while invalidating shared passwords safely” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, audit reveals a shared service password embedded in payroll scripts. The option “Inventory job identities, secrets, execution ownership and privileged file access” instead addresses the requested root-cause evidence.
C:
Replicating shared secrets sustains the original identity risk. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that regulatory evidence must retain actor attribution after migration.
Question 256
At International renewable grid data service, the penetration-test remediation workload has a documented risk: last penetration test found an IDOR flaw but the team marked it fixed after updating documentation. The review found that retest finds cross-tenant API access still possible with valid token. The architecture must also ensure that commercial clients require strict account isolation. The architecture review is paused until the team can prove the real failure path. Which investigation should happen first?
- Identify authorization enforcement path and test dataset boundaries
- Close the security finding based only on a signed policy memo
- Use object-level auth enforcement with independent negative-case tests
- Deploy fixes under tenant-scoped canary and revoke vulnerable paths
Explanation
Correct Answer
A:
Identify authorization enforcement path and test dataset boundaries is the appropriate diagnostic because the observation—retest finds cross-tenant API access still possible with valid token—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (last penetration test found an IDOR flaw but the team marked it fixed after updating documentation) before the design is approved.
Incorrect Answers
B:
Documentation cannot replace verified access-control enforcement. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that commercial clients require strict account isolation.
C:
The alternative “Use object-level auth enforcement with independent negative-case tests” is target architecture selection; it does not establish why the observed path failed. In the reported observation, retest finds cross-tenant API access still possible with valid token. The option “Identify authorization enforcement path and test dataset boundaries” instead addresses the requested root-cause evidence.
D:
The alternative “Deploy fixes under tenant-scoped canary and revoke vulnerable paths” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, retest finds cross-tenant API access still possible with valid token. The option “Identify authorization enforcement path and test dataset boundaries” instead addresses the requested root-cause evidence.
Question 257
At Legal discovery cooperative, the regulated document holds workload has a documented risk: a scheduled lifecycle deletion overlaps a court-ordered legal hold. The review found that records show retention rules expire before litigation review completes. The architecture must also ensure that legal-hold protected files must not be removed by application writers. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Attempt test deletion with ordinary application credentials and confirm refusal
- Grant all document uploaders permission to release legal holds
- Review hold expirations, privileged overrides and lifecycle audit
- Apply object holds and retention configurations that respect verified legal orders
Explanation
Correct Answer
C:
Review hold expirations, privileged overrides and lifecycle audit reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (a scheduled lifecycle deletion overlaps a court-ordered legal hold) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Attempt test deletion with ordinary application credentials and confirm refusal” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, records show retention rules expire before litigation review completes. The option “Review hold expirations, privileged overrides and lifecycle audit” instead addresses the requested ongoing operational assurance.
B:
Uncontrolled release rights defeat binding preservation orders. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that legal-hold protected files must not be removed by application writers.
D:
The alternative “Apply object holds and retention configurations that respect verified legal orders” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, records show retention rules expire before litigation review completes. The option “Review hold expirations, privileged overrides and lifecycle audit” instead addresses the requested ongoing operational assurance.
Question 258
Consider Pharmaceutical research organization and its stakeholder release approvals workload. The issue is that engineering can launch clinical analytics while privacy and quality officers discover changes afterward; the current observation is that change journal shows data exports activated without regulatory signoff. The team must ensure that regulated data usage requires separate business and privacy approval. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Design accountable change review with documented privacy/quality checkpoints
- Introduce approval gates in delivery workflow with emergency exception routing
- Track overdue approvals and unauthorized exceptional changes
- Let the fastest engineering manager approve all regulatory exceptions alone
- Map decision rights, release gates and required stakeholder evidence
Explanation
Correct Answers
A:
Design accountable change review with documented privacy/quality checkpoints targets the underlying issue (engineering can launch clinical analytics while privacy and quality officers discover changes afterward) rather than merely reporting symptoms. It also preserves the required outcome (regulated data usage requires separate business and privacy approval), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
B:
Introduce approval gates in delivery workflow with emergency exception routing is a controlled means to introduce the approved architecture while meeting the requirement that regulated data usage requires separate business and privacy approval. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption. This supplies the controlled-introduction half of the two-action package.
Incorrect Answers
C:
Monitoring stakeholder release approvals for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: engineering can launch clinical analytics while privacy and quality officers discover changes afterward.
D:
Independent controls require the designated privacy/quality owners. The shortcut does not supply the requested design and safe rollout for stakeholder release approvals, where change journal shows data exports activated without regulatory signoff.
E:
This diagnoses the original issue (engineering can launch clinical analytics while privacy and quality officers discover changes afterward), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
Question 259
The penetration-test remediation environment at International renewable grid data service faces this issue: last penetration test found an IDOR flaw but the team marked it fixed after updating documentation. Supporting evidence shows that retest finds cross-tenant API access still possible with valid token. The architect must preserve the requirement that commercial clients require strict account isolation. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Close the security finding based only on a signed policy memo
- Identify authorization enforcement path and test dataset boundaries
- Monitor new unauthorized access attempts and API route drift
- Deploy fixes under tenant-scoped canary and revoke vulnerable paths
- Use object-level auth enforcement with independent negative-case tests
Explanation
Correct Answers
D:
Deploy fixes under tenant-scoped canary and revoke vulnerable paths is a controlled means to introduce the approved architecture while meeting the requirement that commercial clients require strict account isolation. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption. This supplies the controlled-introduction half of the two-action package.
E:
Use object-level auth enforcement with independent negative-case tests targets the underlying issue (last penetration test found an IDOR flaw but the team marked it fixed after updating documentation) rather than merely reporting symptoms. It also preserves the required outcome (commercial clients require strict account isolation), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
A:
Documentation cannot replace verified access-control enforcement. The shortcut does not supply the requested design and safe rollout for penetration-test remediation, where retest finds cross-tenant API access still possible with valid token.
B:
This diagnoses the original issue (last penetration test found an IDOR flaw but the team marked it fixed after updating documentation), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
C:
Monitoring penetration-test remediation for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: last penetration test found an IDOR flaw but the team marked it fixed after updating documentation.
Question 260
At National vehicle licensing agency, the Google Cloud design for data import service release is affected because migration scripts run with project Owner and can modify unrelated vehicle records. A review found that access audit shows scripts touch datasets outside the approved batch. The proposed response must account for the requirement that license imports must be scoped and reversible. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Execute imports using short-lived credentials in staged verified batches
- Keep project Owner permissions because the migration is temporary
- Map intended data reads/writes, identity and rollback data snapshots
- Reconcile allowed changes and attempt denied access to unrelated datasets
Explanation
Correct Answer
D:
Reconcile allowed changes and attempt denied access to unrelated datasets is a direct acceptance test of the path implicated by access audit shows scripts touch datasets outside the approved batch. It checks that the original risk (migration scripts run with project Owner and can modify unrelated vehicle records) has actually been controlled and tests that permitted operations still meet the requirement that license imports must be scoped and reversible.
Incorrect Answers
A:
The alternative “Execute imports using short-lived credentials in staged verified batches” documents change execution but not its operational acceptance result. In the reported observation, access audit shows scripts touch datasets outside the approved batch. The option “Reconcile allowed changes and attempt denied access to unrelated datasets” instead addresses the requested acceptance verification.
B:
Temporary unbounded access remains a major compromise path. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that license imports must be scoped and reversible.
C:
The alternative “Map intended data reads/writes, identity and rollback data snapshots” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, access audit shows scripts touch datasets outside the approved batch. The option “Reconcile allowed changes and attempt denied access to unrelated datasets” instead addresses the requested acceptance verification.