Google Professional Cloud Architect Practice Test 33
Question 320
At Multinational auto-insurer, the third-party risk boundary workload has a documented risk: a data processor claims SOC 2 coverage for a separate custom mobile collection app. The review found that contract review shows its audit excludes the in-app analytics SDK. The architecture must also ensure that customer consent and app data handling require independent assessment. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Map coverage of supplier attestations versus app and SDK control ownership
- Roll out SDK controls under contractual and app store change review
- Monitor third-party scope changes and mobile data egress
- Define separate privacy and security controls for the unassessed mobile collection path
- Treat the processor's SOC 2 report as certification of every unrelated mobile SDK
Explanation
Correct Answers
B:
Roll out SDK controls under contractual and app store change review is a controlled means to introduce the approved architecture while meeting the requirement that customer consent and app data handling require independent assessment. 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.
D:
Define separate privacy and security controls for the unassessed mobile collection path targets the underlying issue (a data processor claims SOC 2 coverage for a separate custom mobile collection app) rather than merely reporting symptoms. It also preserves the required outcome (customer consent and app data handling require independent assessment), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
Incorrect Answers
A:
This diagnoses the original issue (a data processor claims SOC 2 coverage for a separate custom mobile collection app), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
C:
Monitoring third-party risk boundary for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: a data processor claims SOC 2 coverage for a separate custom mobile collection app.
E:
Attestation scope cannot be extended to unexamined components. The shortcut does not supply the requested design and safe rollout for third-party risk boundary, where contract review shows its audit excludes the in-app analytics SDK.
Question 321
The patchable application instances environment at Telecom billing department faces this issue: operators manually patch live VMs and drift from the declared golden configuration. Supporting evidence shows that audit finds two instances missing a required base image update. The architect must preserve the requirement that customers must not lose billing access during security patch cycles. Which migration or rollout step best manages risk, dependencies and reversibility?
- SSH into all production servers simultaneously and update without rollback
- Deploy template versions in health-gated batches across zones
- Adopt immutable image templates with rolling managed-instance replacements
- Track patch-level drift and failed rolling update cohorts
Explanation
Correct Answer
B:
Deploy template versions in health-gated batches across zones is a controlled means to introduce the approved architecture while meeting the requirement that customers must not lose billing access during security patch cycles. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Uncoordinated in-place patching creates inconsistent state and outage risk. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that customers must not lose billing access during security patch cycles.
C:
The alternative “Adopt immutable image templates with rolling managed-instance replacements” describes the chosen design, but not how it is introduced safely. In the reported observation, audit finds two instances missing a required base image update. The option “Deploy template versions in health-gated batches across zones” instead addresses the requested controlled implementation.
D:
The alternative “Track patch-level drift and failed rolling update cohorts” addresses later monitoring rather than the actual controlled deployment. In the reported observation, audit finds two instances missing a required base image update. The option “Deploy template versions in health-gated batches across zones” instead addresses the requested controlled implementation.
Question 322
The SCADA historian migration environment at Metropolitan power utility faces this issue: historian collectors send proprietary UDP and engineers propose direct internet exposure. Supporting evidence shows that packet survey shows embedded devices without TLS or authentication. The architect must preserve the requirement that plant control networks must remain isolated from public ingress. Which migration or rollout step best manages risk, dependencies and reversibility?
- Give cloud VMs public routes into the SCADA control VLAN
- Track DMZ policy deviations and telemetry gaps
- Pilot one substation with read-only replicated data and authenticated broker
- Design a controlled telemetry bridge through an industrial DMZ to cloud storage
Explanation
Correct Answer
C:
Pilot one substation with read-only replicated data and authenticated broker is a controlled means to introduce the approved architecture while meeting the requirement that plant control networks must remain isolated from public ingress. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
Direct internet access violates industrial segmentation. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that plant control networks must remain isolated from public ingress.
B:
The alternative “Track DMZ policy deviations and telemetry gaps” addresses later monitoring rather than the actual controlled deployment. In the reported observation, packet survey shows embedded devices without TLS or authentication. The option “Pilot one substation with read-only replicated data and authenticated broker” instead addresses the requested controlled implementation.
D:
The alternative “Design a controlled telemetry bridge through an industrial DMZ to cloud storage” describes the chosen design, but not how it is introduced safely. In the reported observation, packet survey shows embedded devices without TLS or authentication. The option “Pilot one substation with read-only replicated data and authenticated broker” instead addresses the requested controlled implementation.
Question 323
The connected vehicle insight platform environment at Global fleet analytics company faces this issue: management expects ten times more telemetry after a merger but the platform allocates fixed partitions. Supporting evidence shows that forecast shows devices and event attributes will expand across regions. The architect must preserve the requirement that existing fleet alerts cannot lose events during schema evolution. Before approving a solution, which analysis most directly clarifies the underlying dependency or control gap?
- Roll out schema evolution with dual parsers and backward-compatible records
- Project growth by region and event class with migration milestones
- Design partitioned event contracts and independently scalable analytical consumers
- Change all event schemas simultaneously without versioning
Explanation
Correct Answer
B:
Project growth by region and event class with migration milestones is the appropriate diagnostic because the observation—forecast shows devices and event attributes will expand across regions—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (management expects ten times more telemetry after a merger but the platform allocates fixed partitions) before the design is approved.
Incorrect Answers
A:
The alternative “Roll out schema evolution with dual parsers and backward-compatible records” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, forecast shows devices and event attributes will expand across regions. The option “Project growth by region and event class with migration milestones” instead addresses the requested root-cause evidence.
C:
The alternative “Design partitioned event contracts and independently scalable analytical consumers” is target architecture selection; it does not establish why the observed path failed. In the reported observation, forecast shows devices and event attributes will expand across regions. The option “Project growth by region and event class with migration milestones” instead addresses the requested root-cause evidence.
D:
A schema cutover without compatibility can strand existing devices. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that existing fleet alerts cannot lose events during schema evolution.
Question 324
The support escalation maturity environment at Regional postal delivery firm faces this issue: a production outage remains open because no team owns the supporting vendor service. Supporting evidence shows that ticket history shows repeated bounced ownership assignments. The architect must preserve the requirement that delivery confirmations must have a clear customer-facing support path. Which migration or rollout step best manages risk, dependencies and reversibility?
- Define agreed service ownership and escalation SLAs with vendor contracts
- Introduce unified incident routing with current on-call contact tests
- Close incidents whenever they cross an organizational boundary
- Monitor handoff loops and support response times
Explanation
Correct Answer
B:
Introduce unified incident routing with current on-call contact tests is a controlled means to introduce the approved architecture while meeting the requirement that delivery confirmations must have a clear customer-facing support path. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Define agreed service ownership and escalation SLAs with vendor contracts” describes the chosen design, but not how it is introduced safely. In the reported observation, ticket history shows repeated bounced ownership assignments. The option “Introduce unified incident routing with current on-call contact tests” instead addresses the requested controlled implementation.
C:
No owner does not imply the service problem is resolved. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that delivery confirmations must have a clear customer-facing support path.
D:
The alternative “Monitor handoff loops and support response times” addresses later monitoring rather than the actual controlled deployment. In the reported observation, ticket history shows repeated bounced ownership assignments. The option “Introduce unified incident routing with current on-call contact tests” instead addresses the requested controlled implementation.
Question 325
At National retailer, the SOC 2 assurance evidence workload has a documented risk: cloud service roles change without retaining approval artifacts for audit. The review found that internal audit finds no linkage between IAM grants and access requests. The architecture must also ensure that auditor must reconstruct who authorized production privileges. What follow-up metric or alert will identify emerging failures after the initial acceptance test?
- Sample privileged grant changes and trace each to a valid approved request
- Design traceable access approval, just-in-time privileges and immutable change records
- Track orphan grants, missing approvals and retained evidence coverage
- Treat an informal verbal confirmation as complete access audit evidence
Explanation
Correct Answer
C:
Track orphan grants, missing approvals and retained evidence coverage reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (cloud service roles change without retaining approval artifacts for audit) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
The alternative “Sample privileged grant changes and trace each to a valid approved request” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, internal audit finds no linkage between IAM grants and access requests. The option “Track orphan grants, missing approvals and retained evidence coverage” instead addresses the requested ongoing operational assurance.
B:
The alternative “Design traceable access approval, just-in-time privileges and immutable change records” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, internal audit finds no linkage between IAM grants and access requests. The option “Track orphan grants, missing approvals and retained evidence coverage” instead addresses the requested ongoing operational assurance.
D:
Unrecorded approvals cannot support reproducible assurance. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that auditor must reconstruct who authorized production privileges.
Question 326
Case study: Regional farmers market network: mobile checkout modernization
Regional farmers market network relies on mobile checkout modernization to deliver its operational commitments. The current architectural problem is that the business case assumes continuous cellular service across remote event sites. The team has recorded this evidence: store surveys show multi-hour connectivity gaps at harvest festivals. Any proposed response must preserve the requirement that offline payments must reconcile without accepting unlimited duplicate orders.
Consider Regional farmers market network and its mobile checkout modernization workload. The issue is that the business case assumes continuous cellular service across remote event sites; the current observation is that store surveys show multi-hour connectivity gaps at harvest festivals. The team must ensure that offline payments must reconcile without accepting unlimited duplicate orders. The change committee needs to understand the current system rather than install a fix yet. What should it do?
- Define offline order tokens with bounded spend, duplicate prevention and asynchronous reconciliation
- Let every device approve unlimited offline charges without identity checks
- Enumerate offline duration, refund operations, device trust and reconciliation owners
- Pilot one market with controlled offline ledgers and an explicit failback process
Explanation
Correct Answer
C:
Enumerate offline duration, refund operations, device trust and reconciliation owners is the appropriate diagnostic because the observation—store surveys show multi-hour connectivity gaps at harvest festivals—does not by itself establish every dependency, authorization rule or failure boundary. The findings explain the reported risk (the business case assumes continuous cellular service across remote event sites) before the design is approved.
Incorrect Answers
A:
The alternative “Define offline order tokens with bounded spend, duplicate prevention and asynchronous reconciliation” is target architecture selection; it does not establish why the observed path failed. In the reported observation, store surveys show multi-hour connectivity gaps at harvest festivals. The option “Enumerate offline duration, refund operations, device trust and reconciliation owners” instead addresses the requested root-cause evidence.
B:
Unlimited offline approvals create unbounded fraud and reconciliation exposure. For this question, it is not a defensible choice for root-cause evidence and it does not satisfy the requirement that offline payments must reconcile without accepting unlimited duplicate orders.
D:
The alternative “Pilot one market with controlled offline ledgers and an explicit failback process” is rollout work that may modify the wrong dependency before root-cause evidence is collected. In the reported observation, store surveys show multi-hour connectivity gaps at harvest festivals. The option “Enumerate offline duration, refund operations, device trust and reconciliation owners” instead addresses the requested root-cause evidence.
Question 327
Digital archive service plans to update object version recovery. Investigators found that restore exercise shows no retained noncurrent version after replication, consistent with the reported problem that a script deleted storage objects and replication copied the deletions to the only backup. The response must satisfy the requirement that a contractual RPO requires recovery from mistaken deletes for 45 days. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Set lifecycle to delete every previous generation immediately
- Enable retention after validating governance authority and object lifecycle effects
- Delete test objects as an app writer and restore prior protected versions
- Trace versioning, retention, replication and administrator delete permissions
Explanation
Correct Answer
C:
Delete test objects as an app writer and restore prior protected versions is a direct acceptance test of the path implicated by restore exercise shows no retained noncurrent version after replication. It checks that the original risk (a script deleted storage objects and replication copied the deletions to the only backup) has actually been controlled and tests that permitted operations still meet the requirement that a contractual RPO requires recovery from mistaken deletes for 45 days.
Incorrect Answers
A:
Immediate deletion removes the very recovery history required. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that a contractual RPO requires recovery from mistaken deletes for 45 days.
B:
The alternative “Enable retention after validating governance authority and object lifecycle effects” documents change execution but not its operational acceptance result. In the reported observation, restore exercise shows no retained noncurrent version after replication. The option “Delete test objects as an app writer and restore prior protected versions” instead addresses the requested acceptance verification.
D:
The alternative “Trace versioning, retention, replication and administrator delete permissions” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, restore exercise shows no retained noncurrent version after replication. The option “Delete test objects as an app writer and restore prior protected versions” instead addresses the requested acceptance verification.
Question 328
Emergency medical scheduling startup plans to update feature-flag rollback. Investigators found that pilot notes show accepted bookings are reallocated unexpectedly, consistent with the reported problem that a risky appointment algorithm is released to all users before its impacts can be measured. The response must satisfy the requirement that existing appointments must remain stable during launch. Which target-state design is best justified by the evidence and required business outcome?
- Identify affected cohorts, irreversible side effects and flag state dependencies
- Modify all stored appointments irreversibly when enabling the feature
- Use controlled feature flags with experiment guards and durable booking invariants
- Watch cohort-specific booking errors and rollback latency
Explanation
Correct Answer
C:
Use controlled feature flags with experiment guards and durable booking invariants targets the underlying issue (a risky appointment algorithm is released to all users before its impacts can be measured) rather than merely reporting symptoms. It also preserves the required outcome (existing appointments must remain stable during launch), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Identify affected cohorts, irreversible side effects and flag state dependencies” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, pilot notes show accepted bookings are reallocated unexpectedly. The option “Use controlled feature flags with experiment guards and durable booking invariants” instead addresses the requested architecture selection.
B:
Feature flags cannot undo unprotected database side effects. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that existing appointments must remain stable during launch.
D:
The alternative “Watch cohort-specific booking errors and rollback latency” measures results without defining the preventive design now required. In the reported observation, pilot notes show accepted bookings are reallocated unexpectedly. The option “Use controlled feature flags with experiment guards and durable booking invariants” instead addresses the requested architecture selection.
Question 329
At AI satellite imagery group, the short-lived GPU inference workload has a documented risk: the product team leaves GPU instances running overnight for occasional image classification. The review found that billing shows high GPU idle cost with short bursts of queued requests. The architecture must also ensure that inference can tolerate several seconds of cold-start delay. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Monitor idle GPU spend, request latency and quota exhaustion
- Reserve the largest GPU fleet permanently for infrequent requests
- Canary burst routing with model artifact caching and capped quotas
- Choose a scale-aware inference platform with workload-appropriate GPUs and queueing
Explanation
Correct Answer
C:
Canary burst routing with model artifact caching and capped quotas is a controlled means to introduce the approved architecture while meeting the requirement that inference can tolerate several seconds of cold-start delay. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Monitor idle GPU spend, request latency and quota exhaustion” addresses later monitoring rather than the actual controlled deployment. In the reported observation, billing shows high GPU idle cost with short bursts of queued requests. The option “Canary burst routing with model artifact caching and capped quotas” instead addresses the requested controlled implementation.
B:
Always-on capacity wastes cost when demand is highly intermittent. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that inference can tolerate several seconds of cold-start delay.
D:
The alternative “Choose a scale-aware inference platform with workload-appropriate GPUs and queueing” describes the chosen design, but not how it is introduced safely. In the reported observation, billing shows high GPU idle cost with short bursts of queued requests. The option “Canary burst routing with model artifact caching and capped quotas” instead addresses the requested controlled implementation.
Question 330
E-commerce promotion service plans to update Cloud Run database connection storms. Investigators found that database logs show connection refusals at promotion launch, consistent with the reported problem that a serverless revision scales quickly and exhausts a legacy SQL server's connection pool. The response must satisfy the requirement that backend must remain within database concurrency limits. The design review is over and production introduction is next. Which action is the best fit?
- Stage maximum-instance limits and traffic splitting before peak events
- Allow unlimited cold-start instances to open independent large pools
- Set Cloud Run concurrency and instance limits with appropriate pooling
- Track rejected requests, instance count and DB pool utilization
Explanation
Correct Answer
A:
Stage maximum-instance limits and traffic splitting before peak events is a controlled means to introduce the approved architecture while meeting the requirement that backend must remain within database concurrency limits. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
Unbounded scaling overwhelms a fixed database dependency. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that backend must remain within database concurrency limits.
C:
The alternative “Set Cloud Run concurrency and instance limits with appropriate pooling” describes the chosen design, but not how it is introduced safely. In the reported observation, database logs show connection refusals at promotion launch. The option “Stage maximum-instance limits and traffic splitting before peak events” instead addresses the requested controlled implementation.
D:
The alternative “Track rejected requests, instance count and DB pool utilization” addresses later monitoring rather than the actual controlled deployment. In the reported observation, database logs show connection refusals at promotion launch. The option “Stage maximum-instance limits and traffic splitting before peak events” instead addresses the requested controlled implementation.