examOS.
Exam CatalogueStudy PlansRoadmapsBlogs
Login

ExamOS

Credits PolicyReferral PolicyQuality StandardsPricingPrivacy PolicyTerms of UseContact UsReport a Bug

Follow us

Disclaimer: ExamOS is an independent platform, not affiliated with any certification provider, and does not use or distribute exam dumps.

Share your feedback

Checking sign-in status...

examOS.Study Plan
Disclaimer: ExamOS is an independent platform, not affiliated with any certification provider, and does not use or distribute exam dumps.
← Back to Exam Details
examOS.Study Plan · examos.io

Study Plan

Azure AI Cloud Developer (AI-200) Study Plan for 2026

AI-200 study plan covering containerized AI solutions, Azure data management services, service integration, and securing and monitoring AI workloads.

MicrosoftAI-200Passing score: 700 / 1000Developers with hands-on experience building and deploying applications on Azure, comfortable with Python, Azure SDKs, and containerized workloads14-Sep-202613 views
Start date: _______________Target exam date: _______________

Your personalized plan

A focused route built around your experience and daily study commitment.

Timeline

10 weeks

Personalized calendar

Daily commitment

1h

5 study & practice hrs/week

Progress

0/6

milestones completed

Saved on this device

Your week-by-week breakdown


Your week 1

Milestone 1: Containerized Solutions on Azure (Domain 1)

This week covers the container layer: building images, hosting containers, and orchestrating workloads at scale. Azure Container Apps is the primary hosting option. AKS is covered at the level required for manifest deployments and troubleshooting.

Topics

  • • Azure Container Registry: building, storing, versioning images
  • • ACR Tasks: automated image builds on commit or schedule
  • • Azure Container Apps: environment configuration, revision management
  • • KEDA event-driven autoscaling in Container Apps
  • • Azure Kubernetes Service (AKS): manifest deployments, monitoring, troubleshooting
  • • Containerizing AI workloads

Activities

  • • Build a Python application, containerize it, and push the image to Azure Container Registry. Verify the image appears in the registry.
  • • Create an ACR Task that rebuilds the image on a Git commit. Test with a sample commit.
  • • Deploy the containerized application to Azure Container Apps. Configure environment variables and a revision.
  • • Configure KEDA autoscaling in Container Apps based on a queue length trigger.
  • • Deploy the same application to AKS using a manifest file. Inspect logs and events to verify the deployment.
  • • Complete a Daily Sprint in Challenger mode on Domain 1. Repeat until you pass two consecutive sessions.

Your week 2

Milestone 2: Azure Data Management Services, Part 1: Cosmos DB and Vector Search (Domain 2)

This is the heaviest domain and the one with the most new content. Cosmos DB for NoSQL is the primary vector-enabled database. You need to understand how to store embeddings, run similarity searches, and optimize RU consumption.

Topics

  • • Cosmos DB for NoSQL: SDK connections, queries, indexing policies
  • • Consistency levels and their impact on performance and cost
  • • Vector similarity search: storing embeddings, querying for semantic retrieval
  • • RAG patterns with Cosmos DB: metadata filters, relevance ranking
  • • Change feed processor: detecting and handling new or updated items
  • • Optimizing RU consumption through indexing and query design

Activities

  • • Connect to a Cosmos DB for NoSQL account using the Python SDK. Insert documents and run a query.
  • • Configure an indexing policy that excludes a field from the index. Measure the RU difference on a query.
  • • Store vector embeddings in Cosmos DB. Run a vector similarity search and retrieve the top 5 results.
  • • Implement a RAG pattern: embed a query, search for relevant documents, filter by metadata, and return results.
  • • Implement a change feed processor that logs new items as they are inserted.
  • • Complete a Daily Sprint in Challenger mode on Domain 2 (Cosmos DB). Repeat until you pass two consecutive sessions.

Your week 3

Milestone 3: Azure Data Management Services, Part 2: PostgreSQL, Redis, and Blob Storage (Domain 2)

