All three formats of Microsoft AI-200 practice test are available with up to three months of free Microsoft AI-200 exam questions updates, free demos, and a satisfaction guarantee. Just pay an affordable price and get Microsoft AI-200 updated exam dumps today. Best of luck!
| Section | Objectives |
|---|---|
| Plan and manage Azure AI solutions | - Monitor and optimize AI solutions - Plan security and compliance requirements - Select appropriate Azure AI services |
| Implement and monitor AI workloads | - Deploy AI models and services - Monitor performance and troubleshoot issues |
| Implement Azure AI solutions | - Implement knowledge mining with Azure AI Search - Implement natural language processing solutions - Implement generative AI solutions using Azure OpenAI - Implement computer vision solutions |
As you know, today's society is changing very fast. We also need new knowledge to fill in as we learn. And our AI-200 learning prep can suit you most in this need for you will get the according certification as well as the latest information. AI-200 Exam simulation is selected by many experts and constantly supplements and adjust our questions and answers. When you use our AI-200 study materials, you can find the information you need at any time.
NEW QUESTION # 78
A company is developing a solution that allows smart refrigerators to send temperature information to a central location.
The solution must receive and store messages until they can be processed. You create an Azure Service Bus instance by providing a name, pricing tier, subscription, resource group, and location.
You need to complete the configuration.
Which Azure CLI or PowerShell command should you run?
Answer: C
NEW QUESTION # 79
Case Study 1 - Fabrikam Inc.
Background
Fabrikam Inc. is a global retail analytics company that provides AI-driven demand forecasting and product recommendation services to online retailers. The company is modernizing its solution to run entirely on Microsoft Azure.
The platform ingests transaction data, generates embeddings for semantic retrieval, performs vector similarity search, and returns product recommendations through containerized microservices. Developers use Python and Azure SDKs. Operations teams manage container orchestration, scaling, monitoring, and security.
The solution must meet strict performance, scalability, and security requirements.
Current environment
Application architecture
The Recommendation engine is a customer-facing HTTP API running as a containerized Python application. The engine is deployed to Azure Container Apps (ACA).
Embeddings are stored in Azure Database for PostgreSQL by using pgvector.
Semantic retrieval uses metadata filtering combined with vector similarity search.
Azure Managed Redis is used as a caching layer.
Front-end and API workloads are deployed to Azure Container Apps (ACA).
Batch model retraining workloads run in Azure Kubernetes Service (AKS).
Container and CI/CD
Container images are stored in Azure Container Registry (ACR).
CI/CD uses ACR Tasks to build images on commit.
ACA environments support revision management.
AKS workloads are deployed by using Kubernetes manifest files stored in Git.
Monitoring
Logs are collected in Azure Monitor.
Teams inspect container logs and Kubernetes events when troubleshooting.
Developers write KQL queries to analyze latency spikes.
Business requirements
Customer experience: Maintain a seamless, low-latency recommendation experience for end- users, even during unpredictable seasonal traffic spikes.
Operational cost efficiency: Minimize compute expenditures by deallocating resources during periods of inactivity and by preventing runaway scaling costs.
Data integrity and freshness: Ensure that product recommendations always reflect the most current catalog metadata and pricing to prevent customer dissatisfaction.
Security and compliance: Adhere to a Zero Trust security model by eliminating long-lived credentials and centralizing the management of all sensitive secrets.
Global scalability: Support the rapid ingestion of millions of new product embeddings daily without degrading query performance for existing retailers.
Technical requirements
Performance: Semantic search latency must remain under 200 milliseconds at peak load.
Database optimization: Use pgvector for embeddings and implement metadata filtering to reduce compute overhead. Configure compute and memory appropriately for vector workloads to ensure high-dimensional index residency in RAM and efficient mathematical throughput. Vector similarity calculations must be performed only against products that satisfy mandatory metadata constraints.
Database performance: Database connections must support high concurrency with minimal latency through the implementation of connection optimization.
Data load strategy: To ensure maximum ingestion throughput, secondary indexes must be applied only after bulk loading of embeddings is complete.
Caching: Redis cache entries must expire automatically after 10 minutes. Implement a reactive mechanism to invalidate cache entries upon metadata updates.
Identity: Use managed identities for all service-to-service and service-to-database authentication.
Plain-text credentials in configuration files are strictly prohibited.
Secret management: All secrets must be stored centrally. Secrets must be rotated automatically by using a centralized lifecycle policy.
Scaling: Use Kubernetes event-driven autoscaling (KEDA) for event-driven scaling. The Recommendation API must scale based on HTTP traffic, while batch jobs must scale based on queue length and support scale-to-zero.
CI/CD: All images must be stored in Azure Container Registry. Use ACR Tasks to automate image builds triggered by source code commits.
Monitoring: Use KQL to analyze performance telemetry and troubleshoot microservice connectivity failures. Inspect logs and events when troubleshooting AKS and ACA.
Drag and Drop Question
You need to troubleshoot connectivity failures between microservices running in AKS.
Which troubleshooting actions should you perform? To answer, move the appropriate action to the correct troubleshooting scenario. You may use each action once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation:
Box 1: Inspect Pod descriptions
Inspecting Pod descriptions is an excellent and standard first troubleshooting step to fix inter- service communication failures in Azure Kubernetes Service (AKS).
To remedy a communication failure between containerized microservices in Azure Kubernetes Service (AKS), the first and most direct troubleshooting action is to verify and debug core Kubernetes networking and DNS resolution within the cluster.
1. Check Pod Status: Ensure both the source and target pods are actively running.
Run kubectl get pods -n <namespace> to check for crash loops.
2. Verify DNS Resolution
Etc.
Box 2: Inspect Pod descriptions
To troubleshoot sudden or frequent Pod restarts in Azure Kubernetes Service (AKS), you should inspect Pod descriptions first, as they contain the Last State, Exit Code, and Reason (such as OOMKilled) for the restarted container.
Pod descriptions (Correct Choice): This is the best starting point. Running kubectl describe pod
<pod-name> provides a comprehensive status overview. It specifically reveals the Last State of the container, the Exit Code, and the Termination Reason (e.g., OOMKilled if it exceeded memory limits, or Error). It also displays the Pod's recent lifecycle events at the bottom.
Incorrect:
Container logs: While highly valuable, logs are only useful if the application managed to write an error message to stdout or stderr before crashing. If a Pod is killed externally by the system (such as an Out-Of-Memory event), the container logs will suddenly stop without showing the root cause.
Box 3: Inspect Pod descriptions
To address readiness probe failures, the most immediate and effective troubleshooting action is to inspect the Pod descriptions.
Pod descriptions: This is the correct starting point. Running kubectl describe pod <pod-name> provides a dedicated Events section at the bottom of the output. This section explicitly details exactly why a readiness probe failed, including the specific error codes, timeouts, or connection refusals, and lists the exact timestamps of the failures.
Reference:
https://blog.devgenius.io/k8s-troubleshooting-pod-in-containercreating-status-e89e093d996e?gi=e4e93cbfd5d6
https://learn.microsoft.com/en-us/troubleshoot/azure/azure-kubernetes/availability-performance/troubleshoot-oomkilled-aks-clusters
NEW QUESTION # 80
Drag and Drop Question
You are developing a solution for a hospital to support the following use cases:
- The most recent patient status details must be retrieved even if
multiple users in different locations have updated the patient record.
- Patient health monitoring data retrieved must be the current version
or the prior version.
- After a patient is discharged and all charges have been assessed, the patient billing record contains the final charges.
You provision an Azure Cosmos DB for NoSQL database and set the default consistency level for the database account to Strong.
You set the value for Indexing Mode to Consistent.
You need to minimize latency and any impact to the availability of the solution. You must override the default consistency level at the query level to meet the required consistency guarantees for the scenarios.
Which consistency levels should you implement? To answer, drag the appropriate consistency levels to the correct requirements. Each consistency level may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Answer:
Explanation:
Explanation:
Box 1: Strong
Strong consistency must be used at the query level to meet this requirement.
Linearizability Guarantee: Strong consistency ensures that a read operation always returns the most recent committed version of an item.
Global Consensus: Because multiple users in different locations are updating the patient record, any reader across any region must wait for the updates to be fully committed globally before reading. This prevents any user from reading stale or out-of-order data, which is critical for patient status details.
Box 2: Bounded Staleness
To minimize latency and maximize availability while ensuring that retrieved patient health monitoring data is either the current version or the immediate prior version, you should override the consistency level at the query level to Bounded Staleness.
Version Guarantee: Bounded Staleness ensures that reads are not older than a specific time window or a configured number of versions K versions behind the latest write). Setting the version staleness to 1 (K=1 )guarantees that the data read is either the current version or the prior version.
Lower Latency: Bounded Staleness offers significantly lower latency than the account's default Strong consistency. Strong consistency requires a global majority acknowledgment before a read or write completes, increasing latency.
Higher Availability: By backing down from Strong consistency to Bounded Staleness for this query, you reduce the strict synchronization requirements, thereby minimizing impacts on availability during localized network disruptions.
Box 3: Eventual
Eventual consistency is the correct consistency level to use at the query level for this scenario.
Maximizes Performance: Eventual consistency offers the lowest latency and highest availability among all consistency levels.
Matches Scenario Needs: The billing record is final and no longer changing, so there is no risk of reading stale, in-progress updates.
Optimizes Costs: Eventual consistency queries consume half the Request Units (RUs) compared to Strong or Bounded Staleness queries.
Reference:
https://learn.microsoft.com/en-us/azure/cosmos-db/consistency-levels
NEW QUESTION # 81
A customer support bot built with Azure AI Foundry Agent Service must ground its answers strictly in an internal knowledge base and avoid hallucinating unsupported facts.
What should you implement?
Answer: B
Explanation:
Connect the agent to an Azure AI Search knowledge source and explicitly constrain its instructions to answer from retrieved evidence. Microsoft Foundry Agent Service can use Azure AI Search to retrieve proprietary organizational content and ground model responses in that content. Retrieved documents provide the factual context from which the model generates its answer, and Azure AI Search can return source references for attribution.
Microsoft ' s RAG guidance also specifically recommends using clear system instructions that require the model to stay within retrieved content when hallucination risk must be reduced. If the available evidence does not support an answer, the instructions should direct the agent to state that the information is unavailable rather than inventing facts. Retrieval grounding substantially reduces unsupported generation, although production systems should still evaluate outputs because grounding alone does not mathematically guarantee zero hallucinations.
Increasing temperature would generally increase output variability and is contrary to the objective. A larger context window without retrieval does not give the model access to the organization ' s internal knowledge base. Disabling content filtering weakens safety controls and has no role in factual grounding.
Study Guide references: Microsoft Foundry Agent Service # Azure AI Search tool; RAG grounding; knowledge sources; source attribution; grounding instructions.
NEW QUESTION # 82
You need to translate real-time spoken customer conversations from English to Spanish text during a support call, with minimal latency.
Which Azure AI service should you use?
Answer: D
Explanation:
Use Azure AI Speech with Speech Translation . Microsoft documents Speech Translation as a real-time capability that accepts a live audio stream in a source language and returns translated text, synthesized speech, or both in one or more target languages. This matches the scenario precisely: the input is spoken English during a live support call, the required output is Spanish text, and latency must be minimal.
Speech Translation can be implemented through the Speech SDK , which returns intermediate recognition and translation results as speech is detected. That streaming behavior is materially better suited to live conversations than a workflow that first transcribes audio and then separately calls a text-only translation API.
Microsoft specifically positions Speech Translation for low-latency, real-time speech-to-text and speech-to- speech translation scenarios.
Azure AI Translator translates text and therefore would require a separate speech-to-text stage before translation. Azure AI Language provides NLP capabilities such as classification, sentiment, and entity extraction rather than live speech translation. Azure AI Document Intelligence extracts structured information from documents and forms and is unrelated to streaming conversational audio.
Therefore, Azure AI Speech (Speech Translation) is the correct choice.
Study Guide references: Azure AI Speech # Speech Translation; real-time transcription and translation; Speech SDK; streaming audio translation; target-language text output.
NEW QUESTION # 83
......
Are you still worried about you exam? If you do, then trying the AI-200 exam torrent of us, we will make it easier for you to pass it successfully. AI-200 exam dumps of us are not only have the quality but also have certain quantity, it will be enough for you to deal with your exam. In addition AI-200 Online Test engine can record the process of your learning, and you can have a review of what you have learned. AI-200 Soft test engine stimulates the real environment of the exam, and you can know what the real exam looks like through this version.
New AI-200 Study Guide: https://www.validexam.com/AI-200-latest-dumps.html