Cloud Digital Leader Why cloud technology is transforming business Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  A relational database that stores all prices with daily batch updates from a pricing spreadsheet.

  Why it's wrong here

  A relational database with daily batch updates from a spreadsheet is fundamentally mismatched to sub-hourly price optimization. By the time batch jobs copy rows overnight, market signals, competitor prices, and demand shifts are already stale, so any price derived from that data is obsolete before it is displayed. Even if the batch interval were shortened, the pipeline still relies on manual spreadsheet export and lacks the low-latency, event-driven ingestion needed for true real-time pricing.

• ✓

  Real-time stream processing (Pub/Sub + Dataflow) combined with ML model serving (Vertex AI) to ingest signals and compute optimized prices at scale.

  Why this is correct

  This architecture directly implements the required behavior: Pub/Sub ingests a continuous stream of events such as web traffic, competitor price feeds, and inventory levels, while Dataflow performs windowed feature computation and invokes a Vertex AI model to score the optimal price per product. Because Dataflow auto-scales its worker pool, millions of events per minute can be processed without manual capacity planning, and Vertex AI's online prediction service returns scored prices in the tens of milliseconds. The resulting price updates are written to a serving database and pushed to the storefront, enabling true minutes-level dynamic pricing.

• ✗

  A cloud-hosted ERP system that replaces the on-premises inventory management system.

  Why it's wrong here

  Migrating the on-premises inventory management system to a cloud ERP like SAP S/4HANA Cloud or Oracle Fusion improves data consistency and availability but does not add real-time pricing capabilities. An ERP is designed for transactional processes—order management, procurement, financials—and although it may expose inventory levels via APIs, it is not a low-latency stream-processing and ML-inference platform. The scenario requires continuous signal ingestion and model-based price optimization, which remains outside an ERP's functional scope even when hosted on Google Cloud.

• ✗

  A static website hosted on Cloud Storage that displays current prices.

  Why it's wrong here

  A static website hosted on Cloud Storage serves identical HTML, CSS, and JavaScript to every visitor until an operator manually uploads new files. It has no compute runtime, no database connection, and no ability to read live signals, so it cannot alter a price in response to demand, competition, or inventory changes. Even if client-side JavaScript fetched data, the pricing logic and data storage would still need to live elsewhere, making the static host an irrelevant component of a dynamic pricing solution.

Go deeper

Related to this question