This week covers the rest of Domain 2: Azure Database for PostgreSQL with pgvector, Azure Managed Redis for caching, and Azure Blob Storage for unstructured data.

Topics

  • • Azure Database for PostgreSQL: pgvector extension, vector indexing
  • • Azure Managed Redis: caching patterns, session state, semantic cache
  • • Azure Blob Storage: storing documents, images, and model artifacts
  • • Blob lifecycle policies and tiering for cost optimization
  • • Integrating storage with AI workloads

Activities

  • • Enable the pgvector extension on an Azure Database for PostgreSQL instance. Store embeddings and run a similarity query.
  • • Configure Azure Managed Redis as a semantic cache for repeated queries. Measure the latency difference between cache hits and misses.
  • • Upload documents to Blob Storage and configure a lifecycle policy that moves blobs to Cool after 30 days.
  • • Build a Python script that retrieves a document from Blob Storage, extracts text, and passes it to a model.
  • • Complete a Daily Sprint in Challenger mode on Domain 2 (PostgreSQL and Redis). Repeat until you pass two consecutive sessions.

Your week 4

Milestone 4: Connect to and Consume Azure Services (Domain 3)

This domain covers how AI applications communicate: messaging for decoupling, serverless functions for event handling, and SDKs for service integration. The exam tests whether you can design event-driven architectures.

Topics

  • • Azure Service Bus: queues, topics, subscriptions, sessions
  • • Azure Event Grid: event routing, filtering, delivery
  • • Azure Functions: triggers, bindings, Durable Functions
  • • Azure SDKs and third-party SDKs for service integration
  • • Event-driven architecture patterns for AI workloads

Activities

  • • Create a Service Bus queue and a topic with a subscription. Send and receive messages using the Python SDK.
  • • Create an Event Grid subscription that routes Blob Storage events to a Function App.
  • • Build an Azure Function with a Service Bus trigger that processes messages and writes results to Cosmos DB.
  • • Build a Durable Function that orchestrates a multi-step AI pipeline: retrieve, process, store.
  • • Complete a Daily Sprint in Challenger mode on Domain 3. Repeat until you pass two consecutive sessions.

Your week 5

Milestone 5: Secure, Monitor, and Troubleshoot Azure Solutions (Domain 4)

This domain covers the operational layer: managing secrets, monitoring distributed AI systems, and troubleshooting failures. The exam tests whether you can design observability into an AI application from the start.

Topics

  • • Azure Key Vault: storing secrets, certificates, and keys
  • • Managed identity vs service principal for keyless authentication
  • • Azure App Configuration: feature flags, configuration management
  • • Azure Monitor: metrics, logs, alerts
  • • Application Insights: distributed tracing with OpenTelemetry
  • • KQL queries for logs and metrics analysis
  • • Troubleshooting container and database issues

Activities

  • • Store a database connection string in Key Vault. Retrieve it from a Python application using managed identity.
  • • Configure App Configuration with a feature flag that controls whether a new model version is used.
  • • Instrument an AI application with OpenTelemetry. Verify traces appear in Application Insights.
  • • Write a KQL query that filters Application Insights traces for failed requests in the last 24 hours.
  • • Configure an Azure Monitor alert on a container app's CPU usage exceeding 80%.
  • • Complete a Daily Sprint in Challenger mode on Domain 4. Repeat until you pass two consecutive sessions.

Your week 6

Milestone 6: Exam Simulation and Booking

Your final push. Consolidate all four domains. The AI-200 exam includes interactive lab components, so practice pacing across different question types.

Topics

  • • Full syllabus review across all four domains
  • • Cross-domain scenarios: container + vector data + messaging + monitoring
  • • Time management (120 minutes for 40-60 questions)
  • • Interactive lab component technique
  • • Distractor elimination for scenario-based questions

Activities

  • • Take the free official practice assessment if available. If not, take at least 3 Mock Exams in Legend mode.
  • • For every missed question, write one sentence explaining the architectural principle behind the correct answer.
  • • Build one end-to-end application that uses all four domains: a containerized API, vector search in Cosmos DB, Service Bus messaging, and Application Insights monitoring.
  • • Simulate real exam conditions once: no phone, no breaks, 120 minutes, same time of day as your scheduled exam.
  • • Book your exam when your readiness score is stable and above 80, with every domain covered.

