You are configuring throughput for your Cosmos DB container. What happens if you set the throughput lower than the actual consumption?
AThroughput is automatically increased.
BRequests are throttled.
CData is lost.
DLatency decreases.
Explanation
Requests exceeding set throughput will be throttled; others incorrectly suggest adjustments or outcomes that don’t occur.
Q22
What happens when you enable analytical store in Azure Cosmos DB?
AImproved performance for OLTP operations.
BReal-time analytics capabilities on transactional data.
CData replication to an on-premises SQL server.
DAutomatic backup of all Cosmos containers.
Explanation
Enabling analytical store offers real-time analytics while keeping transactional data intact; other options describe unrelated features.
Q23
A company needs to ensure that all documents in their Cosmos DB are consistent across global regions. Which consistency level should they choose?
AEventual consistency.
BBounded staleness.
CSession consistency.
DStrong consistency.
Explanation
Strong consistency guarantees linearizability across regions, unlike the other options which allow for some degree of inconsistency.
Q24
You are configuring a multi-region setup for Azure Cosmos DB. What setting must you enable for automatic failover?
AMulti-master replication.
BChange feed processor.
CService endpoints.
DAccount configuration.
Explanation
Automatic failover is set via account configuration; the other options do not relate directly to enabling failover.
Q25
Which service is primarily used for high availability in Azure Cosmos DB?
AMulti-region writes
BMongoDB API
CTransactional processing
DAzure Functions
Explanation
Multi-region writes enable high availability by replicating data across multiple regions, while others do not directly provide this feature.
Q26
A company needs to perform complex analytical queries on their data in Azure Cosmos DB. Which feature should they utilize?
AChange feed
BAggregation pipeline
CStored procedures
DSynapse Link
Explanation
Azure Synapse Link allows for complex analytics while Change feed and others are not ideal for that purpose.
Q27
What happens when you configure a Cosmos DB container's throughput to zero?
AAll data is deleted
BContainer becomes read-only
CData remains but cannot be accessed
DData is fully accessible
Explanation
Setting throughput to zero makes the container inaccessible, although the data is not deleted.
Q28
Which isolation level in Cosmos DB optimizes for performance but can result in reading uncommitted changes?
ARead-Only
BRead Committed
CSnapshot
DEventual
Explanation
Eventual consistency allows for improved performance at the cost of potential stale reads.
Q29
A company needs to store large amounts of streaming data for analysis in Azure Cosmos DB. Which API would be most suited for their needs?
ASQL API
BMongoDB API
CCassandra API
DGremlin API
Explanation
Cassandra API is optimized for time-series and streaming data scenarios.
Q30
You are configuring throughput for a new container in Azure Cosmos DB. What happens if you exceed the provisioned RU/s?
AYou get throttled and receive 429 errors.
BThroughput is automatically increased.
CQueries will be ignored.
DNo effect, it remains stable.
Explanation
Exceeding provisioned throughput results in throttling and 429 status codes indicating rate-limiting.