Google Professional Cloud Architect Practice Test 67
Question 660
Mobile banking wallet plans to update payments rollback coordination. Investigators found that release plan contains no financial reconciliation procedure, consistent with the reported problem that CI tool can roll back app pods but cannot reverse a one-way database ledger migration. The response must satisfy the requirement that posted transactions cannot be duplicated or silently lost. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Map irreversible state updates and rollback versus forward-fix choices
- Test dual-version database support before deploying new billing code
- Treat a code rollback as automatically reversing every committed financial transaction
- Fail deployment mid-cutover and verify ledger consistency after recovery
Explanation
Correct Answer
D:
Fail deployment mid-cutover and verify ledger consistency after recovery is a direct acceptance test of the path implicated by release plan contains no financial reconciliation procedure. It checks that the original risk (CI tool can roll back app pods but cannot reverse a one-way database ledger migration) has actually been controlled and tests that permitted operations still meet the requirement that posted transactions cannot be duplicated or silently lost.
Incorrect Answers
A:
The alternative “Map irreversible state updates and rollback versus forward-fix choices” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, release plan contains no financial reconciliation procedure. The option “Fail deployment mid-cutover and verify ledger consistency after recovery” instead addresses the requested acceptance verification.
B:
The alternative “Test dual-version database support before deploying new billing code” documents change execution but not its operational acceptance result. In the reported observation, release plan contains no financial reconciliation procedure. The option “Fail deployment mid-cutover and verify ledger consistency after recovery” instead addresses the requested acceptance verification.
C:
Financial state changes need explicit reconciliation, not just application rollback. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that posted transactions cannot be duplicated or silently lost.
Question 661
Consider Public health research hub and its private SaaS producer endpoint workload. The issue is that consumer projects connect over public load balancers despite producer and consumers residing in Google Cloud; the current observation is that traceroute confirms data traverses a public endpoint with IP-based allowlists. The team must ensure that approved projects require internal-only access and separate VPC ownership. Which acceptance test should demonstrate both protection against the failure and continued authorized service?
- Grant approved consumer endpoint access and update internal DNS in phases
- Enable public access with a broad CIDR allowlist and call it private
- Check unauthorized projects have no endpoint route and valid consumers reach service
- Map service producer/consumer boundaries and traffic direction
Explanation
Correct Answer
C:
Check unauthorized projects have no endpoint route and valid consumers reach service is a direct acceptance test of the path implicated by traceroute confirms data traverses a public endpoint with IP-based allowlists. It checks that the original risk (consumer projects connect over public load balancers despite producer and consumers residing in Google Cloud) has actually been controlled and tests that permitted operations still meet the requirement that approved projects require internal-only access and separate VPC ownership.
Incorrect Answers
A:
The alternative “Grant approved consumer endpoint access and update internal DNS in phases” documents change execution but not its operational acceptance result. In the reported observation, traceroute confirms data traverses a public endpoint with IP-based allowlists. The option “Check unauthorized projects have no endpoint route and valid consumers reach service” instead addresses the requested acceptance verification.
B:
Public routing and wide CIDR access do not meet a private-service boundary. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that approved projects require internal-only access and separate VPC ownership.
D:
The alternative “Map service producer/consumer boundaries and traffic direction” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, traceroute confirms data traverses a public endpoint with IP-based allowlists. The option “Check unauthorized projects have no endpoint route and valid consumers reach service” instead addresses the requested acceptance verification.
Question 662
International insurance portal plans to update automated rollback thresholds. Investigators found that service dashboard shows 6% failure during a 20% canary, consistent with the reported problem that new revision doubles checkout error rate but rollout continues because logs are not tied to release gates. The response must satisfy the requirement that customer billing changes must be reversible without inconsistent transactions. The approved change has been applied. Which validation provides the clearest evidence the original problem is fixed?
- Inject a failing canary and verify traffic reverts before broad exposure
- Treat release success as the number of pods that became Ready
- Deploy gradual traffic with automated abort thresholds
- Establish baseline error budgets, canary signals and rollback authority
Explanation
Correct Answer
A:
Inject a failing canary and verify traffic reverts before broad exposure is a direct acceptance test of the path implicated by service dashboard shows 6% failure during a 20% canary. It checks that the original risk (new revision doubles checkout error rate but rollout continues because logs are not tied to release gates) has actually been controlled and tests that permitted operations still meet the requirement that customer billing changes must be reversible without inconsistent transactions.
Incorrect Answers
B:
Readiness alone does not demonstrate correct customer transactions. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that customer billing changes must be reversible without inconsistent transactions.
C:
The alternative “Deploy gradual traffic with automated abort thresholds” documents change execution but not its operational acceptance result. In the reported observation, service dashboard shows 6% failure during a 20% canary. The option “Inject a failing canary and verify traffic reverts before broad exposure” instead addresses the requested acceptance verification.
D:
The alternative “Establish baseline error budgets, canary signals and rollback authority” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, service dashboard shows 6% failure during a 20% canary. The option “Inject a failing canary and verify traffic reverts before broad exposure” instead addresses the requested acceptance verification.
Question 663
Case study: Financial audit platform: service emulator tests
Financial audit platform relies on service emulator tests to deliver its operational commitments. The current architectural problem is that developers run payment integration tests against live transaction services. The team has recorded this evidence: test logs show real transfer identifiers generated by a local developer build. Any proposed response must preserve the requirement that testing must not create external settlement transfers.
The service emulator tests environment at Financial audit platform faces this issue: developers run payment integration tests against live transaction services. Supporting evidence shows that test logs show real transfer identifiers generated by a local developer build. The architect must preserve the requirement that testing must not create external settlement transfers. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Run all tests using the production billing administrator identity
- Identify external API calls, test credentials and shared environment settings
- Track accidental production endpoint use and test credential expiry
- Use a service emulator or isolated test project with synthetic data for integration checks
Explanation
Correct Answer
D:
Use a service emulator or isolated test project with synthetic data for integration checks targets the underlying issue (developers run payment integration tests against live transaction services) rather than merely reporting symptoms. It also preserves the required outcome (testing must not create external settlement transfers), which a target-state design must satisfy.
Incorrect Answers
A:
Production credentials make test runs capable of unintended transfers. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that testing must not create external settlement transfers.
B:
The alternative “Identify external API calls, test credentials and shared environment settings” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, test logs show real transfer identifiers generated by a local developer build. The option “Use a service emulator or isolated test project with synthetic data for integration checks” instead addresses the requested architecture selection.
C:
The alternative “Track accidental production endpoint use and test credential expiry” measures results without defining the preventive design now required. In the reported observation, test logs show real transfer identifiers generated by a local developer build. The option “Use a service emulator or isolated test project with synthetic data for integration checks” instead addresses the requested architecture selection.
Question 664
At Insurance photo assessor, the Google Cloud design for damaged vehicle classification is affected because claims teams seek automated detection of damaged panels from uploaded images. A review found that validation examples show visual categories differ from text-only customer descriptions. The proposed response must account for the requirement that model outputs are advisory and claims decisions need human review. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Apply only sentiment analysis of the customer's filename
- Monitor low-confidence rates, model changes and reviewer overrides
- Use a suitable vision-capable model or API with calibrated confidence and human escalation
- Measure precision and recall per damage class on withheld claim images
Explanation
Correct Answer
B:
Monitor low-confidence rates, model changes and reviewer overrides reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (claims teams seek automated detection of damaged panels from uploaded images) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Filename sentiment cannot identify visual damage. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that model outputs are advisory and claims decisions need human review.
C:
The alternative “Use a suitable vision-capable model or API with calibrated confidence and human escalation” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, validation examples show visual categories differ from text-only customer descriptions. The option “Monitor low-confidence rates, model changes and reviewer overrides” instead addresses the requested ongoing operational assurance.
D:
The alternative “Measure precision and recall per damage class on withheld claim images” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, validation examples show visual categories differ from text-only customer descriptions. The option “Monitor low-confidence rates, model changes and reviewer overrides” instead addresses the requested ongoing operational assurance.
Question 665
Case study: Financial audit platform: service emulator tests
Financial audit platform relies on service emulator tests to deliver its operational commitments. The current architectural problem is that developers run payment integration tests against live transaction services. The team has recorded this evidence: test logs show real transfer identifiers generated by a local developer build. Any proposed response must preserve the requirement that testing must not create external settlement transfers.
At Financial audit platform, the Google Cloud design for service emulator tests is affected because developers run payment integration tests against live transaction services. A review found that test logs show real transfer identifiers generated by a local developer build. The proposed response must account for the requirement that testing must not create external settlement transfers. The solution is operating. Which evidence should be watched for longer-term reliability and compliance?
- Run all tests using the production billing administrator identity
- Track accidental production endpoint use and test credential expiry
- Use a service emulator or isolated test project with synthetic data for integration checks
- Run full test suite and confirm no live financial side effects
Explanation
Correct Answer
B:
Track accidental production endpoint use and test credential expiry reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (developers run payment integration tests against live transaction services) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Production credentials make test runs capable of unintended transfers. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that testing must not create external settlement transfers.
C:
The alternative “Use a service emulator or isolated test project with synthetic data for integration checks” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, test logs show real transfer identifiers generated by a local developer build. The option “Track accidental production endpoint use and test credential expiry” instead addresses the requested ongoing operational assurance.
D:
The alternative “Run full test suite and confirm no live financial side effects” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, test logs show real transfer identifiers generated by a local developer build. The option “Track accidental production endpoint use and test credential expiry” instead addresses the requested ongoing operational assurance.
Question 666
International fashion retailer plans to update customer loyalty relaunch. Investigators found that transaction dashboards show flash-sale load rises twelvefold for fifteen minutes, consistent with the reported problem that a vendor proposal minimizes compute cost while ignoring peak checkout conversion. The response must satisfy the requirement that checkout must keep the payment processor independent of loyalty analytics. Which target-state design is best justified by the evidence and required business outcome?
- Model conversion loss, flash-sale load profiles and payment dependencies
- Separate checkout from asynchronous loyalty scoring with elastic stateless APIs
- Synchronous-call the loyalty model before charging every order
- Monitor checkout latency, dropped loyalty events and scaling cost per order
Explanation
Correct Answer
B:
Separate checkout from asynchronous loyalty scoring with elastic stateless APIs targets the underlying issue (a vendor proposal minimizes compute cost while ignoring peak checkout conversion) rather than merely reporting symptoms. It also preserves the required outcome (checkout must keep the payment processor independent of loyalty analytics), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Model conversion loss, flash-sale load profiles and payment dependencies” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, transaction dashboards show flash-sale load rises twelvefold for fifteen minutes. The option “Separate checkout from asynchronous loyalty scoring with elastic stateless APIs” instead addresses the requested architecture selection.
C:
Making payment dependent on optional scoring magnifies latency and outages. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that checkout must keep the payment processor independent of loyalty analytics.
D:
The alternative “Monitor checkout latency, dropped loyalty events and scaling cost per order” measures results without defining the preventive design now required. In the reported observation, transaction dashboards show flash-sale load rises twelvefold for fifteen minutes. The option “Separate checkout from asynchronous loyalty scoring with elastic stateless APIs” instead addresses the requested architecture selection.
Question 667
At Online grocery delivery, the feature KPI design workload has a documented risk: migration success is defined as number of VMs shut down while delivery failures increase. The review found that business dashboards show missed deliveries after new routing service launch. The architecture must also ensure that the program must improve delivered-order reliability, not just infrastructure count. Which post-change test most reliably distinguishes a functioning control from a merely successful installation?
- Call the project successful solely because the cloud invoice fell
- Compare deliveries before and after rollout under matched demand
- Introduce metrics dashboards with business owners and stable baselines
- Reconcile technical metrics with customer outcomes and fulfillment costs
Explanation
Correct Answer
B:
Compare deliveries before and after rollout under matched demand is a direct acceptance test of the path implicated by business dashboards show missed deliveries after new routing service launch. It checks that the original risk (migration success is defined as number of VMs shut down while delivery failures increase) has actually been controlled and tests that permitted operations still meet the requirement that the program must improve delivered-order reliability, not just infrastructure count.
Incorrect Answers
A:
Lower spend can accompany worse business performance. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that the program must improve delivered-order reliability, not just infrastructure count.
C:
The alternative “Introduce metrics dashboards with business owners and stable baselines” documents change execution but not its operational acceptance result. In the reported observation, business dashboards show missed deliveries after new routing service launch. The option “Compare deliveries before and after rollout under matched demand” instead addresses the requested acceptance verification.
D:
The alternative “Reconcile technical metrics with customer outcomes and fulfillment costs” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, business dashboards show missed deliveries after new routing service launch. The option “Compare deliveries before and after rollout under matched demand” instead addresses the requested acceptance verification.
Question 668
The damaged vehicle classification environment at Insurance photo assessor faces this issue: claims teams seek automated detection of damaged panels from uploaded images. Supporting evidence shows that validation examples show visual categories differ from text-only customer descriptions. The architect must preserve the requirement that model outputs are advisory and claims decisions need human review. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Apply only sentiment analysis of the customer's filename
- Monitor low-confidence rates, model changes and reviewer overrides
- Determine labels, false-positive risk and annotated evaluation set
- Use a suitable vision-capable model or API with calibrated confidence and human escalation
Explanation
Correct Answer
D:
Use a suitable vision-capable model or API with calibrated confidence and human escalation targets the underlying issue (claims teams seek automated detection of damaged panels from uploaded images) rather than merely reporting symptoms. It also preserves the required outcome (model outputs are advisory and claims decisions need human review), which a target-state design must satisfy.
Incorrect Answers
A:
Filename sentiment cannot identify visual damage. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that model outputs are advisory and claims decisions need human review.
B:
The alternative “Monitor low-confidence rates, model changes and reviewer overrides” measures results without defining the preventive design now required. In the reported observation, validation examples show visual categories differ from text-only customer descriptions. The option “Use a suitable vision-capable model or API with calibrated confidence and human escalation” instead addresses the requested architecture selection.
C:
The alternative “Determine labels, false-positive risk and annotated evaluation set” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, validation examples show visual categories differ from text-only customer descriptions. The option “Use a suitable vision-capable model or API with calibrated confidence and human escalation” instead addresses the requested architecture selection.
Question 669
Regional healthcare network plans to update cross-team incident communication. Investigators found that timeline shows two status pages disagreed on user impact, consistent with the reported problem that operations and security teams issue conflicting statements during a cloud authentication incident. The response must satisfy the requirement that patient portals require one accountable incident communication path. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Map decision authority, approval requirements and factual status sources
- Let every engineer publish its own unverified outage explanation
- Create a single incident command and evidence-qualified status communication plan
- Watch approval delays, contradictory updates and stakeholder confusion
- Introduce communication templates and train technical and legal responders
Explanation
Correct Answers
C:
Create a single incident command and evidence-qualified status communication plan targets the underlying issue (operations and security teams issue conflicting statements during a cloud authentication incident) rather than merely reporting symptoms. It also preserves the required outcome (patient portals require one accountable incident communication path), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
E:
Introduce communication templates and train technical and legal responders is a controlled means to introduce the approved architecture while meeting the requirement that patient portals require one accountable incident communication path. 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 (operations and security teams issue conflicting statements during a cloud authentication incident), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
B:
Uncoordinated messaging can misstate patient impact. The shortcut does not supply the requested design and safe rollout for cross-team incident communication, where timeline shows two status pages disagreed on user impact.
D:
Monitoring cross-team incident communication for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: operations and security teams issue conflicting statements during a cloud authentication incident.
Question 670
The audit retention independence environment at Public pension agency faces this issue: project owners can delete Cloud Audit Logs exports stored in their own bucket. Supporting evidence shows that red-team drill shows the attacker can erase its administrative trail. The architect must preserve the requirement that statutory records require protected independent retention. Which migration or rollout step best manages risk, dependencies and reversibility?
- Rely only on an attacker-controlled project log bucket
- Enable org-level sinks and migrate consumers through verified log routing
- Route required logs to restricted central storage with retention protection
- Monitor sink error rate, retention status and privileged changes
Explanation
Correct Answer
B:
Enable org-level sinks and migrate consumers through verified log routing is a controlled means to introduce the approved architecture while meeting the requirement that statutory records require protected independent retention. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
A single mutable copy undermines evidentiary retention. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that statutory records require protected independent retention.
C:
The alternative “Route required logs to restricted central storage with retention protection” describes the chosen design, but not how it is introduced safely. In the reported observation, red-team drill shows the attacker can erase its administrative trail. The option “Enable org-level sinks and migrate consumers through verified log routing” instead addresses the requested controlled implementation.
D:
The alternative “Monitor sink error rate, retention status and privileged changes” addresses later monitoring rather than the actual controlled deployment. In the reported observation, red-team drill shows the attacker can erase its administrative trail. The option “Enable org-level sinks and migrate consumers through verified log routing” instead addresses the requested controlled implementation.