Your weeks 7–10

Use this practice and review phase for mock exams, weak-topic revision, and reworking missed questions before exam day.

Stay consistent by setting a target date for this certification.

Set target

Week-by-Week Breakdown


W1

Week 1

Containerized Solutions on Azure (Domain 1)

This week covers the container layer: building images, hosting containers, and orchestrating workloads at scale. Azure Container Apps is the primary hosting option. AKS is covered at the level required for manifest deployments and troubleshooting.

Topics

  • Azure Container Registry: building, storing, versioning images
  • ACR Tasks: automated image builds on commit or schedule
  • Azure Container Apps: environment configuration, revision management
  • KEDA event-driven autoscaling in Container Apps
  • Azure Kubernetes Service (AKS): manifest deployments, monitoring, troubleshooting
  • Containerizing AI workloads

Daily Study Routine

Suggested 2–3 Hour Day

TimeActivity
15 minReview yesterday's missed questions. Identify whether the miss was a service-selection error or a configuration error.
30 minWork through Microsoft Learn modules for this week's topic.
45 minHands-on lab: build or modify a component of your end-to-end application.
30 minComplete a Daily Sprint or Mock Exam.

Activities

  • Build a Python application, containerize it, and push the image to Azure Container Registry. Verify the image appears in the registry.
  • Create an ACR Task that rebuilds the image on a Git commit. Test with a sample commit.
  • Deploy the containerized application to Azure Container Apps. Configure environment variables and a revision.
  • Configure KEDA autoscaling in Container Apps based on a queue length trigger.
  • Deploy the same application to AKS using a manifest file. Inspect logs and events to verify the deployment.
  • Complete a Daily Sprint in Challenger mode on Domain 1. Repeat until you pass two consecutive sessions.
W2

Week 2

Azure Data Management Services, Part 1: Cosmos DB and Vector Search (Domain 2)

This is the heaviest domain and the one with the most new content. Cosmos DB for NoSQL is the primary vector-enabled database. You need to understand how to store embeddings, run similarity searches, and optimize RU consumption.

Topics

  • Cosmos DB for NoSQL: SDK connections, queries, indexing policies
  • Consistency levels and their impact on performance and cost
  • Vector similarity search: storing embeddings, querying for semantic retrieval
  • RAG patterns with Cosmos DB: metadata filters, relevance ranking
  • Change feed processor: detecting and handling new or updated items
  • Optimizing RU consumption through indexing and query design

Activities

  • Connect to a Cosmos DB for NoSQL account using the Python SDK. Insert documents and run a query.
  • Configure an indexing policy that excludes a field from the index. Measure the RU difference on a query.
  • Store vector embeddings in Cosmos DB. Run a vector similarity search and retrieve the top 5 results.
  • Implement a RAG pattern: embed a query, search for relevant documents, filter by metadata, and return results.
  • Implement a change feed processor that logs new items as they are inserted.
  • Complete a Daily Sprint in Challenger mode on Domain 2 (Cosmos DB). Repeat until you pass two consecutive sessions.
W3

Week 3

Azure Data Management Services, Part 2: PostgreSQL, Redis, and Blob Storage (Domain 2)

This week covers the rest of Domain 2: Azure Database for PostgreSQL with pgvector, Azure Managed Redis for caching, and Azure Blob Storage for unstructured data.

Topics

  • Azure Database for PostgreSQL: pgvector extension, vector indexing
  • Azure Managed Redis: caching patterns, session state, semantic cache
  • Azure Blob Storage: storing documents, images, and model artifacts
  • Blob lifecycle policies and tiering for cost optimization
  • Integrating storage with AI workloads

