Scenario practice questions

A small business whose customers are all located within 10 kilometers of the company's single data center

Why wrong: When users are geographically clustered near the origin server, CDN provides minimal latency benefit. The geographic distribution gap that CDN solves doesn't exist in this scenario.

A real-time financial trading application that requires unique, uncacheable price data delivered to a single city's traders

Why wrong: CDNs provide no benefit for uncacheable, real-time data. Financial trading data is unique per request and cannot be served from cache. A CDN would add complexity without value here.

An internal HR system used exclusively by employees in the company's headquarters

Why wrong: Internal systems with a geographically concentrated user base near the origin don't benefit from CDN. CDN is optimized for external-facing, geographically distributed traffic.

Economies of scale — the cloud provider has more purchasing power than the startup.

Why wrong: Economies of scale is a cloud benefit, but it relates to cost efficiency, not speed of deployment. The scenario specifically highlights the speed advantage.

Geographic reach — the cloud provider has data centers in more regions.

Why wrong: Geographic reach is relevant to global availability but the primary benefit illustrated here is the speed of provisioning, not the number of available regions.

Reliability — cloud providers have better uptime SLAs than on-premises servers.

Why wrong: Reliability (SLAs) is a cloud benefit but doesn't explain why the startup can launch in 2 weeks instead of 6–8 weeks.

Public cloud — all workloads run in a provider's infrastructure.

Why wrong: Public cloud means all resources are in the cloud provider's infrastructure. The hospital specifically keeps patient records on-premises, so this is not a pure public cloud model.

Private cloud — all workloads run in the hospital's own infrastructure.

Why wrong: Private cloud means all computing happens in the hospital's owned/managed infrastructure. Using Google Cloud's AI services makes this a hybrid, not a pure private cloud.

Multi-cloud — using multiple public cloud providers simultaneously.

Why wrong: Multi-cloud refers to using multiple different public cloud providers (e.g., both Google Cloud and AWS). This scenario is on-premises + one cloud provider — hybrid, not multi-cloud.

Hybrid cloud

Why wrong: Hybrid cloud combines on-premises infrastructure with public cloud. Using two different public cloud providers (AWS + Google Cloud) is multi-cloud, not hybrid — there's no on-premises component described.

Multi-region

Why wrong: Multi-region typically describes using multiple geographic regions within the same cloud provider. Using two different providers (AWS and Google) is multi-cloud.

Distributed cloud

Why wrong: Distributed cloud extends a public cloud provider's services to edge locations or customer premises — a specific architecture, not the multi-provider strategy described.

Private cloud

Why wrong: Private cloud means infrastructure is dedicated to a single organization and may be located on-premises or in a dedicated hosted environment. Using Google's shared public infrastructure is not a private cloud.

Hybrid cloud

Why wrong: Hybrid cloud combines on-premises (or private cloud) infrastructure with public cloud. If all workloads are in Google Cloud with nothing on-premises, this is pure public cloud, not hybrid.

Community cloud

Why wrong: Community cloud is infrastructure shared among organizations with common requirements (e.g., government agencies). Using Google Cloud commercially is a public cloud deployment.

Cloud Interconnect — it connects on-premises to Google Cloud.

Why wrong: Cloud Interconnect provides network connectivity between on-premises and GCP. It doesn't manage workload deployment or provide unified container management.

Google Distributed Cloud — runs Google Cloud services inside the customer's data center.

Why wrong: Google Distributed Cloud (GDC) brings Google Cloud hardware and services on-premises. It's an extreme option for air-gapped environments. Anthos is the broader hybrid management platform for most use cases.

Cloud Deployment Manager — deploys resources via infrastructure-as-code templates.

Why wrong: Cloud Deployment Manager is GCP's native IaC service (similar to CloudFormation). It doesn't manage cross-environment container workloads.

Cloud Armor, which filters incoming requests based on IP allowlists and denylists

Why wrong: Cloud Armor provides DDoS protection and WAF capabilities at the network/application layer. It filters based on IP addresses and request attributes, not device management status or device security posture.

Identity-Aware Proxy (IAP), which provides application-level authentication but without device checks

Why wrong: IAP provides application-level identity-based access control. It can integrate with Access Context Manager for device checks, but IAP alone (without Access Context Manager) does not enforce device security posture requirements.

