Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The AZ-900 Microsoft Azure Fundamentals Exam practice bank has 688 more like it. Try 10 free: instant score, no account.
An online retail company is architecting a production database solution for an application with unpredictable and fluctuating traffic spikes. The company requires predictable performance with guaranteed low latency during sudden demand surges, while avoiding response delays caused by cold starts.
Which cloud database configuration should the company choose to ensure predictable performance and reliability?
Azure Cosmos DB serverless mode is a consumption-based operational model where you are billed exclusively for the Request Units (RUs) consumed by your individual database operations and the storage used.
While serverless is cost-effective for intermittent, low-volume, or non-production environments, it can experience cold-start latency after periods of inactivity. For high-volume production applications requiring strict, predictable performance during sudden traffic surges, cold starts can degrade user experience and violate response time requirements.
The scenario focused on a development environment, prototype, or lightweight internal application with sporadic, low-volume traffic where minimizing idle costs is the primary goal.
Azure Cosmos DB provisioned throughput with autoscale is a capacity management model that allows database resources to automatically scale up and down instantly based on incoming workload demand. Instead of paying for peak capacity continuously or suffering from cold-start latency, autoscale scales throughput (measured in Request Units per second, or RU/s) within a defined range.
For high-demand, variable production systems, provisioned throughput with autoscale provides the best balance of predictability, reliability, and cost control, eliminating latency spikes during sudden load shifts.
Manual throughput in Azure Cosmos DB assigns a fixed allocation of Request Units (RU/s) to a database or container that remains constant regardless of active traffic volume unless manually altered by an administrator.
Setting manual throughput to the minimum baseline fails to handle variable demand and sudden traffic surges. When user requests exceed the statically provisioned capacity, Azure Cosmos DB responds with HTTP 429 (Too Many Requests) rate-limiting errors, creating application failures and unpredictable performance for end users.
The workload experienced a completely steady, predictable transactional rate 24/7 with virtually no deviation or demand spikes.
The Azure Cosmos DB Emulator is a downloadable local application that emulates the Azure Cosmos DB cloud service in an on-premises or local workstation environment for development and testing purposes.
The emulator is not a cloud-hosted production service. It runs on local hardware, lacks cloud scalability, offers no high-availability guarantees, and cannot serve live, public production traffic or handle distributed enterprise workloads.
A developer needed to write and test database queries on a local machine without establishing an active internet connection or incurring cloud billing costs.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated Validated