Activities

  • Enable the pgvector extension on an Azure Database for PostgreSQL instance. Store embeddings and run a similarity query.
  • Configure Azure Managed Redis as a semantic cache for repeated queries. Measure the latency difference between cache hits and misses.
  • Upload documents to Blob Storage and configure a lifecycle policy that moves blobs to Cool after 30 days.
  • Build a Python script that retrieves a document from Blob Storage, extracts text, and passes it to a model.
  • Complete a Daily Sprint in Challenger mode on Domain 2 (PostgreSQL and Redis). Repeat until you pass two consecutive sessions.
W4

Week 4

Connect to and Consume Azure Services (Domain 3)

This domain covers how AI applications communicate: messaging for decoupling, serverless functions for event handling, and SDKs for service integration. The exam tests whether you can design event-driven architectures.

Topics

  • Azure Service Bus: queues, topics, subscriptions, sessions
  • Azure Event Grid: event routing, filtering, delivery
  • Azure Functions: triggers, bindings, Durable Functions
  • Azure SDKs and third-party SDKs for service integration
  • Event-driven architecture patterns for AI workloads

Activities

  • Create a Service Bus queue and a topic with a subscription. Send and receive messages using the Python SDK.
  • Create an Event Grid subscription that routes Blob Storage events to a Function App.
  • Build an Azure Function with a Service Bus trigger that processes messages and writes results to Cosmos DB.
  • Build a Durable Function that orchestrates a multi-step AI pipeline: retrieve, process, store.
  • Complete a Daily Sprint in Challenger mode on Domain 3. Repeat until you pass two consecutive sessions.
W5

Week 5

Secure, Monitor, and Troubleshoot Azure Solutions (Domain 4)

This domain covers the operational layer: managing secrets, monitoring distributed AI systems, and troubleshooting failures. The exam tests whether you can design observability into an AI application from the start.

Topics

  • Azure Key Vault: storing secrets, certificates, and keys
  • Managed identity vs service principal for keyless authentication
  • Azure App Configuration: feature flags, configuration management
  • Azure Monitor: metrics, logs, alerts
  • Application Insights: distributed tracing with OpenTelemetry
  • KQL queries for logs and metrics analysis
  • Troubleshooting container and database issues

Activities

  • Store a database connection string in Key Vault. Retrieve it from a Python application using managed identity.
  • Configure App Configuration with a feature flag that controls whether a new model version is used.
  • Instrument an AI application with OpenTelemetry. Verify traces appear in Application Insights.
  • Write a KQL query that filters Application Insights traces for failed requests in the last 24 hours.
  • Configure an Azure Monitor alert on a container app's CPU usage exceeding 80%.
  • Complete a Daily Sprint in Challenger mode on Domain 4. Repeat until you pass two consecutive sessions.
W6

Week 6

Exam Simulation and Booking

Your final push. Consolidate all four domains. The AI-200 exam includes interactive lab components, so practice pacing across different question types.

Topics

  • Full syllabus review across all four domains
  • Cross-domain scenarios: container + vector data + messaging + monitoring
  • Time management (120 minutes for 40-60 questions)
  • Interactive lab component technique
  • Distractor elimination for scenario-based questions

Activities

  • Take the free official practice assessment if available. If not, take at least 3 Mock Exams in Legend mode.
  • For every missed question, write one sentence explaining the architectural principle behind the correct answer.
  • Build one end-to-end application that uses all four domains: a containerized API, vector search in Cosmos DB, Service Bus messaging, and Application Insights monitoring.
  • Simulate real exam conditions once: no phone, no breaks, 120 minutes, same time of day as your scheduled exam.
  • Book your exam when your readiness score is stable and above 80, with every domain covered.

Overview

AI-200 replaced AZ-204 on July 31, 2026. The credential name changed, but so did the exam. AZ-204 tested general Azure development. AI-200 tests the infrastructure layer that AI applications run on: containers, vector-enabled databases, event-driven messaging, and observability.

This is not AZ-204 with an AI chapter. Roughly half the AZ-204 syllabus is gone, and the new content assumes you already know how to build AI application backends. The exam expects proficiency in Python, Azure SDKs, containerization, and vector databases from the first line of the audience profile.

