Instant Access Microsoft AI-103 Exam Premium Dumps - FreeCram

Correct Answer: A  🗳️

Correct:
* You configure a prompt shield for documents.
Prompt Shield for Documents: Highly Effective (Critical Defense)
How it helps: This shield specifically scans untrusted, third-party data inputs (like external documents or text extracted from uploaded images).
Mechanism: It evaluates the extracted image text before it is sent to the LLM to identify hidden jail
* You configure a prompt shield for user prompts.
Prompt Shield for User Prompts: Partially Effective (Defense in Depth)
How it helps: This shield targets direct jailbreak attempts written manually by the user in the text prompt field accompanying the upload.
Mechanism: It prevents the user from typing supporting instructions that prime the model to execute the hidden instructions found within the image.
* You configure image moderation to block unsafe content before processing the images.
Implementing rigorous image moderation is one of the most effective ways to secure multimodal AI systems against these threats. Moderation acts as a necessary gatekeeper, preventing malicious inputs from ever reaching the generative model.
Incorrect:
* You configure protected material detection.
Protected Material Detection: Ineffective for this Threat
Why it does not help: This feature is designed to scan model outputs to prevent the generation of copyrighted text, proprietary source code, or licensed imagery.
Limitation: It does not scan inputs for adversarial instructions and will not prevent a user from manipulating the model's logic.
Reference:
https://www.upgrad.com/blog/what-is-multimodal-ai/
https://learn.microsoft.com/en-us/azure/ai-services/content-safety/concepts/jailbreak-detection

Correct Answer: A  🗳️

To achieve full, multi-turn, and cross-session continuity with complete historical context (including user messages, agent messages, tool calls, and tool outputs), you must leverage the durable Conversation lifecycle provided by the Microsoft Foundry Agent Service runtime.
Because the underlying Agent Service can be stateless at the inference tier, managing continuity across days requires linking your agent interactions to a persistent, server-side conversation ID.
Here is exactly what must be done to meet your requirements:
*-> 1. Maintain a Durable Conversation ID
Instead of creating a brand-new conversation session every time a user returns, your application must persist and map the unique support case to a Microsoft Foundry Conversation ID (typically prefixed with resp_* or conv_*) in your external database.
New Case: Create a new session and capture the generated ConversationId.
Returning Case: Retrieve the previously saved ConversationId associated with that customer's support case from your database.
2. Resume Sessions via the SDK
When the customer returns days later, initialize the agent's session by passing the existing Conversation ID into the session creation method. This forces the Microsoft Foundry Agent Service to automatically reload the complete, un-summarized thread history on the backend before processing the next turn.
Reference:
https://learn.microsoft.com/en-us/agent-framework/agents/conversations/session

Correct Answer: B  🗳️

Keyless authentication with Microsoft Entra ID issues short-lived OAuth bearer tokens scoped per principal, which removes hardcoded secrets and produces per-principal audit trails. A managed identity extends this to service-to-service calls without storing any credential in code or configuration.

Correct Answer: A  🗳️

To ensure that conversation history does not persist across separate sessions, you must set the scope to session.
The session scope restricts data access to the current active chat instance. It automatically wipes or ignores previous data when a new session starts.
Incorrect:
[Not C]
user or {{$userId}} scope: Persists data across multiple sessions for that specific user. This would cause the exact issue you want to avoid by carrying historical context into new conversations.
References:
https://ai.gopubby.com/agents-with-memory-conceptual-undestanding-part-01-f6caedfcd96d?gi=a9aa95df15c6