DP-900 Describe considerations for working with non-relational data on Azure Practice Test 4 — 15 Questions

Question 1

A logistics company tracks shipments. For each shipment, metadata (ID, weight, destination) is stored in a relational table. The route history is a sequence of events (timestamp, location, status) that is frequently appended but never updated or deleted. The application needs to quickly retrieve the latest status of a shipment and occasionally run analytical queries over the full route history. The company wants to minimize storage cost and use Azure services. Which Azure data store should they choose for the route history?

Choose an answer to begin — your selection is scored in the full session.

Accepted Answer

Azure Blob Storage with append blobs. Azure Blob Storage with append blobs is the correct choice because route history is write-once, read-many (WORM) data that is frequently appended but never modified or deleted. Append blobs are optimized for sequential append operations, offering low-cost storage for large volumes of event data, and they support fast retrieval of the latest status by reading the last block. This minimizes storage cost while allowing occasional analytical queries over the full history via Azure Synapse or other analytics services.

Answer

Azure Cosmos DB Core (SQL) API

Answer

Azure Table Storage

Answer

Azure SQL Database with a JSON column

Question 2

A gaming company stores player profiles as JSON documents. Each profile can have different attributes; for example, some profiles include an 'achievements' field while others include a 'purchaseHistory' field. The application must retrieve profiles by player ID with single-digit-millisecond latency and also support SQL-like queries on any attribute. Which Azure data store should the company use?

Accepted Answer

B. Azure Cosmos DB Core (SQL) API. Azure Cosmos DB Core (SQL) API is the correct choice because it natively stores JSON documents with flexible schemas, supports indexing on any attribute for SQL-like queries, and guarantees single-digit-millisecond latency for point reads by player ID. This meets the requirement for both fast key-based lookups and ad-hoc querying across varying profile attributes.

Answer

A. Azure Table Storage

Answer

C. Azure Blob Storage

Answer

D. Azure Database for PostgreSQL

Question 3

A social media application stores user sessions as JSON documents. Each session document has fields like sessionId, userId, startTime, endTime, and a list of pageviews. The application needs to quickly retrieve a session by its sessionId and also run queries like 'find all sessions for a user in the last 24 hours' using SQL-like syntax. The data has no fixed schema; different sessions may include additional optional fields like 'deviceType' or 'promotionCode'. Which Azure data store should the company use?

Accepted Answer

Azure Cosmos DB with SQL API. Azure Cosmos DB with SQL API is the correct choice because it natively supports storing JSON documents with flexible schemas, allows fast point reads by sessionId using a unique identifier, and enables SQL-like queries (e.g., filtering by userId and startTime) with automatic indexing. Its schema-agnostic design handles optional fields like deviceType or promotionCode without requiring schema changes, and it provides low-latency reads essential for real-time session retrieval.

Answer

Azure Table Storage

Answer

Azure SQL Database

Answer

Azure Blob Storage

Question 4

A social media company stores user-generated posts as JSON documents. Each post contains fields such as postId, userId, timestamp, and content. The application needs to query posts by userId and timestamp ranges with low latency, and also perform SQL-like queries across all posts. The data volume is growing rapidly and must scale globally. Which Azure data store should the company use?

Accepted Answer

B) Azure Cosmos DB SQL API. Azure Cosmos DB SQL API is the correct choice because it provides native support for querying JSON documents with low-latency, including indexed queries on fields like userId and timestamp. Its global distribution capability ensures data can be replicated across multiple Azure regions for low-latency access worldwide, while its SQL API allows SQL-like queries across all posts, meeting both requirements.

Answer

A) Azure Table Storage

Answer

C) Azure Blob Storage

Answer

D) Azure Cache for Redis

Question 5

A gaming company stores player session data as JSON documents. Each document contains fields like sessionId, userId, startTime, and a varying set of optional fields such as deviceType or campaignId. The application needs to query sessions by userId and startTime range using SQL-like queries, and also by sessionId with low latency. Which Azure Cosmos DB API should the company choose?

Accepted Answer

SQL (Core) API. The SQL (Core) API is the correct choice because it natively supports SQL-like queries over JSON documents, enabling efficient filtering by userId and startTime range. It also provides low-latency point reads by sessionId when a well-designed partition key (e.g., /userId) is used, and it offers automatic indexing of all JSON properties, including optional fields like deviceType or campaignId.

Answer

MongoDB API

Answer

Table API

Answer

Gremlin (Graph) API

Question 6

A healthcare organization stores medical imaging files (DICOM) that are actively used by radiologists for the first 30 days. After 30 days, the files are accessed infrequently for up to 5 years. After 5 years, they must be retained for legal compliance but are accessed very rarely. The organization wants to minimize storage costs. Which strategy should they use to manage the data lifecycle in Azure Blob Storage?

Accepted Answer

Store files in the Hot tier, move to Cool tier after 30 days, then to Archive tier after 5 years.. It aligns the data lifecycle with the access patterns: Hot tier for frequent initial access, Cool tier for infrequent access after 30 days, and Archive tier for long-term compliance after 5 years. Azure Blob Storage lifecycle management policies can automate these transitions, minimizing costs by using the most cost-effective tier for each phase.

Answer

Store all files in the Hot tier and use lifecycle management to move to the Archive tier after 5 years.

Answer

