Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail organization is building an e-commerce platform to manage a rapidly changing product catalog and personalized user profiles. Because different products have unique attributes that evolve frequently, the engineering team has the following requirements:
Which database model best meets the organization's requirements?
A NoSQL document database (such as Firestore or Firestore in Datastore mode) is a non-relational database system designed for automatic horizontal scaling, high performance, and flexible application development. Instead of storing data in rigid tables with uniform rows and columns, a document model organizes information into self-contained documents or entities grouped into collections or kinds.
size and color properties while a laptop has processor and memory properties.Non-relational (NoSQL) databases encompass several specialized models tailored to different access patterns:
| Non-Relational Model | Structure & Storage Mechanism | Common Use Cases |
|---|---|---|
| Document | Stores semi-structured data in JSON-like documents or entities with flexible fields | E-commerce product catalogs, user profiles, content management |
| Key-Value | Pairs a unique identifier (key) with an opaque value or payload (such as JSON or BYTES) | High-speed lookups, session state, caching |
| Wide-Column | Organizes data into scalable tables with row keys and dynamic column families | High-throughput time-series data, IoT telemetry, financial ledgers |
For rapidly changing datasets like retail catalogs and user profiles, a NoSQL document database eliminates the operational bottleneck of frequent schema migrations while providing built-in horizontal scalability and ACID transactions for real-time application workloads.
A conventional relational database management system (RDBMS) organizes structured data into predefined tables consisting of rows (records) and columns (attributes). It uses Structured Query Language (SQL) to manage and query data, enforcing strict relationships and data integrity across multiple normalized tables.
NULL values or complex multi-table schemas that require expensive SQL JOIN operations.JSON or BYTES data types, whereas conventional relational databases remain bound by rigid schemas and vertical scaling limits.This model would be the right choice if the organization were building a legacy enterprise resource planning (ERP) or accounting system with highly uniform, predictable data structures that require complex ad hoc SQL joins across normalized tables.
While relational databases excel at structured transactional integrity, NoSQL document models were specifically developed to overcome the rigidity and horizontal scaling limitations of conventional relational tables when handling rapidly evolving application data.
A partitioned columnar storage model (used by analytical platforms like BigQuery with its Capacitor storage format) stores data by column rather than by row and divides large tables into smaller physical segments called partitions, typically based on a DATE or TIMESTAMP column.
This model would be the optimal solution if the engineering team needed to store years of immutable application clickstream logs in a data warehouse and wanted to reduce query costs and scan times when analyzing traffic for specific date ranges.
Columnar storage in an analytical data warehouse should not be confused with a NoSQL wide-column or NoSQL document database. Analytical columnar storage powers batch and interactive SQL analytics, while NoSQL models power real-time, flexible operational workloads.
A star schema is a relational data modeling technique used in analytical data warehouses (such as BigQuery). It organizes structured business data into a central fact table containing quantitative metrics (such as order amounts, discounts, and quantities) linked via keys to surrounding dimension tables (such as customer, supplier, or region).
This option would be appropriate if the retail organization wanted to consolidate historical sales transactions from multiple stores into a central data warehouse so business analysts could run complex SQL aggregations on quarterly revenue trends.
A common misconception is confusing analytical data warehouses with non-relational operational databases. Even though both can scale to petabytes of data, data warehouses optimize for scanning millions of rows to compute aggregates, whereas NoSQL document databases optimize for retrieving and updating individual semi-structured records in milliseconds.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated