AI-200 — Microsoft Azure AI Cloud Developer Associate Quick Review

Quick Review purpose

This Quick Review is for candidates preparing for Microsoft Azure AI Cloud Developer Associate (AI-200), exam code AI-200. Use it as a fast, practical review before working through topic drills, mock exams, and detailed explanations in an IT Mastery question bank.

The goal is not to replace hands-on Azure work. The goal is to help you quickly recognize the major design choices, implementation patterns, traps, and troubleshooting signals that commonly appear in Azure AI developer scenarios.

Exam identity

How to use this Quick Review

1. Scan the decision tables first. AI developer exams often test whether you choose the right Azure AI service and integration pattern.
2. Review the traps. Many misses come from confusing similar services, authentication methods, indexing concepts, or generative AI terms.
3. Practice immediately after each section. Use topic drills to confirm that you can apply the idea under exam-style wording.
4. Read explanations even for correct answers. Detailed explanations help you notice distractors, missing requirements, and better service choices.
5. Finish with mixed mock exams. The real challenge is switching contexts quickly across AI Search, Azure OpenAI, Language, Vision, Speech, Document Intelligence, security, and deployment scenarios.

High-yield domain map

Service selection quick table

Azure OpenAI review

Core concepts to recognize

RAG decision path

    flowchart TD
	    A[User asks a question] --> B{Need private or current knowledge?}
	    B -- No --> C[Prompt model with instructions]
	    B -- Yes --> D[Retrieve relevant content]
	    D --> E[Use Azure AI Search or another retrieval layer]
	    E --> F[Add retrieved passages to prompt]
	    F --> G[Generate grounded answer]
	    G --> H{Need citations or auditability?}
	    H -- Yes --> I[Return sources and confidence cues]
	    H -- No --> J[Return concise answer]

RAG implementation checklist

Prompt design review

Strong prompts usually include:

• Role or task: “You are an assistant that answers from provided policy excerpts.”
• Boundaries: “If the answer is not in the provided context, say you do not know.”
• Output format: JSON, table, bullet list, short paragraph, or classification label.
• Grounding rules: Use only retrieved content when required.
• Safety rules: Avoid restricted content, unsafe advice, or sensitive data exposure.
• Examples: Few-shot examples for formatting or classification consistency.

Weak prompts often:

• Ask for broad expertise without source boundaries.
• Mix several tasks without ordering them.
• Fail to specify output format.
• Trust the model to infer compliance, privacy, or security rules.
• Include user-controlled content in a way that enables prompt injection.

Generative AI traps

Azure AI Search review

Core objects

Search pattern comparison

AI Search implementation traps

• Mark fields correctly for searchable, filterable, sortable, facetable, and retrievable behavior.
• Do not expect to filter on a field that was not configured for filtering.
• Do not expose documents from unauthorized tenants; implement security trimming.
• Do not assume indexers support every source or transformation requirement.
• Use skillsets when enrichment is needed during indexing.
• Validate chunking and retrieval quality with realistic user questions.
• Monitor index freshness if source documents change frequently.
• Use metadata such as source URI, title, document type, timestamp, tenant, department, and permissions.

Azure AI Language review

Language service decision rules

• Use prebuilt capabilities when the requirement matches standard NLP tasks.
• Use custom classification or extraction when labels/entities are domain-specific.
• Use Azure OpenAI when the requirement is open-ended generation, reasoning over context, or flexible summarization.
• Use AI Search + Azure OpenAI when answers must be grounded in a large private corpus.
• For production extraction, plan for evaluation data, confidence thresholds, review queues, and error handling.

Vision and OCR review

Vision traps

• OCR extracts text; it does not automatically understand business meaning.
• Object detection locates objects; classification labels an image.
• Custom models require representative labeled data.
• Image quality, resolution, orientation, and handwriting affect accuracy.
• If the requirement includes tables, key-value pairs, or form fields, consider Document Intelligence instead of generic OCR.

Document Intelligence review

Prebuilt vs custom decision

Document extraction workflow

1. Receive document from an approved source.
2. Validate file type, size, and quality.
3. Select prebuilt, custom, or layout model.
4. Extract fields, tables, and confidence values.
5. Validate required fields and business rules.
6. Send low-confidence or high-risk cases to review.
7. Store extracted data with source traceability.
8. Monitor accuracy by document type and version.

Document Intelligence traps

• Do not choose generic OCR when the requirement asks for named fields from forms.
• Do not assume one custom model works for unrelated document layouts.
• Do not ignore confidence scores.
• Do not train on ideal samples only; include realistic variation.
• Do not skip downstream validation just because extraction succeeded.

Speech review

Speech traps

• Speech-to-text produces transcripts; it does not automatically summarize or classify unless combined with another service.
• Background noise and microphone quality affect recognition.
• Real-time scenarios prioritize latency; batch scenarios can prioritize completeness.
• Text-to-speech voice selection affects user experience but not text correctness.
• Translation, transcription, and conversational understanding are separate tasks.

Bot and conversational app review

Conversational design rules

• Use the model for natural language understanding and generation, not for unchecked business authority.
• Store durable state in application storage where required.
• Validate user identity before retrieving private data.
• Apply security trimming before retrieved content reaches the prompt.
• Use structured tool/function calls for actions such as ticket creation, lookup, or transaction submission.
• Log enough context to troubleshoot without exposing sensitive information unnecessarily.

