DP-900 Practice Test 15 — 15 Questions

Question 1

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

Archive

Answer

Premium

Question 2

A company stores user session data for a web application. Each session has a unique SessionID, UserID, start time, end time, and a variable set of attributes (e.g., pages visited, clicks, device type). The workload requires low-latency reads by SessionID and occasional queries by UserID and time range. Schema flexibility is critical because the attributes evolve over time. The team wants a fully managed NoSQL database that supports secondary indexing. Which Azure data store should they choose?

Accepted Answer

Azure Cosmos DB (NoSQL API). Azure Cosmos DB (NoSQL API) is correct because it is a fully managed NoSQL database that offers low-latency reads by SessionID (using a partition key), supports secondary indexing for queries by UserID and time range, and provides schema flexibility for evolving session attributes. Its multi-model API and global distribution meet the workload requirements without manual indexing or schema management.

Answer

Azure SQL Database

Answer

Azure Table Storage

Answer

Azure Blob Storage

Question 3

A company stores user profiles as JSON documents. Each profile includes standard fields (userId, name, email) and optional fields (preferences, history). The application needs fast key lookups by userId and SQL-like queries on optional fields. 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 JSON documents with flexible schemas, enabling fast key-value lookups on the `userId` field (via automatic indexing) and rich SQL-like querying (e.g., `SELECT * FROM c WHERE c.preferences.theme = 'dark'`) on optional fields. It is the only Azure Cosmos DB API that provides a SQL query syntax directly over JSON, making it ideal for mixed workloads of point reads and ad-hoc queries on nested or optional properties.

Answer

MongoDB API

Answer

Cassandra API

Answer

Table API

Question 4

A company is migrating a relational database to Azure SQL Database. They anticipate that the amount of stored data will grow significantly over time, but the compute requirements (CPU and memory) will remain relatively stable. Which purchasing model should they choose to allow independent scaling of storage and compute?

Accepted Answer

vCore-based purchasing model. The vCore-based purchasing model separates compute and storage costs, allowing you to scale storage independently without changing compute resources. This matches the scenario where data grows but compute requirements remain stable, as you can increase storage capacity without upgrading CPU or memory.

Answer

DTU-based purchasing model

Answer

Serverless compute tier

Answer

Hyperscale service tier

Question 5

A retail company needs to build an analytics pipeline on Azure. They ingest sales data from multiple store systems and an online e-commerce platform. The data must be cleaned, transformed, and loaded into a data warehouse for reporting. The company wants to use a modern ELT (Extract, Load, Transform) approach where raw data is stored first and then transformed. Order the following steps in the correct sequence for this pipeline. (Drag the steps into the correct order.)

Accepted Answer

Ingest data from sources using Azure Data Factory.. ELT approach first ingests raw data to storage, loads it into the warehouse, then transforms it before creating reporting structures.

Question 6

A company plans to migrate an on-premises SQL Server database to Azure. The database relies on SQL Agent jobs for nightly maintenance, uses Service Broker for asynchronous messaging, and requires high CPU and memory resources. The company wants to minimize application code changes. Which two Azure SQL deployment options meet all these requirements? (Choose two.)

Accepted Answer

Azure SQL Managed Instance. Azure SQL Managed Instance is correct because it provides near-100% compatibility with on-premises SQL Server, including SQL Agent jobs and Service Broker, while offering high CPU and memory resources. This minimizes application code changes by preserving existing features and configurations.

Answer

Azure SQL Database Single Database

Answer

Azure SQL Database Elastic Pool

Question 7

A company plans to migrate an on-premises SQL Server database to Azure. The database uses SQL Server Agent to run scheduled jobs and performs cross-database queries within the same instance. The company wants a fully managed PaaS solution that requires minimal application changes. Which Azure SQL deployment option should they choose?

Accepted Answer

Azure SQL Managed Instance. Azure SQL Managed Instance is the correct choice because it provides full SQL Server Agent support for scheduled jobs and enables cross-database queries within the same instance, while being a fully managed PaaS service. It offers near 100% compatibility with on-premises SQL Server, minimizing application changes during migration.

Answer

Azure SQL Database (single database)

Answer

Azure SQL Database elastic pool

Answer

SQL Server on Azure Virtual Machines

Question 8

A company develops an IoT device registry that stores device metadata as JSON documents. Each device has a unique DeviceID, and the attributes vary per device type (e.g., sensors, actuators). The application requires low-latency reads by DeviceID and needs global distribution to support devices worldwide. Which Azure Cosmos DB API should they choose to natively support JSON documents with flexible schema?

Accepted Answer

Azure Cosmos DB SQL API. The Azure Cosmos DB SQL API (formerly DocumentDB) is the correct choice because it provides native support for storing and querying JSON documents with flexible schema, allowing each device document to have a unique DeviceID and varying attributes per device type. It offers low-latency reads by DeviceID via direct point reads using the partition key, and supports global distribution through multi-region writes and automatic replication, meeting the worldwide deployment requirement.

Answer

Azure Cosmos DB Table API

Answer

Azure Cosmos DB for MongoDB API

Answer

Azure Cosmos DB Gremlin API

Question 9

A company plans to migrate an on-premises SQL Server database to Azure. The database uses SQL Server Agent for nightly maintenance jobs, Service Broker for asynchronous messaging, and requires cross-database queries within the same instance. The company wants a fully managed Platform as a Service (PaaS) solution that minimizes application code changes. Which Azure SQL deployment option should they choose?

Accepted Answer

