Courseiva
Knowledge + Practice
CertificationsVendorsCareer RoadmapsLabs & ToolsStudy GuidesGlossaryPractice Questions
C
Courseiva

Free IT certification practice questions with explained answers for CCNA, CompTIA, AWS, Azure, Google Cloud, and more.

Certification Practice Questions

CCNA practice questionsSecurity+ SY0-701 practice questionsAWS SAA-C03 practice questionsAZ-104 practice questionsAZ-900 practice questionsCLF-C02 practice questionsA+ Core 1 practice questionsGoogle Cloud ACE practice questionsCySA+ CS0-003 practice questionsNetwork+ N10-009 practice questions
View all certifications →

Product

CertificationsCertification PathsExam TopicsPractice TestsExam Dumps vs Practice TestsStudy HubComparisons

Company

AboutContactEditorial PolicyQuestion Writing PolicyTrust Center

Legal

Privacy PolicyTerms of Service

Courseiva is a free IT certification practice platform offering original exam-style practice questions, detailed explanations, topic-based practice, mock exams, readiness tracking, and study analytics for Cisco, CompTIA, Microsoft, AWS, and other technology certifications.

© 2026 Courseiva. Courseiva is operated by JTNetSolutions Ltd. All rights reserved.

Courseiva is an independent certification practice platform and is not affiliated with, endorsed by, or sponsored by Cisco, Microsoft, AWS, CompTIA, Google, ISC2, ISACA, or any other certification vendor. Vendor names and certification marks are used only to identify the exams learners are preparing for.

Certifications›DP-900›Objectives›Describe considerations for working with non-relational data on Azure
Objective 3.0

Describe considerations for working with non-relational data on Azure

DP-900 Practice Questions

Use this page to practise Describe considerations for working with non-relational data on Azure questions for this certification. Focus on how the exam tests describe considerations for working with non-relational data on azure in scenario format — understanding the why behind each answer builds more durable knowledge than memorising options.

Full Practice Test →All Objectives

What this objective tests

DP-900 Describe considerations for working with non-relational data on Azure — Key Topics

Describe considerations for working with non-relational data on Azure questions on this certification test your ability to deploy and manage describe considerations for working with non-relational data on azure concepts in scenario-based situations.

  • Core Describe considerations for working with non-relational data on Azure concepts and how they apply in real-world cloud scenarios.
  • How to deploy describe considerations for working with non-relational data on azure correctly and verify the outcome.
  • Troubleshooting describe considerations for working with non-relational data on azure issues by interpreting error output and system state.
  • Cloud best practices and Describe considerations for working with non-relational data on Azure design trade-offs tested by this certification.

Common exam traps

Where candidates lose marks on Describe considerations for working with non-relational data on Azure

  • ⚠Selecting the most expensive service when a simpler managed option meets the requirement.
  • ⚠Forgetting that cloud resources must be explicitly secured — defaults are rarely secure.
  • ⚠Choosing a global service fix when the issue is region-specific.
  • ⚠Overlooking cost implications of cross-region data transfer in architecture questions.

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

30 questions from this objective

Question 2mediummultiple choice
Full question →

A social media application stores user profile data as JSON documents. Each user's document has a different structure, with fields that vary based on user activity. The application needs to query these documents efficiently using SQL-like syntax and support high write throughput. Which Azure data store is most appropriate for this workload?

Question 3mediummultiple choice
Full question →

A ride-sharing application needs to store real-time GPS location updates from drivers and passengers. The data is ingested as key-value pairs where the key is the user ID and the value is a timestamped location. The application requires low-latency reads and writes for millions of concurrent users, and the data model is simple with no need for complex queries or joins. Which Azure NoSQL database API should be used for this workload?

Question 4hardmultiple choice
Full question →

A global social media platform stores user profile images (JPEG) and activity logs in JSON format. The logs have varying structures based on the type of activity. The application requires low-latency reads of images from any region and the ability to query logs using SQL-like syntax. Which Azure data storage solution should they use for each data type?

Question 5easymultiple choice
Full question →

A retail company stores product catalog data as JSON documents. Each product has a different set of attributes depending on its category (e.g., electronics have 'voltage', clothing has 'size'). The application needs to query products by category and price range efficiently. Which Azure data store is most appropriate for this workload?

Question 6mediummultiple choice
Read the full NAT/PAT explanation →

A media company stores large video files and associated metadata (title, duration, tags) as JSON documents. The application requires low-latency streaming of videos to users worldwide and the ability to quickly query metadata by tag. Which combination of Azure services should the company use?

Question 7hardmultiple choice
Read the full NAT/PAT explanation →