Security and identity review

Authentication and authorization

Key security reminders

• Prefer Microsoft Entra ID and managed identities over static keys when supported.
• If keys are used, store them securely and rotate them.
• Keep secrets out of code, prompts, config files, and logs.
• Apply least privilege to data stores, search indexes, AI services, and monitoring systems.
• Treat prompts and model outputs as data that may contain sensitive information.
• Implement tenant isolation and document-level access checks for multi-user RAG apps.
• Validate all model-suggested actions before execution.

Responsible AI review

Responsible AI traps

• Safety filtering is not a complete responsible AI program.
• Grounded generation can still produce wrong synthesis if retrieval is poor.
• Human review should be targeted to risk, uncertainty, or business impact.
• Evaluation should include adversarial, ambiguous, and out-of-scope prompts.
• Prompt injection can come from users, documents, web pages, or tool outputs.
• Do not expose chain-of-thought-style hidden reasoning; provide concise explanations or sources instead.

Application integration review

Common architecture patterns

API and SDK reminders

• Know whether the scenario is asking for management-plane work, such as provisioning resources, or data-plane work, such as calling a model or analyzing a document.
• Handle transient failures with retries and backoff.
• Use regional endpoints and deployment names correctly.
• Do not expose service keys in client-side code.
• Validate request size, supported file formats, and rate/throughput limits in design scenarios.
• Use structured outputs when downstream systems need reliable parsing.
• Log correlation IDs and request metadata for troubleshooting.

Deployment and operations review

Troubleshooting signals

High-yield comparison: RAG vs fine-tuning vs prompt engineering

High-yield comparison: Azure AI Search vs database search

Common candidate mistakes

Service choice mistakes

• Choosing Azure OpenAI for every text problem, even when a prebuilt Language capability is simpler.
• Choosing generic OCR when the scenario requires structured field extraction from forms.
• Choosing fine-tuning when the requirement is current private knowledge.
• Choosing Speech services for conversation intelligence without adding language understanding or generative logic.
• Choosing AI Search when the task is transactional database lookup rather than relevance-based search.

Architecture mistakes

• Putting service keys in browser or mobile client code.
• Forgetting managed identity and least privilege.
• Building RAG without document-level authorization.
• Treating embeddings as a database replacement.
• Ignoring index field attributes needed for filters and facets.
• Sending too much irrelevant context to the model.
• Skipping human review for high-impact automated decisions.

Exam-reading mistakes

• Missing qualifiers like prebuilt, custom, real-time, batch, private data, least privilege, low latency, or structured output.
• Answering for the most advanced technology instead of the simplest service that satisfies the requirement.
• Confusing safety, security, and correctness.
• Ignoring whether the task is ingestion, retrieval, generation, deployment, or monitoring.
• Overlooking that the app, not the model, must enforce identity, authorization, and business rules.

Fast decision rules

Use these quick rules when you are stuck between similar answers:

1. Need enterprise Q&A over documents? Use RAG: Azure AI Search for retrieval plus Azure OpenAI for generation.
2. Need current facts? Retrieve them; do not rely on model training.
3. Need private data access control? Authenticate the user and security-trim before prompting.
4. Need structured form fields? Use Document Intelligence, not just OCR.
5. Need sentiment, entities, or key phrases? Use Azure AI Language prebuilt features unless the labels are custom.
6. Need image labels or object detection? Use Vision capabilities; use custom only for domain-specific recognition.
7. Need speech input or output? Use Speech services; combine with Language or Azure OpenAI for understanding and response generation.
8. Need secure app-to-service access? Prefer managed identity and RBAC where supported.
9. Need safer generative output? Combine grounding, safety filters, evaluation, and human review.
10. Need reliable downstream automation? Use structured outputs and validate before action.

Practice priorities for AI-200

Use IT Mastery practice to convert this review into exam readiness. Prioritize original practice questions in this order:

Final pre-practice checklist

Before starting a mock exam, make sure you can answer these without notes:

• Which service extracts structured fields from invoices or forms?
• Which pattern supports private document Q&A with source grounding?
• Why is RAG usually different from fine-tuning?
• What is the role of embeddings in vector search?
• What index field settings are needed for filtering, sorting, faceting, and retrieval?
• How do you prevent users from seeing unauthorized documents in a chatbot?
• When should you use prebuilt Language capabilities instead of Azure OpenAI?
• What is the difference between OCR and Document Intelligence extraction?
• How should an Azure-hosted app authenticate to AI services securely?
• What controls reduce hallucination, harmful output, and prompt injection?
• What should you inspect when answers are wrong but fluent?
• What should you inspect when an app works locally but fails after deployment?

Next step

After reviewing the tables above, move directly into AI-200 topic drills in an IT Mastery question bank. Start with service selection and RAG scenarios, then use mixed mock exams and detailed explanations to find weak areas before your final review.

Continue in IT Mastery

Use this Quick Review as a final concept map, then move into IT Mastery for focused topic drills, mixed practice sets, timed mock exams, and detailed explanations. The practice questions are original IT Mastery practice items; they are not official Microsoft questions, copied live-exam content, or exam dumps.