Last reviewed
Correct answer: D. It is still part of the specification, but scheduled for removal and not for new implementations.
Explanation
The principle — Deprecated is a defined state in a lifecycle, not a mood.
Why the key is correct — A Deprecated feature remains part of the specification but is scheduled for removal: new implementations SHOULD NOT adopt it, and existing implementations SHOULD migrate before the feature's earliest removal. Three facts in one sentence — still specified, going away, and different advice for new code than for old.
Why the others are wrong — It has not been removed, it does not stop working, and there is a policy behind it rather than an opinion.
Remember this — Still there, still working, on notice.
Sources — MCP first-party documentation.
Sources
“A Deprecated feature remains part of the specification but is scheduled for removal: new implementations SHOULD NOT adopt it, and existing implementations SHOULD migrate before the feature's earliest removal.”
Practise 10 questions on this topic
Take MCP Fundamentals — Timed Test 1 (10 questions) — scored instantly, explanation for every question, no login.