Free Microsoft Azure AI-102 Actual Exam Questions - Question 12 Discussion
HOTSPOT You have an Azure subscription that has the following configurations: • Subscription ID: 8d3591aa-96b8-4737-ad09-OOf9b1ed35ad • Tenant ID: 3edfe572-cbS4-3ced-ae12-c5c177f39a12 You plan to create a resource that will perform sentiment analysis and optical character recognition (OCR). You need to use an HTTP request to create the resource in the subscription. The solution must use a single key and endpoint. How should you complete the request? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. 
I’m pretty sure the key part is that they want a single resource for both OCR and sentiment analysis. That’s what the new “Cognitive Services” resource is for, so the request should create that one. The URL needs to point to the subscription and specify the resource type as “CognitiveServices” and not the old individual services. Also, the endpoint should be the one assigned to that Cognitive Services resource, not the regional or service-specific endpoints, since that’s how you get unified access with one key. This aligns well with options mentioning the new resource type and unified endpoint
I’m thinking the request should hit the /subscriptions path to specify which subscription we’re working with. The unified Cognitive Services resource lets you call both OCR and sentiment analysis through one key, so it won’t need separate endpoints for each. Also, the HTTP method needs to be PUT since you’re creating the resource. If you use POST, it might be for actions or queries but not resource creation. So, a PUT to the subscription-level resource path seems right here.
I think option B makes sense since the new Cognitive Services resource supports both OCR and sentiment analysis under one endpoint. The request URL should include the subscription ID and resource group to scope it correctly.
I’d pick B for resource type since Cognitive Services supports both features, and D for the location because the request URL usually includes the region like eastus or westus. That matches typical Azure API patterns.
B for resource type, because Cognitive Services covers both tasks with one key.
B for the resource type, since Cognitive Services covers both tasks with one key.
This one’s tricky without more context, feels like B or C for the endpoint.