Practice Test #2

This is not the best answer for the question being asked. Error budget consumption is an internal SRE or reliability-management concept used by engineering teams to track service performance against objectives, but the prompt asks for a likely impact on the organization from customer-visible downtime. In a Digital Leader context, the broader business consequence of outages is more relevant than an internal operational metric.

Incorrect. Cloud provider SLAs for managed services are generally standardized and are not typically renegotiated simply because one month of availability was lower than expected. The more common outcomes are service credits, escalation with the provider, or architectural changes to improve resilience. De-emphasizing uptime commitments would not be a likely or sensible organizational response.

Incorrect. Reduced availability means the service was intermittently unavailable or unable to process requests, not that stored data was deleted. Data deletion is related to durability, backup strategy, replication, and disaster recovery rather than uptime percentage alone. An availability shortfall can disrupt operations, but it does not imply irretrievable database loss.

A multi-cloud approach means using services from multiple cloud providers, such as Google Cloud together with AWS or Azure. The question does not describe a need to distribute workloads across multiple public clouds, avoid vendor lock-in, or compare cloud-native services from different vendors. More importantly, multi-cloud does not inherently address the core requirement that all PHI remain stored only in the on-premises data center. Adding more clouds would usually increase governance, networking, and compliance complexity rather than solve the stated constraint.

A public-cloud approach would place the primary workload and data handling model in the cloud provider environment. That conflicts with the explicit requirement that all patient images and metadata must remain stored only in the hospital’s on-premises data center and that no PHI be persisted in the public cloud. Even if cloud services could be secured, the deployment model itself does not match the data residency and persistence restrictions in the question. Therefore, a pure public-cloud strategy is not appropriate here.

A private-cloud approach focuses on running infrastructure in a privately controlled environment, often entirely on-premises. While that could satisfy the requirement to keep PHI stored locally, it would not align with the goal of using Google Cloud’s advanced managed ML services such as Vertex AI. The question specifically asks for an overall cloud strategy that preserves on-prem data residency while still leveraging Google Cloud capabilities. That combination points to hybrid cloud, not private cloud alone.

Incorrect. Cloud SQL does not automatically train, deploy, or serve machine learning models on its transactional tables. Google Cloud provides machine learning capabilities through services such as Vertex AI and BigQuery ML, not as a built-in feature of Cloud SQL. This option describes functionality outside Cloud SQL’s core purpose as a managed relational database.

Incorrect. Cloud SQL does not include a native dashboarding or intelligent analytics interface for creating charts and business reports by itself. It is designed to run relational database workloads, not to replace BI products. To create executive dashboards or interactive analytics, teams typically connect Cloud SQL to tools such as Looker Studio or Looker.

Incorrect. Cloud SQL is not a built-in ETL or text-processing platform for converting unstructured data into structured relational tables. It stores structured relational data and can participate in data pipelines, but transformation of raw or unstructured data is handled by other services. This option describes data engineering functionality rather than a direct Cloud SQL capability.

A dashboard can help explore trends (descriptive analytics) and may surface correlations, but it is manual, subjective, and not a predictive system. It won’t reliably identify which current users are most likely to cancel, nor will it scale to continuous, proactive interventions. This is better for initial exploration, not for targeted retention at production scale.

Surveys can provide qualitative insights and may complement a churn program, but they are not sufficient for proactive identification of at-risk users. Response rates can be low and biased, and sentiment alone may not correlate strongly with churn. It also delays action compared to using existing behavioral and support data to predict churn now.

A summary report and quarterly discussion is retrospective and too slow for churn prevention. It doesn’t produce user-level risk scores or enable automated, timely interventions. Reporting can inform strategy, but it won’t operationalize AI-driven targeting to reduce cancellations in the near term.

Relying less on data and dashboards is the opposite of SRE best practice. SRE depends on observability (metrics, logs, traces) to make fast, correct decisions during incidents and to validate improvements against SLOs. Reducing dashboards might feel like it speeds decisions, but it typically increases guesswork, slows root-cause analysis, and can lead to more outages and more toil over time.

Having developers participate in on-call can be healthy, but removing SREs from on-call and assigning exclusive production ownership to developers does not address the core issue: repetitive manual operational work. It can also reduce reliability expertise during incidents and weaken systematic reliability engineering. SRE is about engineering reliability and reducing toil, not simply shifting operational burden to another team.

Spending less time measuring and documenting outage impact is not an efficiency best practice in SRE. Understanding impact supports blameless postmortems, prioritization, and SLO/error-budget decisions. Skipping impact analysis may reduce short-term effort but usually increases long-term cost by repeating incidents, misprioritizing fixes, and failing to justify automation or reliability investments.