PDFExamDumps剛剛發布了最新的AI-200認證考試所有更新的問題及答案,來確保您考試成功通過。我們提供最新的PDF和軟件版本的問題和答案,可以保證考生的AI-200考試100%通過。在我們的網站上,您將獲得我們提供的Microsoft AI-200免費的PDF版本的DEMO試用,您會發現這絕對是最值得信賴的學習資料。對于擁有高命中率的Microsoft AI-200考古題,還在等什么,趕快下載最新的題庫資料來準備考試吧!
| Section | Objectives |
|---|---|
| Connect to and consume Azure services | - Integrate Azure services
|
| Develop containerized solutions on Azure | - Implement containerized applications
|
| Develop AI solutions by using Azure data management services | - Work with Azure data platforms for AI workloads
|
| Secure, monitor, troubleshoot Azure solutions | - Operate AI cloud solutions
|
當您對我們的Microsoft AI-200考古題感到滿意的時候,趕快購買吧,付款之后,無需等待,你可以立刻獲得你所購買的AI-200考古題。雖然我們的AI-200考古題通過率高達98%,但是我們有退款保證來保護客戶的利益,如果您的AI-200考試失敗了,我們退還你的購買費用,所有考生可以放心購買。選擇Microsoft AI-200考古題可以保證你可以在短時間內增強考試知識,并順利高分通過考試。
問題 #70
Drag and Drop Question
A recommendation system stores 3 million embeddings in Azure Database for PostgreSQL.
During peak hours, P95 similarity-query latency increases, and the cache hit ratio drops significantly.
You suspect that the vector index working set no longer fits in memory, resulting in more disk reads.
You need to scale server resources and validate the outcome.
Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.
答案:
解題說明:
Explanation:
Step 1: Before peak hours, run a fixed workload to capture baseline P95 latency and capture EXPLAIN ANALYZE for the vector query Establishing a baseline is crucial for performance tuning. Running EXPLAIN ANALYZE provides deep insight into whether the query is actually using the vector index (like HNSW or IVFFlat) or falling back to a slow sequential scan.
Step 2: Scale to a tier with more memory per vCore
Since the problem states that the vector index working set no longer fits in memory, scaling to a tier with higher memory (such as Memory-Optimized tiers) directly solves the root cause by allowing the RAM to fully cache the vector index, eliminating slow disk reads.
Step 3: Re-run the same benchmark and compare P95 and P99 latency
To validate the outcome of your scaling operations, you must run the identical benchmark workload and compare high-percentile latencies (P95, P99) against your baseline to prove the bottleneck was resolved.
Step 4: Review memory pressure and cache hit ratio during peak hours and compare them to the baseline This step confirms the success of the resource scaling. A successful remediation will show a significantly increased cache hit ratio and reduced memory pressure/disk I/O compared to the baseline metrics.
Reference:
https://www.pgedge.com/blog/ai-features-in-pgadmin-ai-insights-for-explain-plans
問題 #71
Case Study 2 - Proseware Inc.
Background
Proseware Inc. develops AI-powered knowledge management solutions for enterprise customers.
The company is modernizing its platform to support semantic search, intelligent document retrieval, and real-time partner integrations.
The engineering team uses Python and Azure SDKs. The architecture is being redesigned to support containerized microservices, vector search workloads, and serverless backend processing.
Planned Application Architecture
Microservices are containerized by using Docker.
Code for containerized microservices and Azure Function apps is developed locally but stored in a GitHub repository.
Custom images for containerized microservices are stored in Azure Container Registry (ACR).
Base images are stored in Docker Hub. Custom images must be rebuilt automatically whenever their base images are updated.
Azure Cosmos DB for NoSQL stores documents, metadata, and vector embeddings.
Azure Functions generate vector embeddings of Azure Cosmos DB for NoSQL-hosted documents and send messages to Service Bus to trigger search index updates.
Azure Container Apps (ACA) apps host backend API services that provide semantic search across Azure Cosmos DB for NoSQL documents. API services process Service Bus messages and update search indexes.
Azure Kubernetes Service (AKS) processes batch vector embedding regeneration for existing Azure Cosmos DB for NoSQL documents (whenever the embedding model is changed).
An extranet-facing containerized webhook allows business partners to submit documents to be processed by internal AI workflows for semantic search and retrieval.
Monitoring
Telemetry generated by Azure resources is sent to Azure Monitor.
A Log Analytics workspace is used to collect ACA apps logs, AKS container logs, and Azure Functions apps logs.
Monitoring of Azure Functions is currently implemented by using Azure Application Insights SDK instrumentation.
Business Requirements
Embeddings for new or updated Azure Cosmos DB for NoSQL-hosted documents must be automatically generated.
Backend API services must scale automatically during business hours.
Cold start delay of backend APIs must be minimized.
Secrets must be stored outside of container images.
Developers must be able to correlate telemetry across Azure Functions hosts and apps.
All tracing must be implemented by using OpenTelemetry SDK instrumentation.
Development efforts must be minimized.
Technical Requirements
Container images must be built automatically and validated before code updates are merged into the main branch.
Image build automation must run inside the Azure Container Registry, eliminating dependency on local developer machines and external build services.
Dependency of image builds on local developer machines must be eliminated.
Event-driven scaling in ACA must occur based on the number of pending messages in the Azure Service Bus queue.
Azure Cosmos DB for NoSQL RU consumption must be minimized.
Vector similarity search must use embeddings stored in Azure Cosmos DB for NoSQL.
The partner-facing containerized webhook service must run on Azure App Service.
Secrets must NOT be stored in container images, source control, or application configuration directly. They must be accessed securely at runtime.
All secrets must be stored centrally in Azure Key Vault and accessed at runtime through a managed identity.
Azure App Service must supply secrets at runtime without relying on external services.
Resources and workloads must be deployed by using Bicep templates through an automated, version-controlled pipeline. Local and command-line deployments must be eliminated to ensure repeatable, auditable deployments.
Known Issues
RU consumption spikes during vector similarity queries.
Hotspot Question
You need to configure vector embedding updates according to the business and technical requirements.
Which configurations should you use? To answer, select the appropriate options in the answer area.
NOTE: Each correct selection is worth one point.
答案:
解題說明:
Explanation:
Business Requirements: Embeddings for new or updated Azure Cosmos DB for NoSQL-hosted documents must be automatically generated.
Technical Requirements: Vector similarity search must use embeddings stored in Azure Cosmos DB for NoSQL.
Box 1: Change feed processor
The Change feed processor is the correct component to configure for identifying document changes that should trigger vectorization.
This feature in Azure Cosmos DB provides a reliable, distributed, and scalable way to listen to a constant stream of changes (inserts and updates) within a container. It allows you to process these modifications in real-time, making it the perfect trigger for automated workflows like sending new text to an embedding model.
Box 2: Lease Container
The lease container is the component you configure to coordinate and horizontally scale out the change feed-driven vectorization processing across multiple workers or compute instances.
The Lease Container acts as state storage, tracks checkpoints, and distributes partition keys across parallel compute workers (such as Azure Functions or custom change feed processors) to scale out throughput processing safely without duplicate work.
Incorrect:
RU Throughput: Dictates the maximum performance limit, but provisioning RUs alone does not orchestrate or scale out multiple processing workers.
Consistency Level: Affects data replication guarantees and read/write ordering, not parallel processing distribution.
Reference:
https://blog.nashtechglobal.com/managing-record-changes-with-change-feed-in-azure-cosmos-db/
問題 #72
You are developing an Azure Function that calls external APIs by providing an access token for the API. The access token is stored in a secret named token in an Azure Key Vault named mykeyvault.
You need to ensure the Azure Function can access the token. Which value should you store in the Azure Functions app configuration?
答案:D
問題 #73
You must ensure that PII (personally identifiable information) such as names and phone numbers is automatically redacted from support ticket transcripts before they are stored. What should you use?
答案:A
解題說明:
Azure AI Language's PII detection feature identifies and can redact categories of sensitive information (names, phone numbers, SSNs, etc.) from unstructured text, which is the purpose- built service for this scenario.
問題 #74
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.
答案:
解題說明:
Explanation:
* Service fails to communicate with another service: Inspect Kubernetes service endpoints.
* Pod restarts repeatedly: Inspect container logs.
* Readiness probe failures are observed: Inspect Pod descriptions.
For a service-to-service communication failure , first inspect the Kubernetes service endpoints . Microsoft' s AKS troubleshooting guidance recommends verifying that the destination pod IP address and application port appear as endpoints for the Kubernetes Service. An empty or incorrect endpoint list commonly indicates a selector/label mismatch, incorrect port configuration, or unavailable backend pods.
For a pod that restarts repeatedly , inspect the container logs , including the previous container instance when necessary. Microsoft specifically recommends kubectl logs < pod > --previous for workloads that repeatedly restart because it exposes application errors and termination messages from the container immediately before the restart.
For readiness probe failures , inspect the Pod description by using kubectl describe pod. The description exposes the configured health probes, pod conditions, container state, and associated probe-failure events, allowing you to determine whether the probe path, port, timing, or application readiness behavior is incorrect.
Microsoft recommends reviewing kubectl describe output when pods are not Ready or health probes are failing.
Therefore, the correct mapping is service endpoints # container logs # Pod descriptions .
Study Guide references: AKS troubleshooting; Kubernetes Services and endpoints; container logging; Pod health; readiness/liveness probes; kubectl describe and kubectl logs.
問題 #75
......
PDFExamDumps 能夠消除考生對考試失敗的憂慮;讓考生安心輕松通過 AI-200 考試,把考生通過考試當作自己的事情來對待,這是我們考題網對廣大考生最貼心的服務。考生需要是多做我們的 Microsoft AI-200 考古題,將特別需要記憶或比較的題型做標註,這不僅能檢測出自己理解的多,也能在 AI-200 考試前作最快速的瀏覽,增加內容的熟悉度,有效提高學習效率。
AI-200考證: https://www.pdfexamdumps.com/AI-200_valid-braindumps.html