IT인증시험이 다가오는데 어느 부분부터 공부해야 할지 망설이고 있다구요? 가장 간편하고 시간을 절약하며 한방에 자격증을 취득할수 있는 최고의 방법을 추천해드립니다. 바로 우리Itcertkr IT인증덤프제공사이트입니다. Itcertkr는 고품질 고적중율을 취지로 하여 여러분들인 한방에 시험에서 패스하도록 최선을 다하고 있습니다. Microsoft인증AI-103시험준비중이신 분들은Itcertkr 에서 출시한Microsoft인증AI-103 덤프를 선택하세요.
| Section | Weight | Objectives |
|---|---|---|
| Topic 1: Implement information extraction and knowledge mining | 10–15% | - Extract structured data from documents
|
| Topic 2: Implement computer vision solutions | 10–15% | - Build multimodal solutions
|
| Topic 3: Plan and manage Azure AI solutions | 25–30% | - Design Azure AI infrastructure
|
| Topic 4: Implement generative AI and agentic solutions | 30–35% | - Design and implement intelligent agents
|
| Topic 5: Implement text and speech analysis solutions | 10–15% | - Implement speech capabilities
|
Microsoft AI-103 덤프로 많은 분들께서 Microsoft AI-103시험을 패스하여 자격증을 취득하게 도와드렸지만 저희는 자만하지않고 항상 초심을 잊지않고 더욱더 퍼펙트한Microsoft AI-103덤프를 만들기 위해 모든 심여를 기울일것을 약속드립니다.
질문 # 105
Hotspot Question
You have a Microsoft Foundry project that contains two agents named PolicyWriter and RskReviewer.
PolicyWriter generates daft updates for customer polices, and RiskReviewer reviews the drafts.
In the visual builder, you need to create a workflow that meets the following requirements:
- Finalizes low-risk updates without manual intervention
- Ensures predictable execution across the agents
- Requires user approval for highs updates
What should you configure? To answer, select the appropriate options in the answer area.
NOTE: Each comet selection is worth one point.
정답：
설명：
Explanation:
Box 1: The human-in-the-loop template that pauses execution of the workflow for input Human-in-the-loop template is correct. This pattern allows the system to run automatically for predictable, node-by-node agent execution while explicitly pausing the workflow when a high-risk condition is met to wait for human intervention.
Box 2: Add a Condition statement
Condition statement is correct. You must evaluate the risk level (low vs. high) before deciding whether to finalize the policy. A condition node checks the risk score output from RiskReviewer. If it is low, it routes to auto-finalization. If it is high, it routes to an approval step.
Reference:
https://techcommunity.microsoft.com/blog/azure-ai-foundry-blog/building-human-in-the-loop-ai-workflows-with-microsoft-agent-framework/4460342
질문 # 106
Your company is piloting a customer support agent in a Microsoft Foundry project name Project1. Project1 is connected to an existing Application Insights resource, and the company ' s support team reviews runs in the Traces tab.
The Foundry Agent Service is configured to perform the following actions:
* Retrieve the Application Insights connection string by calling
project_client.telemetry.get_application_insights_connection_string().
* Call configure_azure_monitor(connection_string=...) to enable telemetry.
A separate LangChain service configured to use OpenTelemetry and has the following configurations:
* Uses AzureAIOpenTelemetryTracer(connection_string=..., enable_content_recording=False)
* Passes the tracer by using config={ " callbacks " :[azure_tracer]}
Company policy has the following requirements:
* Telemetry from LangChain and OpenTelemetry must be distinguishable within the same Application Insights resource.
* Secrets and credentials must NOT be stored in prompts, tool arguments, or span attributes.
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
정답：
설명：
Explanation:
The LangChain service will appear in Traces without configuring a tracer: No Setting different OTEL_SERVICE_NAME values separates the services in Application Insights: Yes When using enable_content_recording=False, prompts and tool data will be captured in the telemetry: No The first statement is No because a separate LangChain or LangGraph application must emit telemetry through the configured tracing integration. Microsoft's LangChain tracing guidance states that you configure AzureAIOpenTelemetryTracer, attach it to the runnable or agent through callbacks, and then inspect the emitted traces in Azure Monitor. The troubleshooting guidance also states that missing LangChain or LangGraph spans are caused by tracing callbacks not being attached to the run.
The second statement is Yes . In OpenTelemetry, OTEL_SERVICE_NAME maps to the service.name resource attribute. Azure Monitor Application Insights uses cloud role names to represent separate services, and Microsoft states that when multiple services emit to the same Application Insights resource, cloud role names must be set so services are represented properly.
The third statement is No . enable_content_recording=False is specifically used to redact message content and tool call arguments from traces. Microsoft also advises disabling content recording in production and not storing secrets, credentials, or tokens in prompts or tool arguments. Reference topics: Microsoft Foundry tracing, LangChain tracing, OpenTelemetry service naming, Application Insights, and secure telemetry configuration.
질문 # 107
You have a Microsoft Foundry project that contains a high-traffic agent.
After a recent update, operational costs increase significantly.
Monitoring confirms that the volume of user traffic to the agent remains unchanged.
You suspect that changes to the request or response characteristics are causing the increase.
You need to identify whether the additional costs are driven by the model input size, the model output size, or expanded tool usage.
Which observability capability should you use?
정답：C
설명：
The correct capability is token usage . In Microsoft Foundry observability, token consumption is the primary signal for diagnosing model-cost changes when request volume is unchanged. Token usage lets you distinguish whether costs increased because prompts became larger, retrieved or tool-provided context expanded, responses became longer, or agent execution added more model calls. Microsoft Foundry monitoring dashboards track operational metrics such as token consumption, latency, error rates, and quality scores, and the agent monitoring dashboard is specifically intended to help analyze token usage, latency, success rates, and evaluation outcomes for production traffic.
This directly matches the scenario because the issue is not more traffic, but changed request or response characteristics. Input tokens reveal whether the prompt, chat history, grounding data, or tool outputs being sent to the model increased. Output tokens reveal whether the model is generating longer completions.
Expanded tool usage can also increase cost indirectly by adding more tool results, intermediate calls, and context into subsequent model requests; Foundry tracing and observability capture tool usage and token consumption for agent runs.
Evaluation metrics assess response quality and safety, not cost drivers. Latency identifies performance delays, and run success rate measures reliability. Reference topics: Microsoft Foundry observability, agent monitoring dashboard, token consumption, cost analysis, tool usage, and production monitoring.
질문 # 108
Case Study 1 - Contoso, Ltd
Overview
Company Information
Contoso, Ltd is a multinational retail company that builds, deploys, and manages generative AI and agent-based solutions by using Microsoft Foundry.
Existing Environment
Identity Environment
Contoso uses Microsoft Entra ID for identity management, authentication, and authorization capabilities that enable agents to access organizational resources and services.
Contoso recently formed a new AI engineering team named Agent1Dev Team to optimize and maintain existing AI solutions.
The team collaborates with solution architects, DevOps engineers, and security engineers to design, implement. monitor, and secure AI applications.
Contoso also has a team named Agent1Test Team that is responsible for validating AI solutions before the solution deployments.
Generative Environment
Contoso has a Microsoft Foundry deployment that contains two projects named Project1 and Project2.
Project1
Project1 contains a customer support agent named Agent1 that assists customers with product inquiries and troubleshooting requests.
Agent1 has the following configurations:
- Agent1 uses a base model deployment.
- A safety evaluation pipeline is NOT enabled.
- Tool invocation approval workflows are NOT enabled.
- Conversation memory constraints are NOT configured.
Agent1 interacts with customers by using digital support channels and answers general questions about Contoso products.
Project1 is deployed to an Azure region located in the European Union (EU).
Agent1Dev Team will use Project1 to optimize and maintain Agent1.
Project2
Project2 contains a deployed video generation model. The marketing department at Contoso has access to Project2 and plans to use the model to develop a video creation solution.
Development of the solution is incomplete.
Data Environment
Contoso stores product-related information in Azure resources that support AI applications.
The Azure environment contains an Azure Blob Storage account named storage1 that stores product detail sheets for all the Contoso products.
The product sheets include specifications, feature descriptions, and product support information that Agent1 can use to answer customer questions. The product sheets are stored in the PDF format.
Problem Statements
Contoso identifies the following issues:
- Agent1 has only general knowledge of the Contoso products.
- A recent chat interaction with Agent1 was analyzed for sentiment. The results of the analysis have NOT been processed yet.
- Agent1 does NOT use the detailed product information in the product sheets stored in storage1 when responding to customer questions.
- The finance department at Contoso reports that vendor invoices must be reviewed manually to ensure that the invoices match the terms defined in the vendor contracts. The invoices contain tables, logos, and varied layouts that make the documents difficult to process consistently.
Requirements
Planned Changes
Contoso plans to implement the following changes:
- Implement a solution for Project1 that analyzes the vendor invoices by evaluating both the visual layout and the textual content of the invoices, so that the invoice details can be verified against the vendor contract terms.
- Update the base model deployment used by Agent1 and standardize the model version to ensure continuity and consistent responses.
- Enable Agent1 to retrieve and use the detailed product information from the product sheets stored in storage1.
- Implement an indexing solution for the product sheets that Agent1 can use to answer customer questions.
- Complete the development of the video creation solution.
Technical Requirements
Contoso identifies the following technical requirements:
- The model deployment used by Agent1 must support scalable, high-throughput generative AI workloads and dynamically scale to handle variable customer support traffic, without requiring reserved throughput capacity.
- The product sheets must be processed by using an indexing pipeline that enables semantic and vector search, so that Agent1 can retrieve the relevant product information.
- Responses generated by using the product sheet information must be relevant, complete, and accurate.
- Agent1 must be able to use the product sheets to answer natural language questions about product details.
- The model version used by Agent1 must remain consistent to ensure stable responses.
- The data processed by the model must remain within the EU.
Security and Compliance Requirements
Contoso identifies the following security and compliance requirements:
- API keys must NOT be used to access Foundry-deployed models.
- Access to the Azure resources must follow the principle of least privilege.
- The developers at Contoso must authenticate to Microsoft Foundry resources by using Microsoft Entra authentication.
- Access to Project1 must be assigned to the members of Agent1Dev Team by using a security group named SC_Agent1_Dev.
- Access to Project1 must be assigned to the members of Agent1Test Team by using a security group named SC_Agent1_Test.
- Agent1 must never reveal customer information, even if a document that contains customer data is added erroneously to the product sheet repository in storage1.
- The product sheets might contain images that include embedded text. Agent1 must be protected from malicious instructions potentially hidden within the images.
Business Requirements
Contoso identifies the following business requirements:
- Users that interact with Agent1 must have a personalized experience in future interactions, including the ability for Agent1 to retain conversation context and recall relevant information from previous interactions.
- Agent1 must answer questions only about the products sold by Contoso.
Hotspot Question
You need to ensure that the marketing department can generate videos by using the model deployed to Project2.
How should you complete the Python code? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
정답：
설명：
Explanation:
Box 1: create
client.videos.create(...) initializes the generation job. This returns a video object containing a unique id and a status of "queued" or "in_progress".
Box 2: retrieve
client.videos.retrieve(video.id) refreshes the video object state from the server by fetching its updated completion progress and status until it finishes Reference:
https://developers.openai.com/api/reference/python/resources/videos/methods/create
질문 # 109
Hotspot Question
You need to create a new resource that will be used to perform sentiment analysis and optical character recognition (OCR). The solution must meet the following requirements:
- Use a single key and endpoint to access multiple services.
- Consolidate billing for future services that you might use.
- Support the use of Azure Vision in Foundry Tools in the future.
How should you complete the HTTP request to create the new resource? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
정답：
설명：
Explanation:
Box 1: PUT
Need to create a Cognitive Services Multi-Service resource using the PUT method. This specific resource type provides a single endpoint and key for multiple AI services, consolidates billing, and supports Azure Vision.
Box 2: CognitiveServices
Using the CognitiveServices kind creates a multi-service resource. This fulfills all the requirements by providing a single key and endpoint for multiple services, consolidating billing, and enabling access to features like Azure AI Vision and Text Analytics under one roof.
Reference:
https://learn.microsoft.com/en-us/azure/foundry/how-to/develop/sdk-overview
질문 # 110
......
Itcertkr의 Microsoft AI-103덤프를 공부하면 100% Microsoft AI-103 시험패스를 보장해드립니다. 만약 Microsoft AI-103 덤프자료를 구매하여 공부한후 시험에 탈락할시 불합격성적표와 주문번호를 메일로 보내오시면 덤프비용을 바로 환불해드립니다. 저희 Itcertkr Microsoft AI-103덤프로 자격증부자되세요.
AI-103최신 업데이트 인증공부자료: https://www.itcertkr.com/AI-103_exam.html