Google Professional Cloud Architect Practice Test 79
Question 780
The short-lived GPU inference environment at AI satellite imagery group faces this issue: the product team leaves GPU instances running overnight for occasional image classification. Supporting evidence shows that billing shows high GPU idle cost with short bursts of queued requests. The architect must preserve the requirement that inference can tolerate several seconds of cold-start delay. What test must pass before the business accepts the remediated architecture?
- Canary burst routing with model artifact caching and capped quotas
- Verify output equivalence through GPU scale-down and restart events
- Measure model footprint, arrival patterns and accelerator warm-up cost
- Reserve the largest GPU fleet permanently for infrequent requests
Explanation
Correct Answer
B:
Verify output equivalence through GPU scale-down and restart events is a direct acceptance test of the path implicated by billing shows high GPU idle cost with short bursts of queued requests. It checks that the original risk (the product team leaves GPU instances running overnight for occasional image classification) has actually been controlled and tests that permitted operations still meet the requirement that inference can tolerate several seconds of cold-start delay.
Incorrect Answers
A:
The alternative “Canary burst routing with model artifact caching and capped quotas” documents change execution but not its operational acceptance result. In the reported observation, billing shows high GPU idle cost with short bursts of queued requests. The option “Verify output equivalence through GPU scale-down and restart events” instead addresses the requested acceptance verification.
C:
The alternative “Measure model footprint, arrival patterns and accelerator warm-up cost” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, billing shows high GPU idle cost with short bursts of queued requests. The option “Verify output equivalence through GPU scale-down and restart events” instead addresses the requested acceptance verification.
D:
Always-on capacity wastes cost when demand is highly intermittent. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that inference can tolerate several seconds of cold-start delay.
Question 781
At Telecom customer portal, the Google Cloud design for Google Cloud SDK workload identity is affected because a deployment script has a static JSON key checked into a Git repository. A review found that commit scan reveals key reuse across three build agents. The proposed response must account for the requirement that deployments need constrained short-lived credentials. A deployment ticket has been closed. What direct evidence would justify solution signoff?
- Inventory CI identity provider claims and project permissions
- Run job from a spoofed branch and confirm its identity condition denies deployment
- Copy the static key into the CI variable store without revoking it
- Transition build jobs to federation and revoke leaked keys
Explanation
Correct Answer
B:
Run job from a spoofed branch and confirm its identity condition denies deployment is a direct acceptance test of the path implicated by commit scan reveals key reuse across three build agents. It checks that the original risk (a deployment script has a static JSON key checked into a Git repository) has actually been controlled and tests that permitted operations still meet the requirement that deployments need constrained short-lived credentials.
Incorrect Answers
A:
The alternative “Inventory CI identity provider claims and project permissions” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, commit scan reveals key reuse across three build agents. The option “Run job from a spoofed branch and confirm its identity condition denies deployment” instead addresses the requested acceptance verification.
C:
Relocating the leaked credential does not eliminate its misuse risk. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that deployments need constrained short-lived credentials.
D:
The alternative “Transition build jobs to federation and revoke leaked keys” documents change execution but not its operational acceptance result. In the reported observation, commit scan reveals key reuse across three build agents. The option “Run job from a spoofed branch and confirm its identity condition denies deployment” instead addresses the requested acceptance verification.
Question 782
Digital university archive plans to update BigQuery scripted exports. Investigators found that audit log shows query scope expanded after a new dataset was added, consistent with the reported problem that a nightly bq CLI export uses wildcard datasets and leaks unrelated faculty research. The response must satisfy the requirement that exports must include only approved course statistics. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Give the export service account BigQuery Admin over the whole organization
- Use parameterized explicit BigQuery dataset/table scope with read-only job identity
- Track permission changes and unexpected query bytes
- Deploy export script with bounded project context and approved schedules
- Identify exact dataset boundaries, IAM roles and query requirements
Explanation
Correct Answers
B:
Use parameterized explicit BigQuery dataset/table scope with read-only job identity targets the underlying issue (a nightly bq CLI export uses wildcard datasets and leaks unrelated faculty research) rather than merely reporting symptoms. It also preserves the required outcome (exports must include only approved course statistics), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
D:
Deploy export script with bounded project context and approved schedules is a controlled means to introduce the approved architecture while meeting the requirement that exports must include only approved course statistics. 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:
Broad admin rights violate the limited read-only extraction purpose. The shortcut does not supply the requested design and safe rollout for BigQuery scripted exports, where audit log shows query scope expanded after a new dataset was added.
C:
Monitoring BigQuery scripted exports for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: a nightly bq CLI export uses wildcard datasets and leaks unrelated faculty research.
E:
This diagnoses the original issue (a nightly bq CLI export uses wildcard datasets and leaks unrelated faculty research), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
Question 783
At Retail delivery chain, the portfolio modernization sequencing workload has a documented risk: five app teams ask to migrate together though one shared customer database will be refactored. The review found that dependency map shows migration plans share an incompatible schema cutover. The architecture must also ensure that online ordering must remain open through staged rollout. The team must deliver the approved control safely. Which deployment sequence is most appropriate?
- Move less coupled read services first, then transactional dependencies
- Monitor integration failures and delivery milestones
- Prioritize a dependency-aware wave plan with measurable business milestones
- Schedule all components on one weekend without an integration dry run
Explanation
Correct Answer
A:
Move less coupled read services first, then transactional dependencies is a controlled means to introduce the approved architecture while meeting the requirement that online ordering must remain open through staged rollout. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
The alternative “Monitor integration failures and delivery milestones” addresses later monitoring rather than the actual controlled deployment. In the reported observation, dependency map shows migration plans share an incompatible schema cutover. The option “Move less coupled read services first, then transactional dependencies” instead addresses the requested controlled implementation.
C:
The alternative “Prioritize a dependency-aware wave plan with measurable business milestones” describes the chosen design, but not how it is introduced safely. In the reported observation, dependency map shows migration plans share an incompatible schema cutover. The option “Move less coupled read services first, then transactional dependencies” instead addresses the requested controlled implementation.
D:
Big-bang sequencing ignores the known shared dependency conflict. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that online ordering must remain open through staged rollout.
Question 784
Manufacturing telemetry provider plans to update private partner services. Investigators found that packet traces show traffic exposed through an unnecessary external load balancer, consistent with the reported problem that partners traverse the public internet to reach an internal metrics API. The response must satisfy the requirement that service access must be private and restricted to approved consumer networks. The design review is over and production introduction is next. Which action is the best fit?
- Cut over partners through approved endpoints and DNS changes in phases
- Create a broad public IP allowlist for all partner subnets
- Watch service attachment approvals and unexpected consumer connections
- Use Private Service Connect for scoped private service consumption
Explanation
Correct Answer
A:
Cut over partners through approved endpoints and DNS changes in phases is a controlled means to introduce the approved architecture while meeting the requirement that service access must be private and restricted to approved consumer networks. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
B:
A public allowlist does not provide an intrinsically private service endpoint. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that service access must be private and restricted to approved consumer networks.
C:
The alternative “Watch service attachment approvals and unexpected consumer connections” addresses later monitoring rather than the actual controlled deployment. In the reported observation, packet traces show traffic exposed through an unnecessary external load balancer. The option “Cut over partners through approved endpoints and DNS changes in phases” instead addresses the requested controlled implementation.
D:
The alternative “Use Private Service Connect for scoped private service consumption” describes the chosen design, but not how it is introduced safely. In the reported observation, packet traces show traffic exposed through an unnecessary external load balancer. The option “Cut over partners through approved endpoints and DNS changes in phases” instead addresses the requested controlled implementation.
Question 785
The emergency break-glass access environment at National investment office faces this issue: a single admin group controls production recovery and can also edit security logs. Supporting evidence shows that tabletop shows no independent emergency account if primary IdP fails. The architect must preserve the requirement that recovery access must be auditable and tightly time-bound. Choose the architecture that resolves the documented weakness without breaching the operational constraint.
- Review emergency usage, stale accounts and notification delay
- Share one break-glass password in the team chat channel
- Define protected break-glass identities with separated ownership and alerts
- Map critical emergency actions, alternative identities and audit paths
Explanation
Correct Answer
C:
Define protected break-glass identities with separated ownership and alerts targets the underlying issue (a single admin group controls production recovery and can also edit security logs) rather than merely reporting symptoms. It also preserves the required outcome (recovery access must be auditable and tightly time-bound), which a target-state design must satisfy.
Incorrect Answers
A:
The alternative “Review emergency usage, stale accounts and notification delay” measures results without defining the preventive design now required. In the reported observation, tabletop shows no independent emergency account if primary IdP fails. The option “Define protected break-glass identities with separated ownership and alerts” instead addresses the requested architecture selection.
B:
A widely shared emergency secret is not protected or attributable. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that recovery access must be auditable and tightly time-bound.
D:
The alternative “Map critical emergency actions, alternative identities and audit paths” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, tabletop shows no independent emergency account if primary IdP fails. The option “Define protected break-glass identities with separated ownership and alerts” instead addresses the requested architecture selection.
Question 786
Retail delivery chain plans to update portfolio modernization sequencing. Investigators found that dependency map shows migration plans share an incompatible schema cutover, consistent with the reported problem that five app teams ask to migrate together though one shared customer database will be refactored. The response must satisfy the requirement that online ordering must remain open through staged rollout. The team needs an operations signal rather than another design or one-time test. What should it track?
- Schedule all components on one weekend without an integration dry run
- Prioritize a dependency-aware wave plan with measurable business milestones
- Monitor integration failures and delivery milestones
- Check transaction stability and business KPIs after each wave
Explanation
Correct Answer
C:
Monitor integration failures and delivery milestones reveals recurrence, drift or changing dependencies after launch. It provides a repeatable signal for the risk (five app teams ask to migrate together though one shared customer database will be refactored) rather than treating the first successful test as permanent assurance.
Incorrect Answers
A:
Big-bang sequencing ignores the known shared dependency conflict. For this question, it is not a defensible choice for ongoing operational assurance and it does not satisfy the requirement that online ordering must remain open through staged rollout.
B:
The alternative “Prioritize a dependency-aware wave plan with measurable business milestones” selects a design, but does not provide the ongoing signal required to detect drift. In the reported observation, dependency map shows migration plans share an incompatible schema cutover. The option “Monitor integration failures and delivery milestones” instead addresses the requested ongoing operational assurance.
D:
The alternative “Check transaction stability and business KPIs after each wave” is a one-time acceptance result rather than ongoing operational assurance. In the reported observation, dependency map shows migration plans share an incompatible schema cutover. The option “Monitor integration failures and delivery milestones” instead addresses the requested ongoing operational assurance.
Question 787
Case study: Regional public broadcaster: license-compliant migration planning
Regional public broadcaster relies on license-compliant migration planning to deliver its operational commitments. The current architectural problem is that cloud project budget ignores legacy transcoding license entitlements. The team has recorded this evidence: vendor contract requires designated cores and annual renewal. Any proposed response must preserve the requirement that broadcast licensing must remain valid across hybrid operation.
The license-compliant migration planning environment at Regional public broadcaster faces this issue: cloud project budget ignores legacy transcoding license entitlements. Supporting evidence shows that vendor contract requires designated cores and annual renewal. The architect must preserve the requirement that broadcast licensing must remain valid across hybrid operation. What test must pass before the business accepts the remediated architecture?
- Inventory entitlement terms, renewal dates and workload migration sequence
- Assume cloud pay-as-you-go billing automatically grants third-party software licenses
- Stage licensed capacity migration with legal review and rollback
- Compare total budget and deployed licensed cores after cutover
Explanation
Correct Answer
D:
Compare total budget and deployed licensed cores after cutover is a direct acceptance test of the path implicated by vendor contract requires designated cores and annual renewal. It checks that the original risk (cloud project budget ignores legacy transcoding license entitlements) has actually been controlled and tests that permitted operations still meet the requirement that broadcast licensing must remain valid across hybrid operation.
Incorrect Answers
A:
The alternative “Inventory entitlement terms, renewal dates and workload migration sequence” collects prechange evidence without confirming that the revised service meets its outcome. In the reported observation, vendor contract requires designated cores and annual renewal. The option “Compare total budget and deployed licensed cores after cutover” instead addresses the requested acceptance verification.
B:
Infrastructure payment does not confer separate application rights. For this question, it is not a defensible choice for acceptance verification and it does not satisfy the requirement that broadcast licensing must remain valid across hybrid operation.
C:
The alternative “Stage licensed capacity migration with legal review and rollback” documents change execution but not its operational acceptance result. In the reported observation, vendor contract requires designated cores and annual renewal. The option “Compare total budget and deployed licensed cores after cutover” instead addresses the requested acceptance verification.
Question 788
Regional vehicle-parts supplier plans to update hybrid stock synchronization. Investigators found that network log shows packets re-route onto a congested internet path after the gateway reboot, consistent with the reported problem that headquarters reaches Google Cloud only through one IPsec tunnel that drops during maintenance. The response must satisfy the requirement that inventory updates need redundant private routing to two regions. Select TWO complementary actions: one durable target architecture and one controlled way to introduce it while preserving service. Which TWO are best?
- Inspect tunnel failure modes, BGP advertisements and required private destinations
- Use redundant HA VPN gateways with Cloud Router and independent peer paths
- Establish both encrypted paths and verify advertised routes before removing the old tunnel
- Use a single static VPN gateway and advertise a default public route for all stock traffic
- Alert on tunnel status, route withdrawals and peer latency
Explanation
Correct Answers
B:
Use redundant HA VPN gateways with Cloud Router and independent peer paths targets the underlying issue (headquarters reaches Google Cloud only through one IPsec tunnel that drops during maintenance) rather than merely reporting symptoms. It also preserves the required outcome (inventory updates need redundant private routing to two regions), which a target-state design must satisfy. This supplies the lasting-control half of the two-action package.
C:
Establish both encrypted paths and verify advertised routes before removing the old tunnel is a controlled means to introduce the approved architecture while meeting the requirement that inventory updates need redundant private routing to two regions. 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 (headquarters reaches Google Cloud only through one IPsec tunnel that drops during maintenance), but the TWO requested actions are the target architecture and its implementation; discovery was already completed.
D:
One tunnel and unscoped route reproduce the outage and security risk. The shortcut does not supply the requested design and safe rollout for hybrid stock synchronization, where network log shows packets re-route onto a congested internet path after the gateway reboot.
E:
Monitoring hybrid stock synchronization for future drift is useful after the rollout, but it does not specify the requested target control and safe implementation for this case: headquarters reaches Google Cloud only through one IPsec tunnel that drops during maintenance.
Question 789
Consider International cargo platform and its operational excellence ownership workload. The issue is that three independent teams deploy a critical shipment API without shared incident response rules; the current observation is that postmortem shows repeat outages with no accountable follow-up owner. The team must ensure that shipment tracking must meet a documented four-nine availability SLO. The target architecture is approved; execution without disruption is the remaining decision. Which rollout action is best?
- Set SLOs, runbooks and assigned reliability improvement backlog with accountable owners
- Review error-budget burn, recurring incidents and overdue corrective actions
- Declare the system reliable because developers resolved one emergency manually
- Launch an on-call rotation and practice incident handoff before expansion
Explanation
Correct Answer
D:
Launch an on-call rotation and practice incident handoff before expansion is a controlled means to introduce the approved architecture while meeting the requirement that shipment tracking must meet a documented four-nine availability SLO. Staged delivery, attributable change evidence and rollback guard against an otherwise avoidable service disruption.
Incorrect Answers
A:
The alternative “Set SLOs, runbooks and assigned reliability improvement backlog with accountable owners” describes the chosen design, but not how it is introduced safely. In the reported observation, postmortem shows repeat outages with no accountable follow-up owner. The option “Launch an on-call rotation and practice incident handoff before expansion” instead addresses the requested controlled implementation.
B:
The alternative “Review error-budget burn, recurring incidents and overdue corrective actions” addresses later monitoring rather than the actual controlled deployment. In the reported observation, postmortem shows repeat outages with no accountable follow-up owner. The option “Launch an on-call rotation and practice incident handoff before expansion” instead addresses the requested controlled implementation.
C:
One heroic recovery is not an operating model. For this question, it is not a defensible choice for controlled implementation and it does not satisfy the requirement that shipment tracking must meet a documented four-nine availability SLO.
Question 790
Consider City library data portal and its accessibility acceptance workload. The issue is that a redesigned public portal uses keyboard-inaccessible chart filters; the current observation is that accessibility audit finds focus cannot reach essential search fields. The team must ensure that government content must be accessible to assistive technology users. The team has completed discovery. Which preventive or corrective architecture is most appropriate?
- Approve launch solely because automated unit tests passed
- Track accessibility regressions and user support reports
- Include accessible components and automated/manual quality criteria in release requirements
- Review key workflows, keyboard navigation and applicable accessibility criteria
Explanation
Correct Answer
C:
Include accessible components and automated/manual quality criteria in release requirements targets the underlying issue (a redesigned public portal uses keyboard-inaccessible chart filters) rather than merely reporting symptoms. It also preserves the required outcome (government content must be accessible to assistive technology users), which a target-state design must satisfy.
Incorrect Answers
A:
Unit tests do not capture all interactive accessibility barriers. For this question, it is not a defensible choice for architecture selection and it does not satisfy the requirement that government content must be accessible to assistive technology users.
B:
The alternative “Track accessibility regressions and user support reports” measures results without defining the preventive design now required. In the reported observation, accessibility audit finds focus cannot reach essential search fields. The option “Include accessible components and automated/manual quality criteria in release requirements” instead addresses the requested architecture selection.
D:
The alternative “Review key workflows, keyboard navigation and applicable accessibility criteria” investigates the cause without specifying the durable architecture to resolve it. In the reported observation, accessibility audit finds focus cannot reach essential search fields. The option “Include accessible components and automated/manual quality criteria in release requirements” instead addresses the requested architecture selection.