Azure SQL Managed Instance. Azure SQL Managed Instance is the correct choice because it provides near 100% compatibility with on-premises SQL Server, including SQL Server Agent, Service Broker, and cross-database queries within the same instance, while being a fully managed PaaS offering. This minimizes application code changes because the migration can be performed with minimal schema or code modifications, unlike Azure SQL Database which lacks these features.

Answer

Azure SQL Database (single database)

Answer

Azure SQL Database elastic pool

Answer

Azure SQL Database Hyperscale

Question 10

A company archives legal documents that must be kept for 10 years. Access to these documents is extremely rare (maybe once a year). They want to minimize storage costs. Which Azure Blob Storage access tier is most cost-effective for this data?

Accepted Answer

Archive tier. The Archive tier is the most cost-effective for data that is accessed less than once a year and must be retained for a long period (10 years). It offers the lowest storage cost per GB among all Azure Blob Storage access tiers, but has the highest access and data retrieval costs, making it ideal for rarely accessed, long-term archival data like legal documents.

Answer

Hot tier

Answer

Cool tier

Answer

Cold tier

Question 11

A company plans to migrate an on-premises SQL Server database to Azure. The database currently uses SQL Server Agent jobs for scheduled maintenance tasks, cross-database queries, and query store for performance tuning. The database size is 500 GB and needs to scale to 10 TB eventually. They want a managed service that requires minimal application changes. Which Azure relational database service should they choose?

Accepted Answer

Azure SQL Managed Instance. Azure SQL Managed Instance is the correct choice because it provides near 100% compatibility with on-premises SQL Server, including support for SQL Server Agent jobs, cross-database queries, and Query Store, while being a fully managed PaaS service. It allows scaling up to 10 TB (up to 16 TB with some configurations) with minimal application changes, as it uses the same T-SQL surface area and network configuration (VNet) as on-premises SQL Server.

Answer

Azure SQL Database (single database)

Answer

Azure SQL Database Hyperscale

Answer

Azure Database for SQL Server

Question 12

A global social media app uses Azure Cosmos DB (NoSQL API) to store user profile data. The app is read-heavy and must serve content with the lowest possible latency to users worldwide. The data is updated by users, and the business has determined that eventual consistency is acceptable because immediate consistency after a write is not critical for profile views. Which consistency level should they choose to minimize read latency?

Accepted Answer

Eventual. Eventual consistency is the correct choice because it offers the lowest read latency by allowing reads to return data immediately without waiting for replication to complete. Since the app is read-heavy, global, and can tolerate eventual consistency for profile views, this consistency level minimizes the time to serve content by not imposing any ordering or staleness guarantees on replicas.

Answer

Strong

Answer

Bounded staleness

Answer

Session

Question 13

A company uses Azure SQL Database for an e-commerce application. The Orders table contains columns: OrderID (int, primary key), CustomerID (int), OrderDate (datetime), TotalAmount (decimal). Queries frequently filter by CustomerID and OrderDate to retrieve orders for a specific customer within a date range. Queries also need to retrieve a single order by OrderID quickly. Which indexing strategy will most improve the performance of these queries?

Accepted Answer

A) Keep the clustered index on OrderID and create a non-clustered index on (CustomerID, OrderDate). Option A is correct because the existing clustered index on OrderID efficiently supports the single-order lookup by primary key. Adding a non-clustered index on (CustomerID, OrderDate) provides a covering index for the range queries filtering by CustomerID and OrderDate, allowing SQL Server to perform an index seek and avoid key lookups, which significantly improves performance.

Answer

B) Change the clustered index to (CustomerID, OrderDate) and create a non-clustered index on OrderID

Answer

C) Keep the clustered index on OrderID and create a non-clustered index on (OrderDate, CustomerID)

Answer

D) Keep the clustered index on OrderID and create two separate non-clustered indexes on CustomerID and OrderDate

Question 14

A social media application stores user posts as JSON documents in Azure Cosmos DB. Each post includes fields such as postId, userId, content, timestamp, and an array of tags. The development team wants to query posts by userId and timestamp range using a SQL-like syntax. Which Azure Cosmos DB API should they choose?

Accepted Answer

B. Azure Cosmos DB for NoSQL API (Core SQL API). The Azure Cosmos DB for NoSQL API (Core SQL API) is the correct choice because it natively supports SQL-like querying (SELECT, WHERE, ORDER BY) over JSON documents. The team's requirement to query posts by userId and timestamp range using SQL-like syntax is directly supported by this API, which treats each JSON document as an item and allows filtering on nested fields like userId and timestamp. Other APIs either lack native SQL-like syntax or are optimized for different data models (e.g., MongoDB uses a JSON-like query language, Table API uses OData, Cassandra uses CQL).

Answer

A. Azure Cosmos DB for MongoDB API

Answer

C. Azure Cosmos DB for Table API

Answer

D. Azure Cosmos DB for Apache Cassandra API

Question 15

A social networking application needs to store and query relationships between users, such as 'friends of friends' to recommend new connections. The application must traverse these relationships efficiently. Which Azure NoSQL data store and API should they choose?

Accepted Answer

Azure Cosmos DB with Gremlin API. Azure Cosmos DB with Gremlin API is correct because it provides a graph database model specifically designed for storing and querying highly connected data, such as user relationships. The Gremlin API supports graph traversal queries (e.g., 'friends of friends') natively using the Apache TinkerPop graph traversal language, enabling efficient navigation of edges and vertices without expensive join operations.

Answer

Azure Cosmos DB with MongoDB API

Answer

Azure Table Storage

Answer

Azure Cosmos DB with SQL API