A global gaming company develops a multiplayer game. Player profile data (username, email, preferences) is stored as simple key-value pairs and must be accessible with single-digit millisecond latency from any region. Game session logs are stored as JSON documents with varying fields (session ID, player actions, timestamps) and must be queryable by player ID and timestamp range using SQL-like syntax. The company wants to use a single Azure database service for both workloads. Which combination of Azure Cosmos DB APIs should they choose?

Question 8mediummultiple choice
Full question →

A social media application stores user profiles as JSON documents. Each user profile can have different attributes (e.g., some have 'education', others have 'work experience'). The application needs to query profiles by any attribute with low latency. Which Azure data store is most appropriate?

Question 9mediummultiple choice
Read the full NAT/PAT explanation →

A healthcare application stores patient medical records as JSON documents. Each document contains a variable set of fields depending on the patient's conditions. The application needs to query records by any field and support high write throughput. Which Azure data store is most appropriate?

Question 10mediummultiple choice
Read the full NAT/PAT explanation →

A social networking application stores user profiles as JSON documents. Each profile can have different fields (e.g., education, work history, interests) depending on what the user fills in. The application also needs to traverse friend connections as a graph to recommend new friends. The development team wants to use a single Azure Cosmos DB account for both workloads. Which combination of Azure Cosmos DB APIs should they choose?

Question 11mediummultiple choice
Full question →

A manufacturing company collects sensor readings from thousands of IoT devices. Each reading consists of a device ID, a timestamp, and a numeric value. The data is stored as key-value pairs and must support low-latency reads and writes at a global scale. The company also needs to query the data by device ID and time range. Which Azure Cosmos DB API should they choose?

Question 12mediummultiple choice
Read the full NAT/PAT explanation →

A social media platform stores user profiles as JSON documents where each profile can have different attributes (e.g., education, work history, interests). The platform also needs to traverse friend connections to recommend new connections using graph queries. The development team wants to use a single Azure Cosmos DB account for both workloads while minimizing complexity. Which combination of Azure Cosmos DB APIs should they choose?

Question 13mediummultiple choice
Full question →

A manufacturing company stores IoT sensor data as JSON documents in Azure Cosmos DB. Each document contains a device ID, a timestamp, and a varying set of sensor readings. The application frequently queries data by device ID and a time range to retrieve all readings for a specific device over a period. The development team wants to use an API that supports SQL-like queries on this JSON data. Which Azure Cosmos DB API should they choose?

Question 14hardmultiple choice
Read the full NAT/PAT explanation →

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?

Question 15mediummultiple choice
Full question →

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?

Question 16mediummultiple choice
Read the full NAT/PAT explanation →

A social media application stores user posts as JSON documents. Each post contains fields like post_id, author, content, and timestamp. The application needs to query posts by author and date range using SQL-like queries. Additionally, the application requires the ability to traverse follower relationships as a graph to suggest new friends. The development team wants to use a single Azure Cosmos DB account to minimize management overhead. Which combination of Azure Cosmos DB APIs should they choose?

Question 17easymultiple choice
Full question →

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?

Question 18mediummultiple choice
Full question →

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?

Question 19mediummultiple choice
Full question →

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?

Question 20easymultiple choice
Full question →

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?

Question 21mediummultiple choice
Full question →

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?

Question 22mediummultiple choice
Full question →

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?

Question 23mediummultiple choice
Full question →

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?

Question 24mediummultiple choice
Full question →

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?

Question 25mediummultiple choice
Full question →

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?

Question 26mediummultiple choice
Full question →

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?

Question 27easymultiple choice
Full question →

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?

Question 28mediummultiple choice
Full question →

A real-time leaderboard for an online game needs to store player scores and quickly retrieve the top 100 players. The data must update frequently as players achieve new scores, and the application requires sub-millisecond read and write latency. Which Azure data store is best suited for this requirement?

Question 29mediummultiple choice
Full question →

A gaming company stores player profiles as JSON documents. Each profile includes standard fields like playerId, username, and email, as well as optional fields such as achievements, gamePreferences, and friendsList. The application needs to look up profiles by playerId with low latency (under 10 ms) and also run SQL-like queries to find players who have a specific achievement. Which Azure Cosmos DB API should they choose?

Question 30mediummultiple choice
Full question →

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?

Question 31mediummultiple choice
Full question →

A global social media startup stores user profiles as JSON documents in Azure Cosmos DB. Their application frequently reads profiles by user ID and also runs queries to find users based on location or interests. The workload is read-heavy with high throughput requirements. The operations team notices that query performance degrades during peak hours. Which action would most effectively improve query performance?

More Describe considerations for working with non-relational data on Azure questions available in the full practice test.

Continue Practising →
←

Previous objective

Identify considerations for relational data on Azure

All DP-900 Objectives

  • 2.Identify considerations for relational data on Azure
  • 3.Describe considerations for working with non-relational data on Azure