Domain Weight
Develop containerized solutions on Azure 20-25%
Develop AI solutions by using Azure data management services 25-30%
Connect to and consume Azure services 20-25%
Secure, monitor, and troubleshoot Azure solutions 20-25%

The weighting is unusually flat. No domain falls below 20%, which means there is no section you can deprioritize and still pass comfortably. Domain 2 (data management) is the heaviest at 25-30% and carries the most new content for AZ-204 veterans.

Recommended experience: Hands-on experience building and deploying applications on Azure. Comfortable with Python programming. Familiarity with Azure SDKs, containerized applications, and data management services. This is an intermediate-level exam, not an entry point.

A note on prerequisites: There are no formal prerequisites. However, candidates without prior Azure development experience will find the container and messaging domains difficult. If you are new to Azure, build foundational experience before starting this plan.

Frequently Asked Questions (FAQ)

Do I need AZ-204 before AI-200?

No. AZ-204 retired on July 31, 2026. If you already passed AZ-204, your certification remains on your transcript but can no longer be renewed. AI-200 is the current credential for Azure developers who build AI application backends.

How long does it take to prepare for AI-200?

Six weeks for developers with hands-on Azure experience. Four weeks if you already hold AZ-204 or have strong experience with Azure Container Apps, Cosmos DB, and Service Bus. The new content is concentrated in vector search, RAG patterns, and AI-specific integration.

What is the difference between AI-200 and AI-103?

AI-103 (Azure AI Apps and Agents Developer) focuses on building AI agents and generative AI applications using Microsoft Foundry. AI-200 focuses on the infrastructure layer: containers, vector databases, messaging, and observability. AI-103 is about building the AI logic. AI-200 is about building the platform it runs on.

Do I need to know Python?

Yes. The exam assumes Python proficiency. You need to read and reason about Python code that uses Azure SDKs. You do not need to write production applications from scratch under exam pressure, but you need to be comfortable with SDK patterns.

What is the most important domain to study?

Develop AI solutions by using Azure data management services (25-30%) is the heaviest domain and carries the most new content. Vector search in Cosmos DB and pgvector in PostgreSQL are the highest-leverage topics. Do not skip the AI-specific data patterns.

Can I use Microsoft Learn during the exam?

Yes. All role-based exams, including AI-200, give you access to Microsoft Learn during the exam. A "Learn" button opens Microsoft Learn in a split-screen view. You can only access Microsoft Learn. Use it to confirm specific SDK parameters or service limits. Candidates who know the material well use it to verify edge cases. Candidates who rely on it consistently run out of time.

What are the interactive lab components?

The exam may include interactive components where you complete tasks in a simulated Azure environment. These test hands-on skills, not just knowledge recall. Use the exam sandbox to practice the interface before test day.

What are the most common ways people fail?

  • Confusing Cosmos DB consistency levels. The exam tests whether you can match a workload's consistency requirement to the right level. Session consistency is not the same as strong consistency.
  • Not understanding vector search indexing. Storing embeddings is easy. Indexing them for fast similarity search is where the configuration decisions live.
  • Skipping KEDA autoscaling. Container Apps autoscaling is tested. Know when to scale on queue length versus CPU.
  • Ignoring the data domain. At 25-30%, it is the heaviest domain. Candidates who focus only on containers and messaging miss the largest section.
  • Not practicing KQL. Domain 4 tests whether you can query logs and metrics. KQL is a specific skill, not a general one.

What are the three biggest preparation mistakes?

  1. Studying services in isolation. The exam tests how services work together. Build one application that uses containers, vector data, messaging, and monitoring. The integration patterns are the exam.
  2. Skipping the Python SDK practice. The exam expects you to read and reason about SDK code. Reading documentation is not the same as writing a script that connects to Cosmos DB and runs a query.
  3. Underestimating vector search. This is the biggest new content area for AZ-204 veterans. Spend extra time on embeddings, similarity search, and RAG patterns.

Is there a renewal option?

Yes. AI-200 is valid for 1 year. You can renew it for free by passing an online assessment on Microsoft Learn. The renewal assessment is shorter and focuses on what has changed since you certified.