Store all files in the Archive tier from the beginning to minimize cost.

Answer

Store all files in the Cool tier to balance cost and access.

Question 7

A global e-commerce company needs to store user session data (key-value pairs) for a web application hosted in multiple Azure regions. The data must support low-latency reads and writes (under 10 ms) and be automatically replicated across regions for high availability. The development team also requires the ability to query sessions by user ID using a simple key lookup and occasionally filter by secondary attributes such as timestamp. Which Azure data store should they choose?

Accepted Answer

Azure Cosmos DB. Azure Cosmos DB is correct because it provides globally distributed, multi-region writes with automatic replication, guaranteeing low-latency reads and writes under 10 ms at the 99th percentile. Its key-value API (Table API or SQL API) supports simple key lookups by user ID and secondary indexing on attributes like timestamp, meeting all stated requirements.

Answer

Azure Table Storage

Answer

Azure SQL Database

Answer

Azure Cache for Redis

Question 8

A company stores historical sensor data in Azure Blob Storage. The data is accessed only a few times per year for compliance audits, but when requested, it must be available for reading within 15 minutes. The company wants to minimize storage costs. Which blob access tier should they use?

Accepted Answer

Cool. The Cool tier is the optimal choice because it balances low storage cost with the ability to retrieve data within minutes, meeting the 15-minute availability requirement. Archive would incur a retrieval delay of up to 15 hours, which violates the compliance audit SLA. Hot and Premium tiers are more expensive and unnecessary for data accessed only a few times per year.

Answer

Hot

Answer

Archive

Answer

Premium

Question 9

A social media startup needs to store user sessions as key-value pairs. Each session has a unique session ID, and the data needs to be globally distributed across multiple Azure regions to support low-latency reads for users worldwide. The development team expects heavy write throughput and needs flexible schema. Which Azure data store should they choose?

Accepted Answer

Azure Cosmos DB. Azure Cosmos DB is the correct choice because it provides globally distributed, multi-region writes and reads with turnkey global distribution, supports flexible schema via its document model, and offers multiple consistency levels to balance performance and data integrity. It is designed for high-throughput, low-latency workloads like user sessions, with session IDs serving as natural partition keys for efficient key-value lookups.

Answer

Azure Table Storage

Answer

Azure Blob Storage

Answer

Azure Cache for Redis

Question 10

A social media application stores user profiles as JSON documents. Each profile has standard fields like userId, name, and email, but also optional fields such as education and work history. The application needs to query profiles by userId with low latency and also run SQL-like queries to find all profiles with a specific work history value. Which Azure Cosmos DB API should they choose?

Accepted Answer

SQL (Core) API. The SQL (Core) API is the correct choice because it natively supports querying JSON documents with SQL-like syntax, enabling both low-latency point reads by userId and complex queries on nested fields like work history. It provides automatic indexing of all JSON properties, which ensures efficient execution of queries across optional fields without requiring schema management.

Answer

MongoDB API

Answer

Gremlin (Graph) API

Answer

Table API

Question 11

A company stores customer support chat transcripts as plain text files in Azure Blob Storage. The files are accessed frequently for the first 30 days, then infrequently for the next 2 years, and after that must be retained for 7 years for compliance but are rarely accessed. The company wants to minimize storage costs by automatically moving data through appropriate access tiers. Which Azure Blob Storage lifecycle management policy should they implement?

Accepted Answer

Move blobs from Hot to Cool after 30 days, then to Archive after 2 years. The lifecycle management policy matches the access pattern: move blobs from Hot (frequent access for first 30 days) to Cool (infrequent access for next 2 years) after 30 days, then to Archive (rare access for 7-year compliance) after 2 years. This minimizes storage costs by using the cheapest tier for each phase while retaining data for the required 7-year compliance period.

Answer

Store all data in Hot tier for the full retention period

Answer

Move blobs from Hot to Archive after 30 days and delete after 2 years

Answer

Store all data in Cool tier for the first 30 days, then move to Archive

Question 12

A gaming application stores player profiles as JSON documents. Each profile has standard fields like playerId, username, and email, but also optional fields such as achievements and gamePreferences. The application needs to query profiles by playerId with low latency and also run SQL-like queries to find players with specific achievements. Which Azure Cosmos DB API should they choose?

Accepted Answer

C: SQL (Core) API. The SQL (Core) API is the best choice because it natively supports JSON documents with flexible schemas (including optional fields like achievements and gamePreferences), provides low-latency point reads by playerId using the id field as the partition key, and enables SQL-like queries (e.g., SELECT * FROM c WHERE ARRAY_CONTAINS(c.achievements, 'specific_achievement')) without requiring a separate indexing or translation layer.

Answer

A: Table API

Answer

B: MongoDB API

Answer

D: Cassandra API

Question 13

A company stores massive amounts of unstructured log data as text files in Azure Blob Storage. The logs are written once and accessed only a few times per month for compliance audits. When accessed, the data must be available within 15 minutes. The company's priority is minimizing storage costs. Which Azure Blob Storage access tier should they use?

Accepted Answer

Cool. The Cool access tier is optimal because the logs are accessed infrequently (a few times per month) but require retrieval within 15 minutes. Cool tier offers lower storage costs than Hot while still supporting near-instant access, making it the best balance for minimizing storage costs with occasional compliance audits.

Answer

Hot

Answer