A new API release should initially serve 5% of requests while its behavior is measured, then expand gradually. Which release pattern fits?

Choose the single best answer.

A.Blue-green deployment with an immediate unobserved switch of all users
B.A rolling deployment with no health checks or remaining capacity
C.A slot swap assumed to reverse every database change
D.Canary deployment using supported traffic-shift mechanisms

Show the answer and explanation

✓ Correct answer

Canary deployment using supported traffic-shift mechanisms

Canary deliberately exposes a small traffic share and expands on health evidence. The stated all-at-once blue-green switch does not provide the requested initial percentage, unsafe rolling replacement ignores readiness and capacity, and swaps cannot undo arbitrary database changes. Source guide: PDF page(s) 54.

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.