Google Professional Cloud Architect Practice Test 97
Question 960
At Medical lab network, the shared filesystem for containers workload has a documented risk: lab containers need concurrent POSIX file writes but the team selected object-storage semantics. The review found that test suite fails on file-lock operations and atomic renames. The architecture must also ensure that laboratory collaboration requires managed NFS semantics in one region. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Select Filestore for shared file workloads consumed by GKE pods
- Run concurrent file-lock and rename tests under a pod restart
- Monitor NFS saturation, share capacity and backup success
- Treat Cloud Storage object writes as POSIX byte-range locking
Explanation
Correct Answer
C:
Monitor NFS saturation, share capacity and backup success reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (lab containers need concurrent POSIX file writes but the team selected object-storage semantics) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Select Filestore for shared file workloads consumed by GKE pods” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, test suite fails on file-lock operations and atomic renames. The option “Monitor NFS saturation, share capacity and backup success” instead addresses the requested ongoing operational assurance.
B:
The alternative “Run concurrent file-lock and rename tests under a pod restart” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, test suite fails on file-lock operations and atomic renames. The option “Monitor NFS saturation, share capacity and backup success” instead addresses the requested ongoing operational assurance.
D:
Object storage does not provide identical filesystem locking semantics. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that laboratory collaboration requires managed NFS semantics in one region.
Question 961
The cloud cost allocation environment at National airline alliance faces this issue: shared services costs are split evenly despite wildly different flight-planning workloads. Supporting evidence shows that billing export shows one subsidiary generates most BigQuery queries. The architect must preserve the requirement that chargeback must be auditable without exposing confidential route plans. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?
- Introduce budgets and labels before internal invoicing changes
- Use BigQuery billing exports, project labels and agreed unit economics
- Assign every unit identical cost regardless of actual use
- Define tags, shared-cost rules and stakeholder-approved allocation units
Explanation
Correct Answer
D:
Define tags, shared-cost rules and stakeholder-approved allocation units is the appropriate diagnostic because the observation—billing export shows one subsidiary generates most BigQuery queries—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (shared services costs are split evenly despite wildly different flight-planning workloads) before the design is approved.
Incorrect Answers
A:
The alternative “Introduce budgets and labels before internal invoicing changes” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, billing export shows one subsidiary generates most BigQuery queries. The option “Define tags, shared-cost rules and stakeholder-approved allocation units” instead addresses the requested root-cause evidence.
B:
The alternative “Use BigQuery billing exports, project labels and agreed unit economics” is target architecture selection; it does not establish why the observed path failed. In the reported observation, billing export shows one subsidiary generates most BigQuery queries. The option “Define tags, shared-cost rules and stakeholder-approved allocation units” instead addresses the requested root-cause evidence.
C:
An arbitrary equal split misstates usage and incentives. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that chargeback must be auditable without exposing confidential route plans.
Question 962
Case study: Healthcare billing analytics: log-based incident metrics
Healthcare billing analytics relies on log-based incident metrics to deliver its operational commitments. The current architectural problem is that an API error log is present but there is no alert on rising failed invoice reconciliation. The team has recorded this evidence: log query shows 15% payment finalization errors during partner outage. Any proposed response must preserve the requirement that financial integrity requires detection before end-of-day settlement.
Consider Healthcare billing analytics and its log-based incident metrics workload. The issue is that an API error log is present but there is no alert on rising failed invoice reconciliation; the current observation is that log query shows 15% payment finalization errors during partner outage. The team must ensure that financial integrity requires detection before end-of-day settlement. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Introduce the metric and alert route with synthetic nonfinancial test events
- Only send a weekly email digest for critical reconciliation failures
- Identify a reliable error signature, baseline and affected invoice identifiers
- Emit representative failure logs and verify actionable alert delivery
Explanation
Correct Answer
D:
Emit representative failure logs and verify actionable alert delivery is a direct acceptance test of the path implicated by log query shows 15% payment finalization errors during partner outage. It checks that the original risk (an API error log is present but there is no alert on rising failed invoice reconciliation) has actually been controlled and tests that permitted operations still meet the requirement that financial integrity requires detection before end-of-day settlement.
Incorrect Answers
A:
The alternative “Introduce the metric and alert route with synthetic nonfinancial test events” documents change execution but not its operational acceptance result. In the reported observation, log query shows 15% payment finalization errors during partner outage. The option “Emit representative failure logs and verify actionable alert delivery” instead addresses the requested acceptance verification.
B:
A weekly summary misses urgent financial incidents. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that financial integrity requires detection before end-of-day settlement.
C:
The alternative “Identify a reliable error signature, baseline and affected invoice identifiers” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, log query shows 15% payment finalization errors during partner outage. The option “Emit representative failure logs and verify actionable alert delivery” instead addresses the requested acceptance verification.
Question 963
Case study: Healthcare diagnostics startup: private clinical AI roadmap
Healthcare diagnostics startup relies on private clinical AI roadmap to deliver its operational commitments. The current architectural problem is that new model versions require retraining with patient data but existing architecture exposes raw records to developers. The team has recorded this evidence: governance review finds manual exports from a protected clinical warehouse. Any proposed response must preserve the requirement that clinical data processing must remain consent-bound and auditable.
Consider Healthcare diagnostics startup and its private clinical AI roadmap workload. The issue is that new model versions require retraining with patient data but existing architecture exposes raw records to developers; the current observation is that governance review finds manual exports from a protected clinical warehouse. The team must ensure that clinical data processing must remain consent-bound and auditable. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Map future model use cases, consent, access and lifecycle expectations
- Give all model developers project Owner to speed experimentation
- Design reusable governed feature access and isolated training/serving identities
- Pilot a new model using approved deidentified datasets and audit trails
- Track model lineage, training grants and policy change requests
Explanation
Correct Answers
C:
Design reusable governed feature access and isolated training/serving identities targets the underlying issue (new model versions require retraining with patient data but existing architecture exposes raw records to developers) rather than merely reporting symptoms. It also preserves the required outcome (clinical data processing must remain consent-bound and auditable), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
D:
Pilot a new model using approved deidentified datasets and audit trails is a controlled means to introduce the approved architecture while meeting the requirement that clinical data processing must remain consent-bound and auditable. 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
A:
This diagnoses the original issue (new model versions require retraining with patient data but existing architecture exposes raw records to developers), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
B:
Broad project ownership bypasses patient-data isolation. The shortcut does not supply the requested design and safe rollout for private clinical AI roadmap, where governance review finds manual exports from a protected clinical warehouse.
E:
Monitoring private clinical AI roadmap for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: new model versions require retraining with patient data but existing architecture exposes raw records to developers.
Question 964
The VMware-based customer management environment at Local telecom provider faces this issue: team wants to migrate hundreds of VMware virtual machines with almost no application changes. Supporting evidence shows that migration inventory shows tight network coupling and unsupported guest customization. The architect must preserve the requirement that a contract requires a one-year low-risk transitional hosting period. Which migration or rollout step best manages risk, dependencies and reversibility?
- Review transitional cost and per-app refactor/decommission roadmap
- Consider Google Cloud VMware Engine for compatible transitional virtualization
- Delete the existing hypervisor configurations before verifying guest compatibility
- Pilot a VM cohort with private connectivity and validated operational ownership
Explanation
Correct Answer
D:
Pilot a VM cohort with private connectivity and validated operational ownership is a controlled means to introduce the approved architecture while meeting the requirement that a contract requires a one-year low-risk transitional hosting period. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Review transitional cost and per-app refactor/decommission roadmap” addresses later monitoring rather than the actual controlled deployment. In the reported observation, migration inventory shows tight network coupling and unsupported guest customization. The option “Pilot a VM cohort with private connectivity and validated operational ownership” instead addresses the requested controlled implementation.
B:
The alternative “Consider Google Cloud VMware Engine for compatible transitional virtualization” describes the chosen design, but not how it is introduced safely. In the reported observation, migration inventory shows tight network coupling and unsupported guest customization. The option “Pilot a VM cohort with private connectivity and validated operational ownership” instead addresses the requested controlled implementation.
C:
Unplanned transformation creates unacceptable migration risk. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that a contract requires a one-year low-risk transitional hosting period.
Question 965
The claims analytics modernization environment at National property insurer faces this issue: finance compared storage prices without accounting for nightly claims integration and legal holds. Supporting evidence shows that workload inventory shows a batch export consumed by three regulators and an external actuary. The architect must preserve the requirement that actuarial outputs must be delivered by 06:00 every business day. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Define decoupled ingestion, governed analytical storage and a bounded overnight processing objective
- Monitor missed ingestion deadlines, unclassified data and projected storage spend
- Copy all claim tables into public object buckets for analysts
- Compare daily source-to-target aggregates and check that required reports arrive before 06:00
Explanation
Correct Answer
B:
Monitor missed ingestion deadlines, unclassified data and projected storage spend reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (finance compared storage prices without accounting for nightly claims integration and legal holds) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Define decoupled ingestion, governed analytical storage and a bounded overnight processing objective” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, workload inventory shows a batch export consumed by three regulators and an external actuary. The option “Monitor missed ingestion deadlines, unclassified data and projected storage spend” instead addresses the requested ongoing operational assurance.
C:
Public storage would violate claims confidentiality and regulated access. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that actuarial outputs must be delivered by 06:00 every business day.
D:
The alternative “Compare daily source-to-target aggregates and check that required reports arrive before 06:00” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, workload inventory shows a batch export consumed by three regulators and an external actuary. The option “Monitor missed ingestion deadlines, unclassified data and projected storage spend” instead addresses the requested ongoing operational assurance.
Question 966
At University research network, the Google Cloud design for GKE deployment safety is affected because a new GPU workload is rolled onto the only node while existing experiment pods have no disruption budget. A review found that pilot update evicts every running inference pod. The proposed response must account for the requirement that research service must remain available during cluster upgrades. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Set replicas to one and skip readiness probes to accelerate upgrades
- Design safe rollout using health probes and PodDisruptionBudget where appropriate
- Inventory replicas, node affinity and rescheduling constraints
- Roll out node-pool updates incrementally with fallback capacity
- Watch pod evictions, deployment stalls and degraded GPU availability
Explanation
Correct Answers
B:
Design safe rollout using health probes and PodDisruptionBudget where appropriate targets the underlying issue (a new GPU workload is rolled onto the only node while existing experiment pods have no disruption budget) rather than merely reporting symptoms. It also preserves the required outcome (research service must remain available during cluster upgrades), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
D:
Roll out node-pool updates incrementally with fallback capacity is a controlled means to introduce the approved architecture while meeting the requirement that research service must remain available during cluster upgrades. 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
A:
Unprotected singleton workloads are unavailable on node drain. The shortcut does not supply the requested design and safe rollout for GKE deployment safety, where pilot update evicts every running inference pod.
C:
This diagnoses the original issue (a new GPU workload is rolled onto the only node while existing experiment pods have no disruption budget), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
E:
Monitoring GKE deployment safety for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: a new GPU workload is rolled onto the only node while existing experiment pods have no disruption budget.
Question 967
The feature KPI design environment at Online grocery delivery faces this issue: migration success is defined as number of VMs shut down while delivery failures increase. Supporting evidence shows that business dashboards show missed deliveries after new routing service launch. The architect must preserve the requirement that the program must improve delivered-order reliability, not just infrastructure count. Go-live and initial tests passed. Which ongoing measure is most useful to catch control drift or regression?
- Track on-time rate, order cancellations and unit economics
- Compare deliveries before and after rollout under matched demand
- Define shared availability, on-time-delivery and cost-per-delivery KPIs
- Call the project successful solely because the cloud invoice fell
Explanation
Correct Answer
A:
Track on-time rate, order cancellations and unit economics reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (migration success is defined as number of VMs shut down while delivery failures increase) rather than treating the first successful test as permanent assurance.
Incorrect Answers
B:
The alternative “Compare deliveries before and after rollout under matched demand” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, business dashboards show missed deliveries after new routing service launch. The option “Track on-time rate, order cancellations and unit economics” instead addresses the requested ongoing operational assurance.
C:
The alternative “Define shared availability, on-time-delivery and cost-per-delivery KPIs” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, business dashboards show missed deliveries after new routing service launch. The option “Track on-time rate, order cancellations and unit economics” instead addresses the requested ongoing operational assurance.
D:
Lower spend can accompany worse business performance. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that the program must improve delivered-order reliability, not just infrastructure count.
Question 968
At International health insurer, the Google Cloud design for Cloud Build release flow is affected because a deployment pipeline places unreviewed images into production after every commit. A review found that release logs show no artifact promotion or security scan before a production deploy. The proposed response must account for the requirement that production releases require signed approval and a reversible rollout. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Map build triggers, artifact hashes, approval owners and deployment paths
- Allow every developer to deploy from a mutable local image tag
- Stage signed artifact promotion with progressive traffic rollout
- Attempt promotion of an unsigned build and verify it is rejected
Explanation
Correct Answer
D:
Attempt promotion of an unsigned build and verify it is rejected is a direct acceptance test of the path implicated by release logs show no artifact promotion or security scan before a production deploy. It checks that the original risk (a deployment pipeline places unreviewed images into production after every commit) has actually been controlled and tests that permitted operations still meet the requirement that production releases require signed approval and a reversible rollout.
Incorrect Answers
A:
The alternative “Map build triggers, artifact hashes, approval owners and deployment paths” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, release logs show no artifact promotion or security scan before a production deploy. The option “Attempt promotion of an unsigned build and verify it is rejected” instead addresses the requested acceptance verification.
B:
Mutable unreviewed releases cannot provide attributable production control. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that production releases require signed approval and a reversible rollout.
C:
The alternative “Stage signed artifact promotion with progressive traffic rollout” documents change execution but not its operational acceptance result. In the reported observation, release logs show no artifact promotion or security scan before a production deploy. The option “Attempt promotion of an unsigned build and verify it is rejected” instead addresses the requested acceptance verification.
Question 969
At Genomics research institute, the petabyte cold archive migration workload has a documented risk: network upload estimates exceed the contract closeout window. The review found that measurements show 2PB archive behind a limited 200Mbps link. The architecture must also ensure that research files require checksums and access controls throughout transfer. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Verify file hash samples and complete object counts after import
- Send 2PB over the unmeasured WAN and assume it finishes before the deadline
- Monitor missing manifests, access grants and physical custody exceptions
- Plan an offline transfer appliance workflow with verified staging and encrypted custody
Explanation
Correct Answer
C:
Monitor missing manifests, access grants and physical custody exceptions reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (network upload estimates exceed the contract closeout window) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Verify file hash samples and complete object counts after import” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, measurements show 2PB archive behind a limited 200Mbps link. The option “Monitor missing manifests, access grants and physical custody exceptions” instead addresses the requested ongoing operational assurance.
B:
The available link cannot deliver the required volume within the stated window. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that research files require checksums and access controls throughout transfer.
D:
The alternative “Plan an offline transfer appliance workflow with verified staging and encrypted custody” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, measurements show 2PB archive behind a limited 200Mbps link. The option “Monitor missing manifests, access grants and physical custody exceptions” instead addresses the requested ongoing operational assurance.
Question 970
Case study: Medical device logistics vendor: Windows application portfolio
Medical device logistics vendor relies on Windows application portfolio to deliver its operational commitments. The current architectural problem is that a vendor application requires proprietary Windows integration and cannot be modified until 2028. The team has recorded this evidence: application inventory confirms hard-coded Windows service dependency and vendor support conditions. Any proposed response must preserve the requirement that device dispatch must maintain support entitlement and tested restoration.
The Windows application portfolio environment at Medical device logistics vendor faces this issue: a vendor application requires proprietary Windows integration and cannot be modified until 2028. Supporting evidence shows that application inventory confirms hard-coded Windows service dependency and vendor support conditions. The architect must preserve the requirement that device dispatch must maintain support entitlement and tested restoration. What test must pass before the business accepts the remediated architecture?
- Convert the unsupported proprietary service directly to Cloud Run with no rewrite
- Create reproducible images and migrate one warehouse environment with rollback
- Run vendor certification tests and warehouse dispatch transactions on restored instances
- Assess OS, licensing, database and vendor certification constraints
Explanation
Correct Answer
C:
Run vendor certification tests and warehouse dispatch transactions on restored instances is a direct acceptance test of the path implicated by application inventory confirms hard-coded Windows service dependency and vendor support conditions. It checks that the original risk (a vendor application requires proprietary Windows integration and cannot be modified until 2028) has actually been controlled and tests that permitted operations still meet the requirement that device dispatch must maintain support entitlement and tested restoration.
Incorrect Answers
A:
A Windows-service binary does not become a stateless Linux container automatically. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that device dispatch must maintain support entitlement and tested restoration.
B:
The alternative “Create reproducible images and migrate one warehouse environment with rollback” documents change execution but not its operational acceptance result. In the reported observation, application inventory confirms hard-coded Windows service dependency and vendor support conditions. The option “Run vendor certification tests and warehouse dispatch transactions on restored instances” instead addresses the requested acceptance verification.
D:
The alternative “Assess OS, licensing, database and vendor certification constraints” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, application inventory confirms hard-coded Windows service dependency and vendor support conditions. The option “Run vendor certification tests and warehouse dispatch transactions on restored instances” instead addresses the requested acceptance verification.