AI-103 Practice Question 88: Face Service Limited Access
Microsoft Azure AI Apps and Agents Developer Associate (AI-103) · Test 9 · question 8 of 10
A city transit agency wants to automatically blur faces in dashcam footage before releasing it publicly, using only face detection bounding boxes; it never needs to identify who anyone is. Because no identification or verification is involved, the team assumes no special approval process applies and plans to start calling the Face service right away.
What should they be told?
Show answer and explanation
Answer:
Microsoft gates the whole Face service, not just its recognition operations: "Face service access is limited based on eligibility and usage criteria... Face service is only available to Microsoft managed customers and partners. Use the Face Recognition intake form to apply for access." Face redaction (the blur-for-privacy scenario the agency wants) is listed as one of the service's own example use cases, built on the same gated resource as identification and verification. Detection-only use doesn't exempt a team from that gate.
- B is wrong because it's the exact mistaken assumption the team started with: the Limited Access requirement applies to the Face resource itself, not only to the identification and verification operations layered on top of detection. - C is wrong because it's a pointless workaround: it still calls a gated Face recognition operation, so it doesn't remove the access requirement, and it adds complexity that returns nothing the Detect operation didn't already provide. - D is wrong on the mechanics, not the access question: Image Analysis 4.0's people-detection feature returns bounding boxes around whole people, not faces, so it doesn't give the agency the face-level regions a blurring pipeline needs, regardless of its access model.
Reference: What is the Azure Face service?