Free Microsoft AI-103 Practice Exam with Questions & Answers | Set: 3

Comprehensive and Detailed 150 to 250 words of Explanation From Azure AI Apps and Agents Developer/Course Guide/topics:

The Safety metaprompt is not the Content Safety feature intended to measure harm-category severity and tune moderation thresholds against representative sample text.

A safety metaprompt provides additional behavioral instructions intended to guide a generative model toward safer responses. It can complement other safety controls, but it does not perform the specific text moderation test required to determine whether configured severity thresholds accept or reject sample prompts.

For threshold testing, Microsoft provides the Moderate text content experience. The user supplies sample text, selects Run test , and Content Safety returns detected categories and severity values. The Configure filters interface can then be used to change allowed or prohibited severity levels and retest the samples. Microsoft documents severity classifications including safe, low, medium, and high. Microsoft Learn

Therefore, the proposed Safety metaprompt solution does not meet the stated requirement.

This maps to the AI-103 objectives to configure safety filters, guardrails, risk detection, and content moderation , and to apply responsible-AI safety evaluations. Microsoft Learn

====================

Azure Vision in Foundry Tools Spatial Analysis is designed to process real-time streaming video and analyze the presence, movement, and spatial relationships of people in physical environments. It provides predefined operations such as personcrossingpolygon, which can identify when a person enters or exits a configured zone. The resulting personZoneEnterExitEvent can be consumed by an application to trigger alerts when an employee enters an area designated as high risk.

Spatial Analysis minimizes development effort because it supplies pretrained people-detection and zone-monitoring capabilities. Developers configure camera streams, polygonal zones, and event parameters instead of collecting images, labeling objects, and training a custom model.

Image Analysis primarily evaluates individual images and does not maintain movement or zone state across a live stream. Azure AI Video Indexer extracts searchable insights from video or live-stream content, but it is not the specialized option for detecting physical zone-entry events. Custom Vision object detection would require training data, labeling, model training, deployment, and additional application logic to track movement.

The Study Guide explicitly associates Spatial Analysis with detecting the presence and movement of people in video under Implement computer vision solutions → Analyze videos .

scope = " {{userId}} "

tools = [memory_tool]

The correct scope value is {{userId}} because the requirement is per-authenticated-user memory isolation without the client application manually generating user identifiers. In Microsoft Foundry Agent Service memory, the scope parameter partitions memory items inside the memory store. The official guidance states that when the memory search tool is attached to an agent, setting scope to the user identity template enables per-user memory isolation; the service resolves the end-user identity from the request header when provided, or falls back to the Microsoft Entra tenant ID and object ID of the caller. This matches the requirement to isolate stored preferences by authenticated user automatically.

The tools property must be [memory_tool] because the MemorySearchTool instance is created earlier and must be attached to the PromptAgentDefinition. Foundry guidance shows the memory search tool being passed in the agent definition as tools=[tool] , allowing the agent to read from and write to the configured memory store during conversations.

" session " and {{conversationId}} would limit continuity to a session or conversation instead of enabling long-term recall across separate conversations. [mem_store_name] is a list containing the store name, not a tool definition. Reference topics: Foundry Agent Service memory, memory stores, memory search tools, scope, and per-user isolation.