Microsoft Certified: Azure AI Cloud Developer Associate practice questions
Microsoft · AI-200 · 200 questions
Original practice questions for Microsoft Certified: Azure AI Cloud Developer Associate.
This course contains the use of artificial intelligence.
About the AI-200 exam
- Time allowed
- 2 hours
- Languages
- English
- Format
- Proctored, may include interactive components; Pearson VUE
Schedule this exam The certification this earns
Exam details published by the vendor, checked 25 August 2026. Vendors change fees and formats without notice — confirm on the vendor's own page before you book.
Practice Quizzes
Test your knowledge with standard 20-question practice sets.
Quiz 1
Quiz 2
Quiz 3
Quiz 4
Quiz 5
Quiz 6
Quiz 7
Quiz 8
Quiz 9
Quiz 10
Browse by Domain
Study specific topics at your own pace.
Develop containerized solutions on Azure (20–25%) · 45 questions
- A city permits team packages a generative FAQ API as a container and needs a private registry to store versioned images for promotion across environments. Which Azure service should they use?
- A county 311 team wants immutable image tags for a resident chatbot backend so rollbacks use a known-good digest rather than a floating tag. What practice should they follow in Azure Container Registry?
- A public-health clinic assistant image must stay close to regional App Service deployments across the state. How should the team place the images in Azure Container Registry?
- Library chatbot maintainers need continuous integration to build the container image inside Azure rather than pushing only from developer laptops. Which capability should they use?
- Transit operations wants a scheduled rebuild of the service-alert agent image whenever the base Python image is patched. Which approach fits Azure Container Registry?
- A water-utility RAG API runs as a container on Azure App Service. How should connection strings be supplied without baking secrets into the image?
- A housing authority deploys a containerized document-summarizer to Azure App Service. What must they configure correctly for the container to serve traffic?
- A courts clerk assistant runs in App Service containers. Staging should use different Key Vault secret references than production. What should the team do?
- Parks department needs to test a new generative itinerary agent at low traffic before full cutover. Which Azure Container Apps feature should they use?
- An emergency-management briefing agent on Azure Container Apps must share networking and logging with related municipal workloads. What construct should they configure?
- A city open-data Q&A service on Azure Container Apps should avoid paying for idle replicas overnight when resident traffic drops. Which scaling behavior should they apply?
- A 311 ticket-triage worker on Azure Container Apps should scale based on Service Bus queue depth. Which scaling approach should the team implement?
- Public works wants event-driven scale for a permitting chatbot API during Monday morning peaks on Azure Container Apps. Which KEDA-oriented approach fits?
- Transit ETA agent microservices need internal cluster traffic on Azure Kubernetes Service. What should the team deploy?
- A county AI gateway on AKS needs non-secret model endpoint URLs and secret API keys. How should those values be supplied in manifests?
- A library bot on AKS should not receive traffic until its model client is warm. Which probe configuration addresses that requirement?
- A city GIS narrative agent on AKS must add pods during map-season CPU spikes. Which Kubernetes construct should they apply?
- Housing RAG indexer pods on AKS fail intermittently. What should ops inspect first to diagnose the failures?
- A Container Apps revision of a clerk summarizer returns HTTP 502. What should the team inspect to troubleshoot?
- End-to-end connectivity from Application Gateway to AKS AI ingress fails after a network change. What should the municipal team do?
- A city wants to control Azure Container Registry cost for a permit-bot by pruning untagged images older than 30 days. Which feature should they configure?
- A county requires assurance that production App Service pulls only trusted generative API images from Azure Container Registry. What should they emphasize?
- A public-health agent container must pull from Azure Container Registry without sharing admin registry passwords. What authentication approach should the host use?
- A city wants the 311 classifier image rebuilt and pushed whenever code merges to main. Which ACR capability should they configure?
- A municipal generative API on Azure App Service needs an OpenTelemetry sidecar beside the main container. Which hosting approach supports that layout?
- A city permits chatbot on Azure Container Apps must bind Key Vault secret values into the revision environment without baking credentials into the image. What should the team configure?
- A county clerk summarizer on Container Apps needs a blue-green style rollout that sends only 10% of resident traffic to a new revision. Which approach should ops use?
- A municipal dead-letter replay worker on Container Apps should scale with KEDA only when Service Bus dead-letter queue depth exceeds a set threshold. What should the team configure?
- A city AKS cluster hosts both parks and transit generative workloads. How should the platform team isolate departments and control resource use?
- A public 311 chat API on AKS must be exposed with TLS termination at the ingress controller. What should the municipal team implement?
- County AI ops run GPU-less embedding workers and separate CPU-bound RAG APIs on AKS and need cost-aware placement. What should they do?
- A library knowledge base needs a nightly corpus re-embed that should not run as a long-lived HTTP service. Which Container Apps capability fits?
- A low-traffic courts FAQ container on Azure App Service must avoid cold starts during hearing days. Which setting should the team enable?
- A housing agent Deployment on AKS shows ImagePullBackOff after a registry change. What is the most appropriate first remediation focus?
- A city needs a simple single-service permits chatbot with event-driven scale and prefers managed revisions over operating a full Kubernetes control plane. Which hosting choice fits best?
- An emergency-alert paraphraser API is bursty and benefits from scale-to-zero between incidents. Comparing App Service Linux containers and Container Apps, what is the better default for that pattern?
- A statewide health-assistant image must be available close to several regional App Service deployments. What ACR topology should the municipal cloud team prefer?
- A bad Container Apps deploy of a clerk redaction API is hurting production. What should the municipal team do to restore service quickly?
- Transit ops must upgrade the disruption-narrator Deployment on AKS with zero downtime for riders. Which strategy should they use?
- Elevated latency appears in a 311 intent API on Container Apps. What should the team collect first to diagnose?
- A work-order AI triage worker on Container Apps scales with KEDA against Service Bus, but the scaler cannot read queue metrics. What should the team validate?
- Parks recommender API builds must be reproducible when ACR Tasks rebuilds from a Dockerfile. What practice should the team follow?
- A containerized RAG query API on Azure App Service should be removed from the load balancer when it is unhealthy. What should the team configure?
- A municipal Container Apps revision for a permitting assistant keeps restarting. Logs show the model endpoint environment variable is missing. What should ops do?
- An internal embedding service on AKS must accept calls only from approved municipal namespaces. Which control should the platform team apply?
Develop AI solutions by using Azure data management services (25–30%) · 55 questions
- A city RAG store keeps ordinance chunk embeddings in Azure Cosmos DB for NoSQL for the permits bot. How should the back end retrieve nearest neighbors?
- County 311 knowledge items in Cosmos DB experience hot partitions around popular resident topics. What should the data design prioritize?
- A public-health FAQ assistant must look up grounding documents in Cosmos DB for NoSQL from its Azure back end. What is the appropriate access approach?
- A courts exhibit-metadata store in Cosmos DB needs lower RU cost for queries filtering on caseType and filedDate. What should the team optimize?
- A housing assistant needs consistent reads across a resident’s multi-turn retrieval session without paying for strong consistency on every regional operation. Which Cosmos consistency choice fits best?
- A transit agency stores alert embeddings in Cosmos DB for NoSQL and must meet semantic retrieval SLAs for the rider-info bot. What should the team configure?
- A library open-data bot needs grounded answers from Cosmos DB items that include both chunk text and embeddings. How should each item be modeled?
- Whenever permitting rules documents change in Cosmos DB, a search projection used by the city permits assistant must refresh. Which approach fits?
- Emergency management SOPs stored in Cosmos DB must be re-embedded when they are updated so the ops assistant stays current. What should drive the refresh?
- A parks FAQ generative workload hits Cosmos DB 429 responses during seasonal tourism spikes. What should the team do?
- An ordinance assistant already knows the id and partition key of a chunk it must load, while admins sometimes run ad hoc cross-partition searches. Which access pattern should the service prefer for the known chunk?
- A 311 agent stores short-lived conversation memory in Cosmos DB alongside long-lived knowledge chunks. How should TTL be applied?
- An assessor’s RAG assistant must join parcel attributes to embedding rows in Azure Database for PostgreSQL. What schema approach fits?
- A city complaint assistant stores embeddings with the pgvector extension in Azure Database for PostgreSQL. What must align for correct similarity search?
- County IT must support vector index builds on a large code-enforcement corpus in Azure Database for PostgreSQL. What should sizing prioritize?
- A housing casework assistant uses pgvector in Azure Database for PostgreSQL but must limit results by district and case status. What pattern should it use?
- A Container Apps RAG API calling Azure Database for PostgreSQL shows high connection latency under load. What should the team apply?
- A municipal code-search service on Azure Database for PostgreSQL filters by foreign keys and ranks by vector similarity. How should indexes be designed?
- Python civic services must query Azure Database for PostgreSQL under load for a permitting RAG back end. What is the appropriate approach?
- An active-permits chatbot queries Azure Database for PostgreSQL mostly against non-archived rows. How can indexing cut latency?
- A city wants to cut token spend on repeated 311 FAQ answers. Which Azure Managed Redis use fits?
- Ordinance answers cached in Azure Managed Redis become stale when the prompt or model version changes. What should cache keys include?
- Transit disruption summaries in Azure Managed Redis change quickly during incidents. Which expiration approach fits?
- A lightweight parks recommender needs fast nearest-neighbor lookup. How can Azure Managed Redis help?
- Clerk form-help snippets are generated by an LLM and reused through Azure Managed Redis. Which caching pattern is typically preferred for this side data?
- Top resident questions in Cosmos DB should warm an Azure Managed Redis cache used by the 311 assistant. What integration pattern fits?
- A municipal code-search assistant must apply keyword filters then rank by semantic similarity across Azure data services. What approach fits?
- An agent tool layer nearly stored raw API keys inside Cosmos DB documents used for municipal workflows. What should the team do instead?
- A city must re-embed outdated rows when the embedding model changes. What should be stored with each vector?
- Historical meeting-minute chunks must be loaded into Cosmos DB for AI retrieval at city scale. What ingest approach fits?
- After a large parks program corpus is loaded into Azure Database for PostgreSQL with pgvector, vector query plans degrade. What maintenance step should the city take?
- Azure Managed Redis filling with seasonal event Q&A cache entries risks out-of-memory errors for the city FAQ bot. Which eviction approach fits?
- A statewide emergency FAQ assistant needs high availability for Cosmos DB writes, but cost still matters. What tradeoff should the architect evaluate?
- Civic staff admin tools query Cosmos DB for NoSQL using filters from UI fields. How should those queries be written?
- A city AI platform stores bulky ordinance PDFs and high-churn embedding items in Cosmos DB. How should containers be designed?
- A multi-department RAG app on Azure Database for PostgreSQL must keep HR-adjacent public-records rows scoped by department. What approach fits?
- A permitting RAG query on Azure Database for PostgreSQL should avoid computing vector distance across the entire corpus. What should the service do first?
- Multiple RAG indexer instances across environments process a Cosmos DB change feed for permitting rules. How should leases be handled?
- Many 311 API pods miss Azure Managed Redis simultaneously during an outage recovery. What problem should the team prevent?
- A parks RAG design wants a Redis vector index for speed but durable full chunk text elsewhere. What split fits Azure data services?
- A shared city AI platform in Cosmos DB must partition by city, department, and document type together. What feature helps?
- After changing PostgreSQL pgvector lists/probes-style settings for a code-enforcement corpus, what should county IT measure?
- A reprocessing job may embed the same ordinance version more than once. How should writes be handled?
- Citywide semantic cache traffic on Azure Managed Redis exceeds a single-node comfort zone. What should the platform team evaluate?
- Structured permit fields must remain the system of record while also feeding RAG. Which data-service choice fits?
- Withdrawn public comments must stop appearing in RAG without hard-deleting audit history in PostgreSQL. What model fits?
- A multi-tenant civic Cosmos DB AI store must understand which department partitions consume the most RU. What should ops monitor?
- Azure Functions repeatedly look up the same RAG metadata shapes in Azure Database for PostgreSQL. How can throughput improve?
- A municipal agent caches structured tool-step results in Azure Managed Redis. Which data-structure approach fits?
- After an embedding model upgrade, some Cosmos DB ordinance items still have null vector fields. What job should run?
- An emergency agent must read SOP chunks that were just written to Cosmos DB. Which consistency concern applies?
- Azure Database for PostgreSQL stores large binary attachments beside searchable municipal text used for RAG. How should indexing treat those binaries?
- Chatty RAG clients threaten the shared Cosmos DB RU budget during council-meeting nights. What client-side protection fits?
- Before inserting into a pgvector column for a municipal corpus, what must the pipeline validate?
- Cold meeting transcripts should leave Azure Managed Redis while hot FAQ vectors stay warm. What tiering approach fits?
Connect to and consume Azure services (20–25%) · 50 questions
- A city permits API must accept large document-summarization jobs without making residents wait on the HTTP response. Which Azure messaging pattern should the back end use?
- A 311 triage publisher must route the same incident message so housing and public-works AI workers each receive only their category. What Service Bus feature fits?
- RAG re-index messages keep failing after poison payloads reach the city’s embedding worker. Where should those failed Service Bus messages go for investigation?
- A clerk portal sometimes retries the same AI job submit, risking double token spend. How should Service Bus protect the city’s summarization queue?
- A resident chatbot must keep multi-step agent tool calls ordered for one conversation. Which Service Bus capability enforces that ordering?
- Container Apps workers summarizing permit packets are thrashing on lock expirations. What Service Bus consumer tuning should the city apply?
- The library wants bulk re-embed jobs to start overnight without staff starting workers at midnight. How should Service Bus schedule that work?
- When a new ordinance PDF lands in Blob Storage, the city’s RAG indexer should start without polling. Which integration should they use?
- Emergency management requires a human approval signal before publish agents distribute an alert draft. What Event Grid approach fits?
- Only application/pdf blob creations should invoke the city’s OCR-to-embed Function. How should Event Grid be configured?
- A flaky enrichment endpoint drops intermittent Event Grid deliveries for permit metadata. What reliability configuration should the city apply?
- The same ordinance-published event must update analytics logging and invalidate a live agent cache. What Event Grid pattern should the city use?
- Parks chatbot tools need a lightweight internal HTTP API for lookup actions. Which Azure Functions trigger should host that API?
- Staff upload new SOP PDFs that must be chunked for RAG automatically. Which Functions trigger starts that work on upload?
- Code-enforcement summary jobs sit on a Service Bus–backed work queue. How should Azure Functions consume that work?
- When FAQ items change in Cosmos DB, the city’s Redis cache for the resident assistant must refresh. Which Functions approach fits?
- Nightly, the city must find stale embeddings and enqueue re-embed messages. Which Functions trigger schedules that maintenance?
- A permits enrichment Function should write outputs to Blob Storage and enqueue follow-up work with minimal SDK boilerplate. What should developers use?
- The city must stage a new agent-tool Function API before residents hit it. Which deployment practice reduces release risk?
- Long RAG enrichment jobs exceed default Consumption timeouts for the city’s Function app. What hosting decision fits?
- A Function must send to Service Bus without storing a connection string in app settings. What authentication approach should the city use?
- A Function repeatedly fails on a corrupt permit PDF from the queue. What poison-message strategy should operators follow?
- Courts IT creates a new custom Event Grid topic and webhook endpoint for workflow events. What must the endpoint handle during subscription setup?
- A failed agent step must be traced from a Service Bus message through Application Insights. What correlation practice should developers apply?
- A Service Bus topic must route only “public-health” intents to the clinic assistant worker. Which feature implements that rule?
- Event Grid delivers the same blob-upload event twice to the city’s summarizer Function. How should the Function stay idempotent?
- Embedding workers for the library SOP corpus need higher Service Bus throughput without raising lock thrash. What receive pattern helps?
- Summarizer Function deliveries keep landing in Event Grid’s failure destination after repeated errors. What should ops investigate first?
- Permit packet generation needs multi-step generative work with checkpoints and retries across hours. Which Functions approach fits best?
- An internal civic agent calls HTTP-triggered tool Functions. Which auth approach best fits machine-to-machine calls inside the city tenant?
- Thousands of 311 events flood Event Grid during a storm surge into AI triage. What capacity planning concern matters most?
- A Service Bus transaction cannot undo model tokens already spent on a failed civic enrichment. What design lesson applies?
- High-volume water-meter alert paraphrasing needs more Service Bus throughput than a single non-partitioned queue provides. What helps?
- Blob-created events from Azure Storage should start RAG indexing without polling. Which Event Grid topic type is the natural fit?
- An embedding Function app must load connection settings and secrets without hardcoding them in code. What configuration practice fits?
- Clerk desk tools hosted on Azure Functions suffer cold-start delays that frustrate staff. What hosting mitigation fits latency-sensitive tools?
- A legacy city webhook posts nonstandard JSON that AI workflows need on Event Grid. How should Azure Functions help?
- Multiple Function instances must process redaction jobs from one Service Bus queue safely. Which pattern applies?
- After a housing case row commits, an agent follow-up message must not be lost if the process crashes mid-flight. What pattern helps?
- Only blob subjects under /permits/ should wake the AI classifier subscription. How should Event Grid be scoped?
- Sensitive resident-notice drafts must wait for human review before the distribution agent runs. Which Service Bus feature fits?
- A public parks FAQ site calls an Azure Function HTTP API. What exposure practice is appropriate?
- Poison/dead-letter queue depth for document AI jobs is climbing. What operational response fits?
- Parallel enrichment Functions must finish before the city enqueues the final summary job. What coordination pattern fits?
- A simple fire-and-forget park photo caption job needs a basic queue. For AI-200 messaging skills, which service is the primary exam focus?
- After a Function outage, Event Grid retries create a retry storm into the city’s AI handler. What mitigation helps?
- Ephemeral agent-session work queues should disappear after idle timeout. Which Service Bus lifecycle setting helps?
- A grounded-answer Function should persist audit rows to Cosmos DB with minimal custom SDK plumbing. What helps?
- Functions that call internal RAG data services must avoid public internet exposure of those stores. What networking approach fits?
- Agent tool schemas still call /api/v1/tools while a new Function API is ready. How should routes be versioned safely?
Secure, monitor, troubleshoot Azure solutions (20–25%) · 50 questions
- A city Container App must load model API keys at runtime without baking them into the image. What should the team use?
- The RAG indexer Function’s shared service principal secret must rotate on a schedule without downtime. Which approach fits?
- Only the permits API identity should read the Cosmos key secret in Key Vault. What control enforces that?
- Production agent credentials live in Key Vault and must survive accidental deletion. Which protection should be enabled?
- An App Service hosting the clerk assistant should resolve secrets without copying values into app settings. What pattern should be used?
- The city wants to enable a new summarizer prompt version citywide without redeploying every service. Where should the toggle live?
- Non-secret model endpoints and temperature defaults for all 311 AI services should be centralized. Which service fits?
- Clerk assistant settings must differ between staging and production without separate key names for every value. What App Configuration feature helps?
- Parks bots must pick up new content-safety thresholds without redeploying containers. What capability is required?
- During an incident, outbound agent tools for the resident assistant must be disabled quickly. What control fits?
- Ops must follow one resident request across the API gateway, an Azure Function, and Cosmos DB. What should they implement?
- Trace context from the public chat UI must continue into Service Bus consumers that finish the work. What is required?
- Latency must be broken down across embedding, retrieval, and generation for the housing RAG path. How should instrumentation look?
- Container Apps running the transit assistant must send traces into Azure Monitor for analysis. What should the team configure?
- Council-night traffic spikes flood traces for the meeting assistant, but errors must still be captured. Which approach fits?
- During an outage, analysts must find Function failures tied to one Cosmos partition for the health records assistant. What should they use?
- Leaders need p95 latency of the permits chatbot API by Container Apps revision. Which technique applies?
- Ops suspect Cosmos RU exhaustion on the knowledge store after seeing client errors. What should a KQL investigation look for?
- Dead-letter count on the summarization queue must page on-call when it exceeds a threshold. How should that be implemented?
- A hard-to-reproduce agent bug needs Application Insights requests joined to container stdout. What correlation key should ops use?
- Staging identities must not read production secrets for the courts assistant. What Key Vault design fits?
- Internal agent-tool services need mutual TLS using a certificate the city manages centrally. Where should the certificate live?
- The transit RAG API needs both model temperature defaults and database connection secrets. How should they be split?
- After Key Vault rotation, the embedding worker fails with authorization errors. What is the most likely fix path?
- Diagnostics need a non-PII department id on traces for the multi-department resident portal. What OpenTelemetry mechanism fits?
- A city's 311 Container Apps revision starts returning errors after deploy. What KQL approach best diagnoses the bad revision?
- A parks permitting API emits custom token-count metrics. How should ops monitor generative cost proxies?
- A transit AKS cluster must retrieve secrets without exposing Key Vault to the public internet. What should the city implement?
- Staging App Configuration for a clerk RAG assistant is verified. How should settings move to production safely?
- After tuning KEDA for a housing caseworker queue, how should the team verify queue latency improved?
- Event Grid–triggered Functions for emergency notifications show intermittent failures. What should KQL highlight first?
- Court e-filing integration keys in Key Vault are approaching expiration. What operational practice should the clerk AI team follow?
- A water-utility agent pipeline uses Service Bus. How should send and receive be traced with OpenTelemetry?
- A civic RAG API intermittently fails talking to Azure Database for PostgreSQL. What should a KQL query surface?
- Internal agent services read App Configuration. How should the city harden networking?
- A permitting agent fails on secret get. How should ops correlate the failure?
- City AI microservices emit traces with inconsistent naming. What OpenTelemetry practice should leadership standardize?
- Production AI logs may contain case metadata. Who should be allowed to run KQL against that workspace?
- A new tool endpoint for library holds will roll out gradually. How should App Configuration and monitoring work together?
- Traces break between Azure Functions and Container Apps in a multi-hop civic agent path. What should the team investigate?
- After a deploy, managed identities for a housing AI API fail Key Vault gets. What alert should ops configure?
- Departments need different model deployment names without redeploying code. Where should those names live?
- Service Bus dead-letters pile up for a grants-processing AI job. How should KQL help?
- Resident PII sometimes appears in custom log dimensions. What balance should the city strike?
- Ops wants a health view for a multi-service permitting AI back end. What should the dashboard emphasize?
- A multi-agent workflow outage spanned messaging and Functions. How should post-incident analysis use KQL?
- A compromised secret version was disabled. How should the parks AI app retrieve secrets afterward?
- Citywide AI platforms depend on App Configuration reads. What availability consideration applies?
- AI workers consume Service Bus jobs for inspections. Which OpenTelemetry metrics help ops most?
- Embedding dimension mismatches start failing vector upserts citywide. How should KQL help find the pattern?
These questions are original practice material and are NOT actual exam questions or brain-dump content. Microsoft and related marks are trademarks of their respective owners. This material is not affiliated with, endorsed by, or sponsored by Microsoft.