Free Microsoft Azure AI-102 Actual Exam Questions - Question 5 Discussion
HOTSPOT You have an app that uses the AI Language custom question answering service. You need to ad alternatives for the word testing by using the Authoring API. How should you complete the JSON payload? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. 
D works because it directly lists alternatives as an array, no extra nesting.
D fits best since it uses a straightforward array of alternatives under "testing."
I agree with picking D since it uses a simple array under “testing” which seems to fit the question’s need for alternatives. The other options either add too much complexity or don’t clearly show synonyms. The key “alternatives” also feels right because it directly indicates alternative words. It matches what I’d expect for adding word variations without overcomplicating the payload.
I’d rule out A and B because they both use nested objects that seem too complex for just adding simple alternatives. D’s straightforward array under "alternatives" looks clean and matches similar JSON patterns I've seen.
I think option D works because it directly groups synonyms under "testing" in a simple array. Other options add unnecessary layers or keys that don’t seem required here.
D fits best since it clearly nests alternatives under "testing" without extra stuff.
D looks like the cleanest way to add synonyms under the “testing” key without extra unrelated data. The nested “alternatives” array fits the usual JSON pattern for this kind of update.
I’m thinking D might be better because it directly associates the alternatives with the term “testing” in a clear, nested way. The payload looks more structured for adding synonyms specifically, unlike option A which seems a bit flatter and might just overwrite data rather than add alternatives. Also, the way D uses an array of alternatives under the term feels more consistent with how you’d expect to expand vocabulary entries in a JSON format for this API.
Option D also looks promising because it uses "alternatives" properly under the term "testing." The structure matches how synonyms are usually added, unlike B or C which seem off.
Option A feels right since it targets the word directly with alternatives. The key point is we want synonyms, so anything about metadata alone like in B doesn’t fit the goal here.
Skipped option B cause it’s generic and doesn’t deal with synonyms. Looks like option A has the right structure for adding alternatives specifically to “testing.”