VPC Service Controls, which restrict access to Google APIs based on network perimeter membership

Why wrong: VPC Service Controls define network-level perimeters around Google Cloud resources. They restrict access based on network (project/VPN membership), not individual device security attributes.

Cloud Armor, by blocking requests from IP addresses associated with personal devices

Why wrong: Cloud Armor blocks based on IP addresses and request attributes, not device management status. Personal devices don't have distinct IP addresses identifiable at the network layer.

Enabling two-factor authentication for all users, which prevents unauthorized access

Why wrong: 2FA strengthens authentication but doesn't differentiate between managed and unmanaged devices. A user could successfully authenticate with 2FA on a personal device and still download files.

Encrypting all Google Drive files so they cannot be read on personal devices

Why wrong: Google Drive files are encrypted at rest by Google, but this encryption is transparent to authorized users. An authenticated user can still download and read files on a personal device — encryption doesn't prevent downloads.

Company B must have spent more on cloud than Company A, proving that higher cloud investment always produces better outcomes

Why wrong: Investment level is not the differentiating factor. Company A may have spent as much or more on its migration. The type of value created — operational efficiency vs. new customer capabilities — is the differentiator.

Company A made a mistake by moving to cloud; it should have stayed on-premises to avoid disruption

Why wrong: Moving to cloud was not Company A's mistake. The mistake was treating cloud purely as infrastructure without reimagining business capabilities. On-premises would have been even more constraining.

Company B succeeded because it used a different cloud provider with superior technology

Why wrong: The question attributes the difference to what each company built with cloud (new capabilities vs. existing app migration), not which provider they used. Provider choice is not the differentiating factor.

The company also needs to migrate its email to a cloud-based provider before transformation is complete

Why wrong: Email migration is an IT infrastructure change, not digital transformation. The advisor is pointing to a more fundamental reimagining of customer experience and business model, not additional IT migrations.

The company must also migrate its accounting software to the cloud before claiming digital transformation

Why wrong: Accounting software migration is IT modernization. The advisor's point is about creating new customer-facing value, not completing a checklist of IT migrations.

Cloud storage alone cannot store inventory data; additional specialized database services are required

Why wrong: Cloud storage can store inventory data in many forms. The advisor's point is about business transformation, not technical storage capability.

Software as a Service (SaaS)

Why wrong: SaaS delivers fully managed applications over the internet (e.g., Gmail, Salesforce). The customer manages nothing except data and user access — the provider manages everything from hardware to the application.

Platform as a Service (PaaS)

Why wrong: PaaS provides a managed runtime environment where the customer deploys applications without managing OS or middleware. App Engine is Google's PaaS — the customer manages code and data, not the infrastructure below.

Function as a Service (FaaS)

Why wrong: FaaS (serverless) provides event-driven execution of individual functions — the provider manages everything except the function code. This is more managed than IaaS.

Disaster recovery planning

Why wrong: Disaster recovery planning addresses business continuity in the event of failures. The application categorization described is a migration strategy exercise.

Capacity planning for on-premises servers

Why wrong: Capacity planning sizes on-premises infrastructure. The scenario describes categorizing applications for cloud migration, not sizing servers.

Software development lifecycle (SDLC) planning

Why wrong: SDLC describes the stages of building software. The described activity is migration strategy assessment, not development lifecycle planning.

Cloud Scheduler, which triggers a series of jobs at specified cron intervals

Why wrong: Cloud Scheduler triggers individual jobs on a time schedule. It doesn't orchestrate multi-step workflows with conditional branching (e.g., 'if build passes, deploy; else notify'). Workflows is designed for that logic.

Cloud Pub/Sub, by publishing messages between pipeline stages to trigger each subsequent step

Why wrong: Pub/Sub can connect loosely coupled event-driven systems but doesn't natively orchestrate sequential workflow logic with conditional branching and state management. Pub/Sub is asynchronous messaging, not workflow orchestration.

Cloud Run, by writing the orchestration logic as a container application that calls other services sequentially

Why wrong: You could write orchestration logic as a Cloud Run application, but this requires custom code for retry handling, state management, and error recovery that Workflows provides out of the box. Using the purpose-built service is more maintainable.

