Every tenant in an elastic pool now runs a large batch at 09:00. Why can they all throttle despite acceptable individual database limits?

Choose the single best answer.

A.Their overlapping total demand exceeds the pool's resource budget
B.Per-database limits eliminate all shared-resource contention
C.The pool automatically reserves each database's maximum so total demand is irrelevant
D.Elastic pools replicate writes to every tenant database

Show the answer and explanation

✓ Correct answer

Their overlapping total demand exceeds the pool's resource budget

Pool and per-database constraints both apply. Individual headroom does not supply aggregate budget. Pooling does not replicate tenant writes, and limits do not guarantee contention-free simultaneous peaks. Source guide: PDF page 24.

Read the source reference

This item is flagged for content review.

Read and review here, or open the app to practise and save your results on this device.

Practise in the app

Unofficial study aid; not affiliated with or endorsed by Microsoft. Original practice questions are not real examination questions and do not guarantee an exam result.