Microsoft Azure

Azure Cosmos DB Developer Specialty

DP-420

Specialize in Azure Cosmos DB with the DP-420 exam designed for developers.

147 questions 0 views Free
Start Mock Test Timed · Full-length · Scored

Questions 111–120 of 147

Q111

What happens when you exceed the provisioned throughput in Azure Cosmos DB?

  • A Queries are throttled
  • B Data loss occurs
  • C Latency improves temporarily
  • D Throughput increases automatically
Explanation Queries are throttled when the provisioned throughput is exceeded to ensure fair resource usage.
Q112

Which indexing mode in Azure Cosmos DB allows for flexible querying but may incur higher storage costs?

  • A Consistent
  • B Custom
  • C Spatial
  • D Default
Explanation Custom indexing mode provides more control over indexing, allowing optimization for specific queries but typically increases storage costs due to additional index storage requirements.
Q113

A company needs to automatically scale its Azure Cosmos DB based on application usage. What feature should be used?

  • A Autoscale provisioned throughput
  • B Manual scaling
  • C Partitioning
  • D Replicated throughput
Explanation Autoscale provisioned throughput automatically adjusts the RU/s based on usage, ensuring performance without manual intervention.
Q114

What happens when you exceed the provisioned throughput in Azure Cosmos DB?

  • A Request succeeds with extra charge
  • B Request fails with 429 status
  • C Database shuts down temporarily
  • D Read throughput is prioritized
Explanation When throughput limits are exceeded, requests return a 429 status code, indicating Too Many Requests and signaling to retry later.
Q115

Which feature of Azure Cosmos DB ensures low latency?

  • A Multiple consistency models
  • B Global distribution of data
  • C Stored procedures support
  • D Data encryption at rest
Explanation Global distribution allows low latency by bringing data closer to users.
Q116

A company needs to ensure its documents in Azure Cosmos DB do not exceed 2 MB in size. What should they implement to handle larger documents?

  • A Chunking the data
  • B Using stored procedures
  • C Increased throughput provision
  • D Change partition key
Explanation Chunking allows larger documents to be stored in smaller parts without losing data integrity.
Q117

What happens when you change the partition key of an existing container in Azure Cosmos DB?

  • A Data is automatically migrated
  • B Data access is improved
  • C This is not allowed
  • D Throughput is automatically adjusted
Explanation Azure Cosmos DB does not allow changing the partition key once defined.
Q118

A company needs to optimize their data queries in Azure Cosmos DB to handle an increase in read throughput. Which approach should they consider?

  • A Implement dedicated database throughput
  • B Use manual partitioning for data
  • C Reduce the number of indexes
  • D Use multiple account regions
Explanation Dedicated throughput increases performance for database operations, while other options do not directly improve read throughput.
Q119

What happens when you exceed the provisioned throughput on a Cosmos DB container?

  • A All operations are blocked
  • B Requests are throttled with 429 status
  • C Data is automatically replicated
  • D Throughput is dynamically increased
Explanation Exceeding throughput results in throttled requests with a 429 status code, while other options are incorrect behaviors.
Q120

You are configuring Azure Cosmos DB for multi-region replication. Which configuration helps achieve low-latency reads?

  • A Read replicas in multiple regions
  • B Active-Active with multi-region writes
  • C Change feed processing only
  • D Using single region fallback
Explanation Active-Active configuration allows for low-latency reads by enabling writes in multiple regions, unlike other options that do not support this effectively.