The company wants to pay less for cloud services.

Why wrong: Managed private clouds cost MORE than public clouds due to dedicated hardware. Cost savings favor public cloud's multi-tenant economics.

The company wants the fastest possible internet speeds for their applications.

Why wrong: Network performance is not tied to public vs. private cloud distinction. Public clouds have massive, redundant network infrastructure.

The company has fewer than 10 employees and doesn't need multi-tenant scale.

Why wrong: Company size doesn't determine cloud type. A 10-person company can effectively use public cloud. Managed private cloud is driven by regulatory requirements, not company size.

Data warehousing — storing historical data for reporting purposes.

Why wrong: Data warehousing is the technical solution, not the organizational concept. The cultural shift to making decisions based on data is called becoming 'data-driven.'

Business intelligence — creating reports and dashboards.

Why wrong: BI tools and dashboards are enablers. The organizational concept being described is data-driven decision making — the culture of using data to guide choices, not just the reporting technology.

Data governance — policies for who owns and manages data.

Why wrong: Data governance defines ownership, quality standards, and access controls. Data-driven decision making is the cultural practice of using data for decisions — distinct from governance policies.

IT infrastructure modernization — replacing on-premises servers with cloud VMs.

Why wrong: The transformation is not about infrastructure replacement — it is about fundamentally changing the customer experience and the operational process (from manual spreadsheets to real-time automated tracking).

Cost reduction initiative — eliminating the spreadsheet software license fees.

Why wrong: The primary outcome is 35% higher customer satisfaction from improved service. Spreadsheet license costs are trivial compared to the business value of improved customer experience.

Employee productivity transformation — helping logistics coordinators work faster using cloud apps.

Why wrong: Employee productivity is a secondary benefit. The primary transformation is customer-facing: real-time shipment visibility and automated notifications.

Outsourcing — moving work to contractors in lower-cost locations.

Why wrong: Outsourcing involves transferring work to external parties. Remote work (enabled by cloud) is internal employees working from distributed locations, not work being outsourced.

Digital transformation — the company is changing its business model.

Why wrong: While enabling remote work may be part of a broader transformation, the specific capability described is cloud-enabled distributed work — using cloud tools for productivity from any location.

Automation — replacing human work with AI and robotics.

Why wrong: Automation replaces human tasks with machines. Remote work enablement is about empowering human employees to work from anywhere, not replacing them.

Cost reduction through infrastructure consolidation and server decommissioning

Why wrong: The value described is not infrastructure cost reduction — it is operational effectiveness (35% fewer stockouts, 28% less waste) enabled by real-time data integration and ML.

Business continuity improvement through data backup and disaster recovery in the cloud

Why wrong: Backup and disaster recovery are infrastructure concerns. The scenario describes active decision-making transformation using live data, not resilience planning.

Employee productivity improvement through providing staff with cloud-based collaboration tools

Why wrong: Collaboration tools address productivity, not the supply chain decision-making transformation described. The value driver here is ML-powered demand sensing, not employee tooling.

The company is automating its accounting system using cloud software.

Why wrong: Accounting automation is unrelated. The described transformation is about operations — specifically maintenance practices on physical manufacturing equipment.

The company is replacing human maintenance workers with robots.

Why wrong: Predictive maintenance informs human maintenance scheduling — it doesn't replace maintenance workers with robots.

The factory is migrating its ERP system to the cloud to improve supply chain visibility.

Why wrong: ERP migration is a separate IT project. The described transformation is specifically about equipment maintenance prediction using IoT sensor data and ML.

The primary challenge is selecting the correct cloud database for patient records.

Why wrong: Database selection is a technical detail. The scenario highlights organizational change management — aligning legal, IT, and clinical leadership around the transformation.

The hospital should delay cloud adoption until quantum computing makes it more secure.

Why wrong: Waiting for hypothetical future technology is not a strategy. Present cloud security frameworks (HIPAA eligibility, encryption, audit logs) adequately address healthcare data requirements.

The legal department's concerns prove that healthcare organizations cannot use public cloud.

Why wrong: Legal concerns are addressable. Thousands of healthcare organizations worldwide successfully use compliant cloud platforms (with HIPAA BAAs, regional data residency, etc.).