Tag: Microsoft Certification

Agentic AI, AI, AI-103, Artificial Intelligence (AI), Azure AI, Generative AI, Microsoft Certification May 25, 2026

Configure an application to connect to a Foundry project (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Implement generative AI and agentic solutions (30–35%)
   --> Build generative applications by using Foundry
      --> Configure an application to connect to a Foundry project

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

Azure AI Foundry provides a centralized environment for developing, deploying, and managing AI applications and agentic solutions.

Applications that use generative AI models, agents, retrieval systems, or multimodal capabilities must connect securely and reliably to Foundry projects.

This topic is important for the AI-103: Develop AI Apps and Agents on Azure certification exam.

For the AI-103 exam, you should understand:

Azure AI Foundry projects
Application connectivity
Authentication methods
SDK configuration
Endpoint configuration
Deployment configuration
Managed identities
API keys
Environment variables
Network security
Role-based access control (RBAC)
Connecting to deployed models and agents
Configuration management
Monitoring and troubleshooting

What Is an Azure AI Foundry Project?

An Azure AI Foundry project is a centralized workspace used to:

Manage AI resources
Deploy models
Configure agents
Build workflows
Store evaluation assets
Monitor AI systems

Projects help organize AI development and operations.

Components of a Foundry Project

A Foundry project may include:

Model deployments
Agent configurations
Prompt flows
Evaluation datasets
Connections
Search resources
Storage resources
Monitoring tools

Why Applications Need Project Connectivity

Applications connect to Foundry projects to:

Access deployed models
Invoke agents
Perform retrieval operations
Execute workflows
Use AI services securely

Common Connection Scenarios

Applications commonly connect to:

Chat models
Embedding models
Multimodal models
Agent services
Prompt flow endpoints
Azure AI Search resources

Connection Architecture

Typical connectivity includes:

Application
Authentication layer
Foundry project endpoint
Model or agent deployment

SDK-Based Connectivity

Applications often use SDKs to:

Authenticate
Send prompts
Receive responses
Stream outputs
Manage workflows

SDKs simplify development.

API-Based Connectivity

Applications may also use:

REST APIs
HTTP endpoints
Direct service requests

Authentication Methods

Applications must authenticate securely.

Common methods include:

API keys
Managed identities
Azure Active Directory (Azure AD)
Keyless authentication

API Key Authentication

API keys are:

Simple to configure
Easy for development and testing

However, they require secure storage.

Managed Identity Authentication

Managed identities provide:

Secretless authentication
Improved security
Automatic credential management

Managed identity is recommended for production workloads.

Azure AD Authentication

Azure AD enables:

Enterprise identity management
Role-based access
Secure authentication workflows

Keyless Authentication

Keyless authentication reduces:

Credential exposure
Secret management overhead

Secure Credential Storage

Applications should avoid:

Hardcoded secrets
Plain-text credentials

Credentials should be stored securely.

Environment Variables

Environment variables commonly store:

API endpoints
Deployment names
Keys
Configuration settings

Configuration Files

Applications may use:

JSON configuration files
YAML files
Application settings

Endpoint Configuration

Applications must connect to the correct:

Foundry endpoint
Model deployment endpoint
Agent endpoint

Deployment Names

Applications typically reference:

Specific deployment names
Model identifiers
Agent identifiers

Connecting to Model Deployments

Applications may connect to:

Chat completion models
Embedding models
Code models
Multimodal models

Connecting to Agent Workflows

Applications may invoke agents that:

Use tools
Access memory
Execute workflows
Coordinate tasks

Connecting to Prompt Flows

Applications can invoke:

Prompt flow endpoints
Orchestrated workflows
Multi-step pipelines

Connecting to Azure AI Search

RAG applications often connect to:

Azure AI Search
Vector indexes
Semantic search pipelines

Role-Based Access Control (RBAC)

RBAC controls:

Resource permissions
Service access
Administrative privileges

Least Privilege Principle

Applications should receive:

Only required permissions
Minimal access rights

Private Networking

Organizations may secure connectivity using:

Private endpoints
Virtual networks
Network isolation

Firewall Configuration

Firewall rules may restrict:

Public access
Unauthorized IP ranges

Secure Communication

Applications should use:

HTTPS
Encrypted communication
Secure APIs

SDK Initialization

Applications typically initialize:

Client objects
Authentication providers
Connection settings

Client Configuration

Client configuration may include:

Endpoint URLs
API versions
Deployment names
Authentication credentials

Streaming Configuration

Applications may enable:

Streaming responses
Incremental output rendering

Retry Policies

Applications should implement:

Retry logic
Exponential backoff
Timeout handling

Error Handling

Applications should handle:

Authentication failures
Network issues
Rate limits
Invalid requests

Logging and Monitoring

Applications should log:

Requests
Responses
Failures
Latency metrics

Observability

Observability helps organizations:

Monitor usage
Diagnose issues
Improve reliability

Application Scalability

Applications should support:

High concurrency
Distributed workloads
Elastic scaling

Cost Considerations

Connection design impacts:

Token usage
API consumption
Search operations
Infrastructure costs

CI/CD Integration

Connection settings may be managed through:

Deployment pipelines
Infrastructure as code
Environment promotion

Development vs Production Environments

Organizations often separate:

Development
Testing
Staging
Production

Each environment may use different:

Endpoints
Credentials
Policies

Multi-Region Connectivity

Global applications may connect to:

Multiple regional deployments
Regional failover systems

High Availability

Applications should support:

Redundant deployments
Failover strategies
Resilient architecture

Governance Considerations

Organizations may enforce:

Access policies
Security baselines
Audit logging
Compliance requirements

Troubleshooting Connectivity Issues

Common issues include:

Invalid credentials
Incorrect endpoints
Missing RBAC permissions
Network restrictions
Deployment mismatches

Performance Optimization

Organizations should optimize:

Connection reuse
Latency
Request batching
Streaming efficiency

Real-World Scenario

Scenario: Enterprise AI Assistant

Requirements:

Secure authentication
RAG integration
Agent orchestration
Enterprise access control

Recommended Approach:

Managed identity
RBAC
Private networking
Azure AI Search integration
SDK-based connectivity

Common AI-103 Exam Tips

Understand Authentication Options

Know when to use:

API keys
Managed identities
Azure AD

Understand Endpoint Configuration

Know:

Deployment names
Service endpoints
Agent endpoints

Learn RBAC Concepts

Understand:

Least privilege
Role assignments
Secure access management

Understand Networking Concepts

Know:

Private endpoints
Firewalls
Secure connectivity

Learn Application Integration Concepts

Understand:

SDK initialization
Client configuration
Retry logic
Monitoring

Summary

Connecting applications to Azure AI Foundry projects is a foundational skill for AI-103.

For the exam, you should understand:

Foundry projects
Application connectivity
SDK integration
API integration
Authentication methods
Managed identities
RBAC
Deployment configuration
Endpoint management
Networking security
Logging and monitoring
Scalability and reliability

These skills are essential for building secure, scalable enterprise AI applications on Azure.

Practice Exam Questions

Question 1

What is the purpose of an Azure AI Foundry project?

A. Replace Azure subscriptions
B. Centrally manage AI resources, deployments, and workflows
C. Eliminate authentication
D. Replace APIs entirely

Answer

B. Centrally manage AI resources, deployments, and workflows

Explanation

Foundry projects organize AI development and operational assets.

Question 2

Which authentication method is recommended for production Azure workloads?

A. Hardcoded credentials
B. Managed identity
C. Shared public keys
D. Anonymous access

Answer

B. Managed identity

Explanation

Managed identities improve security by avoiding embedded secrets.

Question 3

What is a primary advantage of SDKs?

A. They eliminate APIs completely
B. They simplify application development and integration
C. They remove all authentication requirements
D. They prevent monitoring

Answer

B. They simplify application development and integration

Explanation

SDKs provide abstractions that simplify connectivity and workflow development.

Question 4

Why should applications use environment variables?

A. To increase GPU performance
B. To securely manage configuration values
C. To eliminate authentication
D. To disable RBAC

Answer

B. To securely manage configuration values

Explanation

Environment variables help manage endpoints and credentials securely.

Question 5

What does RBAC primarily control?

A. Token compression
B. Permissions and access to resources
C. Model quantization
D. Network bandwidth

Answer

B. Permissions and access to resources

Explanation

RBAC enforces authorization policies.

Question 6

Why are private endpoints used?

A. To increase hallucinations
B. To improve network security and isolate traffic
C. To disable monitoring
D. To reduce embedding dimensions

Answer

B. To improve network security and isolate traffic

Explanation

Private endpoints help secure enterprise AI workloads.

Question 7

What is commonly required when connecting to a deployed model?

A. Deployment name
B. Firewall removal
C. Disabling authentication
D. Public anonymous access

Answer

A. Deployment name

Explanation

Applications typically reference deployment identifiers.

Question 8

Why should applications implement retry policies?

A. To increase hallucinations
B. To recover from transient failures and improve reliability
C. To disable APIs
D. To remove authentication

Answer

B. To recover from transient failures and improve reliability

Explanation

Retry logic improves resiliency.

Question 9

Which service is commonly integrated for RAG search functionality?

A. Azure AI Search
B. Azure DNS
C. Azure Backup
D. Azure Batch

Answer

A. Azure AI Search

Explanation

Azure AI Search supports vector and semantic retrieval.

Question 10

What is the least privilege principle?

A. Give all users full access
B. Grant only the permissions necessary to perform required tasks
C. Disable RBAC
D. Allow anonymous authentication

Answer

B. Grant only the permissions necessary to perform required tasks

Explanation

Least privilege reduces security risk by minimizing unnecessary permissions.

Go to the AI-103 Exam Prep Hub main page

Agentic AI, AI, AI-103, Azure AI, Generative AI, Microsoft Certification May 25, 2026

Integrate generative workflows into applications by using Foundry SDKs and connectors (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Implement generative AI and agentic solutions (30–35%)
   --> Build generative applications by using Foundry
      --> Integrate generative workflows into applications by using Foundry SDKs and connectors

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

Modern AI applications rarely operate in isolation.

Enterprise generative AI solutions typically integrate with:

Web applications
APIs
Databases
Search systems
Business applications
Workflow engines
External tools

Azure AI Foundry provides:

SDKs
APIs
Connectors
Agent frameworks
Workflow orchestration capabilities

These services help developers integrate generative AI into enterprise applications.

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your understanding of integrating generative workflows into applications.

For the AI-103 exam, you should understand:

Foundry SDKs
APIs
Connectors
Workflow orchestration
Tool integration
Agent integration
RAG integration
Authentication
Deployment integration
Event-driven workflows
Monitoring and governance

What Are Foundry SDKs?

SDKs (Software Development Kits) provide:

Libraries
APIs
Helper functions
Authentication support
Workflow integration tools

SDKs simplify application development.

Benefits of SDKs

SDKs help developers:

Reduce development complexity
Standardize integration
Accelerate deployment
Improve reliability

Common SDK Capabilities

SDKs commonly support:

Model invocation
Agent orchestration
Function calling
Authentication
Streaming responses
Workflow management
Monitoring integration

APIs vs SDKs

APIs

Provide direct service access.

SDKs

Provide higher-level development abstractions.

SDKs often simplify API usage.

What Are Connectors?

Connectors integrate AI systems with:

External services
Enterprise applications
Data sources
Workflow systems

Common Connector Scenarios

Examples include:

CRM integration
ERP integration
SharePoint access
Database connectivity
Messaging systems
Search services

Workflow Integration

Generative workflows may integrate with:

Web applications
Mobile applications
Enterprise platforms
Automation systems

Web Application Integration

Generative AI commonly integrates into:

Chat interfaces
Copilots
Knowledge assistants
Recommendation systems

API-Based Integration

Applications often communicate with AI systems through:

REST APIs
HTTP endpoints
SDK abstractions

Authentication and Authorization

Secure integration requires:

Authentication
Authorization
Identity management

Managed Identity

Managed identities allow Azure services to:

Authenticate securely
Avoid hardcoded secrets
Access resources safely

Keyless Authentication

Keyless authentication improves security by reducing:

API key exposure
Credential management complexity

Secure Credential Storage

Applications should protect:

API keys
Tokens
Connection strings

Role-Based Access Control (RBAC)

RBAC helps control:

Resource permissions
Service access
Administrative privileges

Event-Driven Workflows

Event-driven systems react to:

User actions
File uploads
Database changes
External events

Asynchronous Workflows

Asynchronous workflows:

Improve scalability
Reduce blocking operations
Support long-running tasks

Streaming Responses

Streaming enables applications to:

Display responses incrementally
Improve user experience
Reduce perceived latency

Conversational Application Integration

Conversational systems often integrate:

Memory
Retrieval
Tool usage
User context

Integrating Retrieval-Augmented Generation (RAG)

RAG integration typically includes:

Vector search
Embedding generation
Retrieval pipelines
Prompt grounding

Azure AI Search Integration

Applications commonly integrate Azure AI Search for:

Vector search
Semantic search
Hybrid retrieval

Tool-Augmented Integration

Applications may integrate tools such as:

Databases
Search APIs
Business systems
External APIs

Function Calling Integration

Function calling enables:

Dynamic tool invocation
Structured interactions
Workflow orchestration

Agent Integration

Agent-based systems may:

Coordinate tools
Perform multistep reasoning
Execute workflows
Manage task state

Workflow Orchestration

Workflow orchestration coordinates:

AI reasoning
Tool execution
Retrieval
Human approvals

State Management

Integrated systems often maintain:

Session state
Workflow progress
User context

Memory Integration

Applications may integrate:

Short-term memory
Long-term memory
User preferences

Human-in-the-Loop Integration

Enterprise applications may require:

Human approvals
Review workflows
Escalation paths

Monitoring Integration

Applications should integrate monitoring for:

Errors
Latency
Tool usage
Costs
Safety violations

Logging and Traceability

Logging supports:

Troubleshooting
Auditing
Workflow analysis
Compliance

Trace Logging

Trace logs may capture:

Prompt flows
Tool calls
Retrieval steps
Workflow execution

Error Handling

Applications should handle:

API failures
Timeout errors
Invalid responses
Authentication failures

Retry Mechanisms

Retry strategies improve reliability by:

Recovering from transient failures
Reducing workflow interruptions

Scalability Considerations

Integrated AI systems should support:

High concurrency
Dynamic scaling
Distributed workloads

Latency Considerations

Developers should optimize:

Retrieval speed
Tool invocation times
Model response times

Cost Optimization

Organizations should optimize:

Token usage
API calls
Search operations
Infrastructure costs

CI/CD Integration

Generative AI applications may integrate with:

Automated deployment pipelines
Testing frameworks
Infrastructure automation

Testing Integrated Workflows

Organizations should test:

Workflow correctness
Tool integration
Retrieval quality
Safety compliance

Safety Integration

Applications should integrate:

Content filtering
Safety policies
Guardrails
Approval workflows

Governance and Compliance

Enterprise systems may require:

Audit logging
Data protection
Regulatory compliance
Access controls

Azure AI Foundry Integration Features

Azure AI Foundry supports:

SDK-based development
Workflow orchestration
Model deployment
Agent development
Evaluation pipelines
Monitoring

Real-World Integration Scenarios

Scenario 1: Enterprise Knowledge Assistant

Requirements:

Document retrieval
Conversational AI
Enterprise search integration

Recommended Integration:

Foundry SDK + Azure AI Search

Scenario 2: Customer Support Copilot

Requirements:

CRM integration
Ticket lookup
Escalation workflows

Recommended Integration:

Tool-augmented agent workflows

Scenario 3: Financial Workflow Automation

Requirements:

Human approvals
Audit logging
Secure authentication

Recommended Integration:

HITL workflow + RBAC + trace logging

Scenario 4: AI Research Assistant

Requirements:

Multistep reasoning
Web search integration
Citation generation

Recommended Integration:

RAG + orchestration workflows

Common AI-103 Exam Tips

Understand SDK vs API Differences

Know:

SDK abstractions
API integrations
Authentication approaches

Learn Connector Concepts

Understand:

External integrations
Enterprise systems
Workflow connectors

Understand Workflow Integration

Know:

Tool orchestration
Agent integration
Event-driven workflows
Streaming responses

Learn Security Concepts

Understand:

Managed identity
Keyless credentials
RBAC
Secure secret handling

Summary

Modern generative AI systems depend heavily on integration.

For the AI-103 exam, you should understand:

Foundry SDKs
APIs
Connectors
Workflow orchestration
Function calling
Agent integration
RAG integration
Authentication and RBAC
Event-driven workflows
Monitoring and logging
CI/CD integration
Governance and compliance

These concepts are foundational for building scalable enterprise AI applications and agentic systems on Azure.

Practice Exam Questions

Question 1

What is the primary purpose of an SDK?

A. Replace APIs entirely
B. Simplify application development using libraries and abstractions
C. Eliminate authentication requirements
D. Disable workflow orchestration

Answer

B. Simplify application development using libraries and abstractions

Explanation

SDKs provide tools and abstractions that simplify development.

Question 2

What is a connector in a generative AI solution?

A. A GPU optimization engine
B. A mechanism for integrating external systems and services
C. A vector compression method
D. A storage replication service

Answer

B. A mechanism for integrating external systems and services

Explanation

Connectors enable integration with business applications and data sources.

Question 3

Why are managed identities important?

A. They increase token limits
B. They provide secure authentication without hardcoded credentials
C. They replace vector search
D. They eliminate RBAC

Answer

B. They provide secure authentication without hardcoded credentials

Explanation

Managed identities improve security by avoiding embedded secrets.

Question 4

What is the benefit of streaming responses?

A. Eliminates all latency
B. Improves user experience by displaying incremental output
C. Disables monitoring
D. Prevents tool invocation

Answer

B. Improves user experience by displaying incremental output

Explanation

Streaming responses reduce perceived latency.

Question 5

What is the purpose of function calling?

A. Compress prompts
B. Allow models to invoke external tools dynamically
C. Replace orchestration
D. Eliminate APIs

Answer

B. Allow models to invoke external tools dynamically

Explanation

Function calling enables structured tool interactions.

Question 6

Which Azure service is commonly integrated for vector and semantic search?

A. Azure AI Search
B. Azure DNS
C. Azure Backup
D. Azure Batch

Answer

A. Azure AI Search

Explanation

Azure AI Search supports vector and semantic retrieval.

Question 7

What is a key advantage of asynchronous workflows?

A. Increased blocking operations
B. Improved scalability and support for long-running tasks
C. Removal of authentication
D. Elimination of APIs

Answer

B. Improved scalability and support for long-running tasks

Explanation

Asynchronous workflows support efficient distributed execution.

Question 8

Why is trace logging important?

A. It removes monitoring requirements
B. It provides visibility into workflow execution and troubleshooting
C. It disables retrieval pipelines
D. It eliminates RBAC

Answer

B. It provides visibility into workflow execution and troubleshooting

Explanation

Trace logs help monitor workflows and investigate issues.

Question 9

What is the purpose of RBAC?

A. Increase vector dimensions
B. Control permissions and access to resources
C. Replace authentication
D. Reduce prompt sizes

Answer

B. Control permissions and access to resources

Explanation

RBAC enforces authorization policies.

Question 10

What is a major challenge when integrating complex generative workflows?

A. Eliminating all costs
B. Managing latency, scalability, and reliability
C. Removing all monitoring
D. Disabling orchestration

Answer

B. Managing latency, scalability, and reliability

Explanation

Integrated workflows often involve multiple services and asynchronous operations.

Go to the AI-103 Exam Prep Hub main page

Agentic AI, AI, AI-103, Artificial Intelligence (AI), Azure AI, Microsoft Certification May 25, 2026

Evaluate models and apps, including detecting fabrications, relevance, quality, and safety (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Implement generative AI and agentic solutions (30–35%)
   --> Build generative applications by using Foundry
      --> Evaluate models and apps, including detecting fabrications, relevance, quality, and safety

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

Building generative AI applications is only part of the development process.

Organizations must also evaluate whether AI systems are:

Accurate
Reliable
Relevant
Safe
Grounded
Trustworthy

AI systems can generate:

Hallucinations
Unsafe content
Biased responses
Irrelevant answers
Inconsistent outputs

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your understanding of evaluating models and applications.

For the AI-103 exam, you should understand:

Model evaluation
Application evaluation
Fabrication detection
Groundedness
Relevance evaluation
Quality evaluation
Safety evaluation
Responsible AI testing
Automated evaluators
Human evaluation
Benchmarking
Monitoring and continuous evaluation

Why AI Evaluation Matters

Evaluation is essential because generative AI systems are probabilistic.

This means:

Responses may vary
Outputs may be incorrect
Safety risks may occur
Hallucinations may appear

Without evaluation, organizations cannot reliably trust AI systems.

What Is AI Evaluation?

AI evaluation is the process of measuring:

Accuracy
Safety
Reliability
Relevance
Groundedness
User satisfaction

Types of AI Evaluation

Common evaluation categories include:

Model evaluation
Prompt evaluation
Retrieval evaluation
Application evaluation
Safety evaluation
Human evaluation

Model Evaluation

Model evaluation focuses on:

Model quality
Accuracy
Performance
Reasoning ability

Application Evaluation

Application evaluation measures:

End-to-end user experience
Workflow success
Tool orchestration quality
Groundedness

What Are Fabrications?

Fabrications are generated outputs that:

Are incorrect
Are unsupported
Contain invented facts
Misrepresent information

Fabrications are commonly called hallucinations.

Causes of Fabrications

Fabrications may occur because:

The model lacks relevant knowledge
Prompts are ambiguous
Retrieval quality is poor
Context is insufficient
Safety constraints are weak

Fabrication Detection

Organizations should evaluate whether outputs:

Match trusted sources
Remain grounded
Avoid unsupported claims

Groundedness Evaluation

Groundedness measures whether responses are supported by:

Retrieved documents
Enterprise data
Trusted sources

Importance of Groundedness

Grounded responses:

Improve trust
Reduce hallucinations
Increase explainability

Retrieval Quality Evaluation

RAG systems should evaluate:

Search relevance
Retrieved chunk quality
Citation accuracy
Context completeness

Relevance Evaluation

Relevance measures whether responses:

Answer the user’s question
Stay on-topic
Match user intent

Quality Evaluation

Quality evaluations may assess:

Clarity
Completeness
Coherence
Fluency
Professionalism

Consistency Evaluation

Consistency measures whether models:

Produce stable responses
Avoid contradictory outputs
Maintain predictable behavior

Safety Evaluation

Safety evaluations identify:

Harmful outputs
Toxic content
Unsafe instructions
Policy violations

Responsible AI Evaluation

Responsible AI testing focuses on:

Fairness
Safety
Transparency
Accountability
Privacy

Bias Evaluation

Organizations should evaluate whether models:

Produce biased outputs
Treat groups unfairly
Reinforce stereotypes

Toxicity Detection

Toxicity evaluations identify:

Offensive language
Hate speech
Harassment
Abusive content

Jailbreak Testing

Jailbreak testing evaluates whether users can bypass:

Safety controls
Content filters
Guardrails

Adversarial Testing

Adversarial testing intentionally challenges models using:

Malicious prompts
Edge cases
Prompt injection attacks

Prompt Injection Testing

Prompt injection testing evaluates whether:

External content manipulates model behavior
Instructions override safety policies

Automated Evaluators

Automated evaluators use:

Rules
Scoring systems
AI-based evaluators

To assess model outputs.

AI-Assisted Evaluation

Some systems use LLMs to evaluate:

Relevance
Groundedness
Quality
Safety

Human Evaluation

Human reviewers may evaluate:

Accuracy
Tone
Helpfulness
Safety
Business alignment

Human-in-the-Loop Evaluation

Human-in-the-loop evaluation combines:

Automated evaluation
Human oversight
Expert validation

Benchmarking Models

Benchmarking compares models using:

Standard datasets
Consistent prompts
Defined metrics

A/B Testing

A/B testing compares:

Different prompts
Different models
Different workflows

Evaluation Metrics

Common metrics include:

Precision
Recall
Accuracy
Relevance
Groundedness
Toxicity scores
Latency
User satisfaction

Precision and Recall

Precision

Measures how many retrieved results are relevant.

Recall

Measures how many relevant results were successfully retrieved.

Latency Evaluation

Organizations should measure:

Response times
Retrieval delays
Tool execution times

Cost Evaluation

Cost evaluation considers:

Token usage
API calls
Infrastructure consumption

User Satisfaction Evaluation

Organizations may measure:

User feedback
Completion success
Satisfaction ratings

Continuous Evaluation

AI systems should be evaluated continuously because:

User behavior changes
Data evolves
Model drift may occur

Model Drift

Model drift occurs when:

Performance changes over time
Inputs evolve
User expectations shift

Monitoring Production Systems

Organizations should monitor:

Safety violations
Hallucination rates
Retrieval failures
Latency spikes
Cost increases

Evaluation Pipelines

Evaluation pipelines automate:

Testing
Scoring
Reporting
Regression analysis

Regression Testing

Regression testing ensures updates do not:

Reduce quality
Break workflows
Increase hallucinations

Azure AI Foundry Evaluation Capabilities

Azure AI Foundry supports:

Evaluation workflows
Automated evaluators
Safety monitoring
Groundedness evaluation
Prompt testing
Trace analysis

Trace Analysis

Trace analysis helps inspect:

Tool calls
Retrieval steps
Agent decisions
Workflow execution

Evaluation Datasets

Organizations should create datasets containing:

Expected outputs
Edge cases
Adversarial prompts
Real-world scenarios

Synthetic Test Data

Synthetic data may help test:

Rare scenarios
Adversarial prompts
Safety boundaries

Real-World Evaluation Scenarios

Scenario 1: Enterprise Chatbot

Requirements:

Accurate responses
Citation support
Low hallucination rate

Recommended Evaluation:

Groundedness testing
Retrieval quality evaluation

Scenario 2: Financial Assistant

Requirements:

High accuracy
Safety compliance
Low fabrication risk

Recommended Evaluation:

Human review
Adversarial testing
Approval workflows

Scenario 3: Customer Support Copilot

Requirements:

Relevant responses
Fast response times
Consistent tone

Recommended Evaluation:

Latency evaluation
Quality scoring
A/B testing

Scenario 4: Agentic Workflow System

Requirements:

Tool accuracy
Safe tool execution
Workflow traceability

Recommended Evaluation:

Trace analysis
Tool execution monitoring
HITL evaluation

Common AI-103 Exam Tips

Understand Evaluation Categories

Know the differences between:

Relevance
Quality
Groundedness
Safety
Consistency

Learn Fabrication Detection Concepts

Understand:

Hallucinations
Unsupported claims
Grounding validation

Understand Safety Testing

Know:

Toxicity testing
Jailbreak testing
Prompt injection evaluation
Adversarial testing

Learn Monitoring Concepts

Understand:

Continuous evaluation
Drift detection
Trace analysis
Regression testing

Summary

Evaluating generative AI systems is critical for building:

Reliable
Safe
Grounded
Trustworthy applications

For the AI-103 exam, you should understand:

Fabrication detection
Groundedness evaluation
Retrieval quality
Relevance testing
Quality evaluation
Safety evaluation
Toxicity detection
Adversarial testing
Human evaluation
Automated evaluators
Monitoring and drift detection
Evaluation pipelines

These concepts are foundational for developing enterprise-grade AI applications and agentic systems on Azure.

Practice Exam Questions

Question 1

What is a fabrication in generative AI?

A. A storage replication process
B. An unsupported or invented response
C. A vector indexing method
D. A deployment strategy

Answer

B. An unsupported or invented response

Explanation

Fabrications, also called hallucinations, are incorrect or invented outputs.

Question 2

What does groundedness measure?

A. GPU performance
B. Whether outputs are supported by trusted sources
C. Network bandwidth
D. Token compression efficiency

Answer

B. Whether outputs are supported by trusted sources

Explanation

Groundedness evaluates factual support from retrieved or trusted data.

Question 3

Which evaluation type focuses on harmful or unsafe outputs?

A. Latency evaluation
B. Safety evaluation
C. Compression evaluation
D. Replication evaluation

Answer

B. Safety evaluation

Explanation

Safety evaluations detect harmful, toxic, or policy-violating outputs.

Question 4

What is the purpose of retrieval quality evaluation in RAG systems?

A. Measure GPU speed
B. Assess search relevance and retrieved context quality
C. Reduce storage redundancy
D. Disable embeddings

Answer

B. Assess search relevance and retrieved context quality

Explanation

Retrieval quality measures how useful and relevant retrieved information is.

Question 5

What is jailbreak testing?

A. Testing storage failures
B. Evaluating attempts to bypass safety controls
C. Measuring retrieval latency
D. Compressing prompts

Answer

B. Evaluating attempts to bypass safety controls

Explanation

Jailbreak testing checks whether users can circumvent AI safety mechanisms.

Question 6

Which metric measures whether responses answer the user’s question appropriately?

A. Relevance
B. Replication
C. Throughput
D. Compression

Answer

A. Relevance

Explanation

Relevance evaluates how well outputs match user intent.

Question 7

Why is continuous evaluation important?

A. To eliminate all infrastructure costs
B. Because models and data can change over time
C. To remove all safety policies
D. To disable monitoring

Answer

B. Because models and data can change over time

Explanation

Continuous evaluation helps detect drift and performance degradation.

Question 8

What is adversarial testing?

A. Testing network redundancy
B. Challenging AI systems with malicious or difficult prompts
C. Increasing vector dimensions
D. Optimizing GPU allocation

Answer

B. Challenging AI systems with malicious or difficult prompts

Explanation

Adversarial testing identifies vulnerabilities and unsafe behaviors.

Question 9

What is a benefit of A/B testing in AI systems?

A. Eliminates monitoring requirements
B. Compares prompts or models to identify better performance
C. Removes the need for evaluation datasets
D. Disables retrieval pipelines

Answer

B. Compares prompts or models to identify better performance

Explanation

A/B testing helps optimize prompts, workflows, and models.

Question 10

Which Azure capability helps inspect workflow execution and tool calls?

A. Trace analysis
B. DNS failover
C. Storage mirroring
D. GPU partitioning

Answer

A. Trace analysis

Explanation

Trace analysis provides visibility into workflow execution and reasoning steps.

Go to the AI-103 Exam Prep Hub main page

Agentic AI, AI, AI-103, Artificial Intelligence (AI), Azure AI, Generative AI, Microsoft Certification May 25, 2026

Design workflows, tool-augmented flows, and multistep reasoning pipelines (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Implement generative AI and agentic solutions (30–35%)
   --> Build generative applications by using Foundry
      --> Design workflows, tool-augmented flows, and multistep reasoning pipelines

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

Modern AI systems are evolving beyond simple prompt-response interactions.

Today’s generative AI applications often:

Use external tools
Perform multistep reasoning
Orchestrate workflows
Retrieve enterprise data
Execute actions autonomously
Coordinate across services

These systems are commonly called:

Agentic systems
Tool-augmented AI systems
AI workflow pipelines

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your understanding of designing intelligent workflows and reasoning pipelines.

For the AI-103 exam, you should understand:

AI workflows
Agent orchestration
Tool augmentation
Function calling
Multistep reasoning
Workflow pipelines
Retrieval integration
Memory integration
Planning and execution
Human-in-the-loop workflows
Monitoring and governance

What Are AI Workflows?

AI workflows are structured sequences of operations that combine:

AI reasoning
Data retrieval
Tool execution
Decision-making
Automation

Workflows coordinate multiple steps to complete complex tasks.

Why AI Workflows Matter

Simple prompts are often insufficient for:

Enterprise automation
Complex reasoning
Dynamic decision-making
Multi-system integration

Workflows allow AI systems to:

Break problems into steps
Use external tools
Validate outputs
Iterate toward solutions

What Is Tool Augmentation?

Tool augmentation allows AI systems to use external capabilities.

Examples include:

APIs
Databases
Search engines
Calculators
Business systems
Code interpreters

Why Tool Augmentation Is Important

Language models alone:

Cannot access real-time data
Cannot execute business actions directly
Cannot reliably perform all calculations

Tools extend AI capabilities.

Common Tool-Augmented Scenarios

Examples include:

Checking inventory
Booking appointments
Querying databases
Sending emails
Executing workflows
Calling REST APIs

What Is Function Calling?

Function calling enables models to:

Detect when a tool is needed
Generate structured tool requests
Invoke external services
Process returned results

Function Calling Workflow

Typical flow:

User submits request
Model determines tool requirement
Model generates function call
External tool executes
Results return to model
Model generates final response

Structured Tool Inputs

Function calling typically uses:

JSON schemas
Structured parameters
Validated inputs

This improves reliability.

Tool Selection

Agentic systems may dynamically choose:

Which tools to use
Which workflows to invoke
Which retrieval strategies to apply

Tool Orchestration

Tool orchestration coordinates multiple tools within a workflow.

Examples include:

Retrieval + summarization
Search + booking systems
Database queries + reporting

Sequential Workflows

Sequential workflows execute steps in order.

Example:

Retrieve customer data
Analyze account status
Generate recommendations
Send response

Parallel Workflows

Parallel workflows execute multiple tasks simultaneously.

Benefits include:

Faster execution
Better scalability
Reduced latency

Conditional Workflows

Conditional workflows branch based on:

User intent
Retrieved data
Safety evaluations
Confidence scores

What Is Multistep Reasoning?

Multistep reasoning breaks complex problems into smaller steps.

This improves:

Accuracy
Planning
Decision quality

Examples of Multistep Reasoning

Examples include:

Research workflows
Financial analysis
Travel planning
Technical troubleshooting

Chain-of-Thought Reasoning

Chain-of-thought reasoning encourages models to:

Reason step-by-step
Decompose problems
Validate intermediate steps

Planning and Execution Models

Agentic systems often separate:

Planning
Execution

The planner decides:

What steps are needed
Which tools to use

The executor performs actions.

Planner-Executor Architectures

Planner-executor architectures support:

Dynamic workflows
Adaptive reasoning
Task decomposition

ReAct Pattern

The ReAct (Reason + Act) pattern combines:

Reasoning
Tool usage
Observation
Iterative decision-making

Reflection and Self-Correction

Some systems support:

Self-evaluation
Output refinement
Error correction

Retrieval-Augmented Workflows

Workflows often integrate:

Vector search
RAG pipelines
Enterprise grounding

Memory in Agentic Systems

AI systems may use memory for:

Conversation history
User preferences
Workflow state
Long-running tasks

Short-Term Memory

Short-term memory stores:

Current conversation context
Immediate workflow information

Long-Term Memory

Long-term memory stores:

Persistent preferences
Historical interactions
Learned context

Workflow State Management

State management tracks:

Current task progress
Intermediate outputs
Pending actions

Human-in-the-Loop (HITL) Workflows

High-risk workflows may require:

Human approvals
Validation checkpoints
Escalation paths

Approval Gates

Approval gates can prevent:

Unsafe actions
Unauthorized tool usage
Harmful outputs

Safety and Governance

Organizations should enforce:

Tool restrictions
Permission boundaries
Safety filters
Approval workflows

Autonomous vs Semi-Autonomous Agents

Autonomous Agents

Can:

Make decisions independently
Execute workflows automatically

Semi-Autonomous Agents

Require:

Human review
Approval checkpoints

Workflow Monitoring

Organizations should monitor:

Tool usage
Failures
Safety violations
Latency
Costs

Trace Logging

Trace logging helps track:

Workflow execution
Tool calls
Reasoning steps
Agent decisions

Error Handling in Workflows

Workflow pipelines should handle:

API failures
Missing data
Timeout errors
Invalid outputs

Retry Strategies

Common retry strategies include:

Automatic retries
Fallback workflows
Alternative tool selection

Fallback Models

Applications may use fallback models when:

Primary models fail
Costs exceed thresholds
Latency becomes excessive

Workflow Optimization

Optimization strategies include:

Parallel processing
Caching
Smaller models
Efficient retrieval

Latency Considerations

Complex workflows may increase latency due to:

Multiple model calls
Tool invocations
Retrieval operations

Cost Considerations

Tool-augmented systems may increase:

Token usage
API calls
Infrastructure costs

Azure AI Foundry Workflow Capabilities

Azure AI Foundry supports:

Model orchestration
Tool integration
Agent workflows
Evaluation pipelines
Monitoring

Common AI-103 Workflow Scenarios

Scenario 1: Enterprise Research Assistant

Requirements:

Multi-document retrieval
Summarization
Citation generation

Recommended Workflow:

RAG + multistep reasoning

Scenario 2: Customer Service Agent

Requirements:

CRM access
Ticket management
Escalation workflows

Recommended Workflow:

Tool-augmented agent

Scenario 3: Financial Approval System

Requirements:

Risk evaluation
Human approvals
Audit logging

Recommended Workflow:

HITL approval pipeline

Scenario 4: AI Coding Assistant

Requirements:

Code generation
Code execution
Documentation retrieval

Recommended Workflow:

Code model + tool orchestration

Common AI-103 Exam Tips

Understand Workflow Patterns

Know:

Sequential workflows
Parallel workflows
Conditional workflows

Learn Tool-Augmented AI Concepts

Understand:

Function calling
Tool orchestration
Dynamic tool selection

Understand Multistep Reasoning

Know:

Chain-of-thought reasoning
Planner-executor patterns
ReAct workflows

Learn Governance Concepts

Understand:

HITL workflows
Approval gates
Monitoring
Trace logging

Summary

Modern AI applications increasingly rely on:

Workflow orchestration
Tool augmentation
Multistep reasoning
Agentic architectures

For the AI-103 exam, you should understand:

AI workflow design
Function calling
Tool orchestration
Sequential and parallel workflows
Multistep reasoning
Planner-executor architectures
ReAct patterns
Memory integration
HITL workflows
Monitoring and governance

These concepts enable organizations to build:

Intelligent
Autonomous
Scalable
Governed AI systems

They are foundational for modern generative AI and agentic solutions on Azure.

Practice Exam Questions

Question 1

What is the primary purpose of tool augmentation in AI systems?

A. Reduce storage costs
B. Extend model capabilities using external tools
C. Eliminate prompts
D. Replace vector search

Answer

B. Extend model capabilities using external tools

Explanation

Tool augmentation enables AI systems to interact with APIs, databases, and other services.

Question 2

What does function calling enable a model to do?

A. Generate only static responses
B. Invoke external tools using structured inputs
C. Eliminate workflows
D. Replace embeddings

Answer

B. Invoke external tools using structured inputs

Explanation

Function calling allows models to interact with external services.

Question 3

Which workflow type executes tasks simultaneously?

A. Sequential workflow
B. Parallel workflow
C. Manual workflow
D. Static workflow

Answer

B. Parallel workflow

Explanation

Parallel workflows improve speed by running tasks concurrently.

Question 4

What is multistep reasoning?

A. Compressing vector indexes
B. Breaking complex tasks into smaller reasoning steps
C. Increasing GPU memory
D. Reducing prompt size only

Answer

B. Breaking complex tasks into smaller reasoning steps

Explanation

Multistep reasoning improves problem-solving accuracy.

Question 5

What does the ReAct pattern combine?

A. Compression and storage
B. Reasoning and acting
C. Replication and scaling
D. Encryption and backup

Answer

B. Reasoning and acting

Explanation

ReAct combines reasoning steps with tool usage.

Question 6

What is the purpose of workflow state management?

A. Monitor GPU temperature
B. Track task progress and intermediate outputs
C. Disable logging
D. Replace semantic search

Answer

B. Track task progress and intermediate outputs

Explanation

State management helps maintain workflow continuity.

Question 7

Which architecture separates planning from execution?

A. Static inference architecture
B. Planner-executor architecture
C. Batch storage architecture
D. Compression architecture

Answer

B. Planner-executor architecture

Explanation

Planner-executor systems divide reasoning and execution responsibilities.

Question 8

Why are approval gates important in AI workflows?

A. They increase vector dimensions
B. They prevent unsafe or unauthorized actions
C. They reduce indexing speed
D. They eliminate monitoring requirements

Answer

B. They prevent unsafe or unauthorized actions

Explanation

Approval gates enforce governance and human oversight.

Question 9

Which concept allows AI systems to remember previous interactions?

A. Semantic ranking
B. Memory integration
C. Static chunking
D. GPU partitioning

Answer

B. Memory integration

Explanation

Memory enables contextual continuity and long-running workflows.

Question 10

What is a major challenge of complex AI workflows?

A. Eliminating all costs
B. Increased latency from multiple operations
C. Removing all need for monitoring
D. Preventing all hallucinations automatically

Answer

B. Increased latency from multiple operations

Explanation

Complex workflows may require multiple model calls and tool executions.

Go to the AI-103 Exam Prep Hub main page

AI, AI-103, Azure AI, Microsoft Certification May 25, 2026

Implement Retrieval-Augmented Generation (RAG) in an application (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Implement generative AI and agentic solutions (30–35%)
   --> Build generative applications by using Foundry
      --> Implement Retrieval-Augmented Generation (RAG) in an application

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

Large language models (LLMs) are powerful, but they have limitations.

LLMs may:

Hallucinate information
Generate outdated responses
Lack organization-specific knowledge
Produce unverifiable answers

Retrieval-Augmented Generation (RAG) addresses these issues by combining:

Information retrieval
Vector search
Enterprise knowledge grounding
Generative AI

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your understanding of how to implement RAG-based applications.

For the AI-103 exam, you should understand:

RAG architecture
Vector search
Embeddings
Chunking strategies
Indexing
Semantic search
Grounding techniques
Prompt augmentation
Retrieval pipelines
RAG optimization
Monitoring and evaluation
Security considerations

What Is Retrieval-Augmented Generation (RAG)?

RAG is an AI architecture that combines:

Information retrieval
Context augmentation
Generative AI

Instead of relying only on model training data, RAG retrieves relevant information from external sources and injects it into prompts.

Why RAG Matters

RAG improves:

Accuracy
Grounding
Freshness of information
Enterprise knowledge integration
Explainability

Common RAG Use Cases

Typical RAG applications include:

Enterprise chatbots
Knowledge assistants
Internal documentation search
Customer support systems
Research assistants
AI copilots

Core Components of a RAG System

A RAG solution typically includes:

Data sources
Chunking pipeline
Embedding model
Vector database or search index
Retrieval engine
Large language model
Prompt orchestration layer

RAG Workflow Overview

The general workflow is:

Ingest data
Split data into chunks
Generate embeddings
Store embeddings in an index
Receive user query
Convert query to embeddings
Retrieve relevant chunks
Add retrieved context to prompt
Generate grounded response

What Are Embeddings?

Embeddings are numerical vector representations of data.

Embeddings capture:

Semantic meaning
Contextual similarity
Relationships between concepts

Embedding Models

Embedding models convert:

Text
Documents
Queries

Into vectors for similarity comparison.

Vector Similarity Search

Vector search identifies content that is semantically similar.

Unlike keyword search, vector search understands:

Meaning
Intent
Context

What Is Chunking?

Chunking divides documents into smaller sections.

Chunking is essential because:

Models have token limits
Smaller chunks improve retrieval precision
Large documents are difficult to process efficiently

Chunking Strategies

Common chunking methods include:

Fixed-size chunking
Sliding window chunking
Semantic chunking
Paragraph-based chunking

Fixed-Size Chunking

Documents are split into equal-sized chunks.

Advantages:

Simple
Predictable

Disadvantages:

May break context unexpectedly

Sliding Window Chunking

Chunks overlap partially.

Benefits include:

Better context preservation
Improved retrieval continuity

Semantic Chunking

Semantic chunking groups logically related content.

Advantages:

Better contextual integrity
Higher retrieval quality

Metadata in RAG Systems

Metadata may include:

Document title
Author
Date
Category
Security labels

Metadata improves filtering and retrieval.

Indexing in RAG Systems

Indexes store:

Embeddings
Metadata
Searchable content

Indexes enable efficient retrieval.

Vector Databases and Search Indexes

RAG systems commonly use:

Azure AI Search
Vector indexes
Hybrid search systems

Semantic Search

Semantic search improves relevance using:

Meaning
Intent
Natural language understanding

Hybrid Search

Hybrid search combines:

Keyword search
Semantic ranking
Vector similarity search

This often improves retrieval quality.

Retrieval Pipelines

Retrieval pipelines:

Process user queries
Retrieve relevant information
Rank search results
Filter irrelevant content

Query Embeddings

User queries are converted into embeddings.

The query vector is compared against stored vectors.

Similarity Metrics

Common similarity calculations include:

Cosine similarity
Euclidean distance
Dot product similarity

Top-K Retrieval

Top-K retrieval returns the most relevant results.

Choosing the right K value is important:

Too few results may miss context
Too many results may add noise

Prompt Augmentation

Retrieved content is inserted into prompts.

This process is called:

Prompt grounding
Context injection
Prompt augmentation

Grounded Responses

Grounded responses:

Reference trusted data
Reduce hallucinations
Improve reliability

System Prompts in RAG

System prompts may instruct the model to:

Use only retrieved sources
Cite references
Avoid unsupported claims

Citation Generation

Many RAG applications provide:

Source references
Citations
Linked documents

This improves transparency.

Hallucination Reduction

RAG reduces hallucinations by:

Providing factual context
Using enterprise knowledge
Restricting unsupported generation

RAG Architecture Patterns

Common patterns include:

Basic RAG
Hybrid RAG
Multi-stage retrieval
Agentic RAG

Basic RAG

Basic RAG:

Retrieves documents
Injects them into prompts
Generates responses

Hybrid RAG

Hybrid RAG combines:

Vector search
Keyword search
Semantic ranking

Multi-Stage Retrieval

Multi-stage retrieval uses:

Initial retrieval
Re-ranking
Filtering
Secondary refinement

Agentic RAG

Agentic RAG systems may:

Choose retrieval tools dynamically
Perform iterative searches
Validate retrieved data
Orchestrate workflows

Azure AI Search in RAG

Azure AI Search commonly provides:

Vector search
Semantic ranking
Hybrid search
Index management

Data Ingestion Pipelines

RAG ingestion pipelines may process:

PDFs
Web pages
Databases
Office documents
Structured data

Data Freshness

Organizations should ensure indexes remain current.

Strategies include:

Scheduled reindexing
Incremental ingestion
Event-driven updates

Access Control in RAG

Enterprise RAG systems should enforce:

Role-based access
Document-level security
Identity-aware retrieval

Security Considerations

Organizations should secure:

Data ingestion pipelines
Search indexes
Embedding endpoints
Model endpoints

Monitoring RAG Systems

Organizations should monitor:

Retrieval quality
Grounding quality
Latency
Hallucinations
Search relevance

Evaluating RAG Performance

Key evaluation metrics include:

Precision
Recall
Relevance
Groundedness
Citation accuracy

Groundedness Evaluation

Groundedness measures whether responses are supported by retrieved content.

Retrieval Quality Evaluation

Organizations should evaluate:

Search result relevance
Ranking effectiveness
Missing context

Latency Optimization

RAG pipelines can introduce additional latency.

Optimization strategies include:

Caching
Smaller embeddings
Efficient indexing
Query optimization

Cost Optimization

Cost reduction strategies include:

Limiting retrieved chunks
Smaller embedding models
Efficient indexing
Intelligent caching

Responsible AI Considerations

Developers should:

Validate sources
Prevent data leakage
Monitor hallucinations
Enforce safety policies

Common AI-103 RAG Scenarios

Scenario 1: Enterprise Knowledge Chatbot

Requirements:

Internal document access
Accurate answers
Source citations

Recommended Solution:

RAG with Azure AI Search

Scenario 2: Legal Document Assistant

Requirements:

High factual accuracy
Traceability
Large document support

Recommended Solution:

Semantic chunking
Hybrid search
Citation generation

Scenario 3: Customer Support Copilot

Requirements:

Fast retrieval
Grounded answers
Updated knowledge

Recommended Solution:

Incremental indexing
Real-time retrieval

Scenario 4: Agentic AI Workflow

Requirements:

Dynamic retrieval
Multi-step reasoning
Tool orchestration

Recommended Solution:

Agentic RAG architecture

Common AI-103 Exam Tips

Understand the RAG Workflow

Know all stages:

Ingestion
Chunking
Embeddings
Indexing
Retrieval
Prompt augmentation
Generation

Learn Embedding Concepts

Understand:

Semantic vectors
Similarity search
Embedding models

Understand Search Types

Know the differences between:

Keyword search
Vector search
Semantic search
Hybrid search

Understand Grounding

Know how grounding:

Reduces hallucinations
Improves factual accuracy
Supports explainability

Summary

Retrieval-Augmented Generation (RAG) is one of the most important generative AI architectures.

For the AI-103 exam, you should understand:

RAG architecture
Embeddings
Chunking
Indexing
Vector search
Semantic search
Hybrid search
Prompt grounding
Retrieval pipelines
Groundedness evaluation
Security considerations
Monitoring and optimization

RAG enables organizations to build:

Accurate
Explainable
Grounded
Enterprise-aware AI applications

These concepts are foundational for modern AI systems on Azure.

Practice Exam Questions

Question 1

What is the primary goal of Retrieval-Augmented Generation (RAG)?

A. Reduce storage replication
B. Improve factual grounding using retrieved data
C. Eliminate vector search
D. Replace all language models

Answer

B. Improve factual grounding using retrieved data

Explanation

RAG improves accuracy by injecting retrieved information into prompts.

Question 2

What are embeddings?

A. GPU drivers
B. Numerical vector representations of data
C. Network security policies
D. Storage replication methods

Answer

B. Numerical vector representations of data

Explanation

Embeddings represent semantic meaning as vectors.

Question 3

Why is chunking important in RAG systems?

A. To increase network latency
B. To divide documents into manageable sections
C. To disable semantic search
D. To eliminate embeddings

Answer

B. To divide documents into manageable sections

Explanation

Chunking improves retrieval efficiency and contextual relevance.

Question 4

Which search method understands semantic meaning instead of exact keywords?

A. Static indexing
B. Vector search
C. Archive retrieval
D. Compression balancing

Answer

B. Vector search

Explanation

Vector search retrieves semantically similar content.

Question 5

What does hybrid search combine?

A. GPU clusters and storage accounts
B. Keyword search and vector search
C. Virtual machines and containers
D. Authentication and authorization

Answer

B. Keyword search and vector search

Explanation

Hybrid search combines lexical and semantic retrieval methods.

Question 6

What is prompt augmentation?

A. Increasing storage capacity
B. Adding retrieved context to prompts
C. Compressing vectors
D. Removing metadata

Answer

B. Adding retrieved context to prompts

Explanation

Prompt augmentation injects retrieved content into model prompts.

Question 7

What is groundedness?

A. GPU allocation efficiency
B. Whether responses are supported by retrieved sources
C. Network bandwidth usage
D. Storage replication speed

Answer

B. Whether responses are supported by retrieved sources

Explanation

Groundedness measures factual support from retrieved content.

Question 8

Which Azure service is commonly used for vector and semantic search in RAG systems?

A. Azure AI Search
B. Azure DNS
C. Azure Backup
D. Azure Batch

Answer

A. Azure AI Search

Explanation

Azure AI Search supports vector, semantic, and hybrid search.

Question 9

What is a major advantage of semantic chunking?

A. It eliminates embeddings
B. It preserves contextual meaning better
C. It disables retrieval
D. It reduces authentication requirements

Answer

B. It preserves contextual meaning better

Explanation

Semantic chunking groups logically related content.

Question 10

Which metric evaluates whether retrieved results are relevant?

A. Groundedness
B. Retrieval quality
C. GPU utilization
D. Storage redundancy

Answer

B. Retrieval quality

Explanation

Retrieval quality measures the relevance of retrieved documents.

Go to the AI-103 Exam Prep Hub main page

AI, AI-103, Artificial Intelligence (AI), Generative AI, Microsoft Certification May 25, 2026

Deploy and consume LLMs, small models, code models, and multimodal models (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Implement generative AI and agentic solutions (30–35%)
   --> Build generative applications by using Foundry
      --> Deploy and consume LLMs, small models, code models, and multimodal models

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

Modern AI applications rely on a wide variety of AI models.

Different models are optimized for different workloads, including:

Conversational AI
Code generation
Text summarization
Image understanding
Audio processing
Reasoning tasks
Agentic workflows

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your understanding of how to deploy and consume AI models in Azure AI Foundry.

For the AI-103 exam, you should understand:

Large language models (LLMs)
Small language models (SLMs)
Code models
Multimodal models
Model deployment concepts
Model consumption patterns
API-based model access
Endpoint configuration
Performance and cost tradeoffs
Model selection strategies
Responsible AI considerations

What Are Large Language Models (LLMs)?

Large language models are advanced AI systems trained on massive datasets.

LLMs can:

Generate text
Summarize documents
Answer questions
Translate languages
Reason across prompts
Support conversational AI

Common LLM Use Cases

Typical use cases include:

AI assistants
Enterprise chatbots
Content generation
Knowledge retrieval
Agent orchestration
Workflow automation

Characteristics of LLMs

LLMs typically provide:

Strong reasoning
Broad general knowledge
Advanced conversational abilities
Complex instruction following

However, they also:

Require more compute
Cost more to run
May introduce higher latency

What Are Small Language Models (SLMs)?

Small language models are lightweight models optimized for:

Faster inference
Lower cost
Lower latency
Edge deployment
Specialized tasks

Common SLM Use Cases

SLMs are often used for:

Classification
Simple chatbots
Mobile applications
Embedded AI
Lightweight assistants

Benefits of Small Models

Advantages include:

Reduced infrastructure cost
Faster response times
Lower resource requirements
Easier deployment at scale

LLM vs SLM Tradeoffs

LLMs

Best for:

Complex reasoning
Broad knowledge
Multi-step tasks

Tradeoffs:

Higher cost
Higher latency
Larger infrastructure requirements

SLMs

Best for:

Lightweight inference
Narrow tasks
Cost-sensitive workloads

Tradeoffs:

Reduced reasoning capability
Smaller context windows
Less flexibility

What Are Code Models?

Code models are specialized AI models trained for software development tasks.

These models can:

Generate code
Explain code
Complete functions
Debug issues
Convert between languages

Common Code Model Use Cases

Typical scenarios include:

Developer copilots
Code generation
Documentation generation
Test generation
Refactoring assistance

Code Model Capabilities

Code models often support:

Multiple programming languages
Natural language prompts
Code reasoning
Syntax understanding

What Are Multimodal Models?

Multimodal models process multiple types of input.

Examples include:

Text and images
Text and audio
Video and text

Multimodal AI Capabilities

Multimodal models may support:

Image understanding
OCR
Visual question answering
Audio transcription
Speech interaction
Video analysis

Common Multimodal Use Cases

Examples include:

AI vision assistants
Document understanding
Medical imaging analysis
Voice assistants
Image captioning

Model Deployment in Azure AI Foundry

Azure AI Foundry enables developers to:

Discover models
Deploy models
Test models
Monitor deployments
Consume models through APIs

Model Catalogs

Azure AI Foundry provides access to:

Foundation models
Open-source models
Specialized models
Multimodal models

Deployment Concepts

A deployment makes a model available through:

APIs
Endpoints
Applications
Agent workflows

Deployment Types

Common deployment options include:

Managed online deployments
Serverless deployments
Real-time inference endpoints
Batch inference deployments

Real-Time Inference

Real-time inference is used for:

Interactive chat
AI assistants
Live applications
Agent workflows

Batch Inference

Batch inference is used for:

Large-scale document processing
Offline analysis
Scheduled workloads
Bulk content generation

Endpoint Configuration

Deployments expose endpoints for application access.

Endpoints may include:

Authentication
Rate limits
Scaling policies
Monitoring settings

Authentication and Authorization

Applications may access models using:

API keys
Managed identities
Microsoft Entra ID
Role-based access control (RBAC)

Consuming Models Through APIs

Applications consume deployed models using:

REST APIs
SDKs
Client libraries

Prompt-Based Interactions

Generative AI applications commonly interact with models through prompts.

Prompts may include:

Instructions
Context
Examples
Retrieved documents

System Prompts

System prompts define:

AI behavior
Tone
Constraints
Safety policies

Model Parameters

Common inference parameters include:

Temperature
Top-p
Max tokens
Frequency penalty
Presence penalty

Temperature

Temperature controls output randomness.

Lower temperature:

More deterministic
More predictable

Higher temperature:

More creative
More variable

Context Windows

Context windows determine how much information a model can process in a request.

Larger context windows support:

Long conversations
Large documents
Multi-document grounding

Streaming Responses

Streaming enables applications to receive responses incrementally.

Benefits include:

Improved user experience
Faster perceived response times

Grounding Models

Grounding improves factual accuracy by providing trusted data.

Grounded applications commonly use:

Vector search
Retrieval-Augmented Generation (RAG)
Enterprise knowledge sources

Model Selection Considerations

Developers should evaluate:

Accuracy
Cost
Latency
Context size
Reasoning ability
Multimodal support
Scalability

Choosing Between Models

Use LLMs When:

Complex reasoning is required
Broad knowledge is needed
Multi-step workflows are involved

Use SLMs When:

Low latency matters
Cost optimization is critical
Tasks are narrow or repetitive

Use Code Models When:

Building developer tools
Generating code
Supporting programming workflows

Use Multimodal Models When:

Images or audio are required
Visual understanding is needed
Mixed media inputs are processed

Scaling Model Deployments

Scaling strategies may include:

Autoscaling
Regional deployments
Load balancing
Rate limiting

Monitoring Deployments

Organizations should monitor:

Latency
Throughput
Token usage
Errors
Safety events
Cost

Cost Optimization

Cost optimization strategies include:

Choosing smaller models
Limiting token usage
Caching responses
Using batch processing

Responsible AI Considerations

Developers should implement:

Safety filters
Guardrails
Content moderation
Monitoring
Human oversight

Multimodal Safety Concerns

Multimodal systems may require:

Image moderation
OCR filtering
Audio moderation
Content safety evaluation

Agentic AI and Model Consumption

AI agents may use:

LLMs for reasoning
SLMs for lightweight tasks
Code models for automation
Multimodal models for perception

Common AI-103 Deployment Scenarios

Scenario 1: Enterprise Chatbot

Requirements:

Strong reasoning
Long conversations
Grounded responses

Recommended Model:

LLM with RAG

Scenario 2: Mobile AI Assistant

Requirements:

Fast responses
Low cost
Lightweight inference

Recommended Model:

Small language model

Scenario 3: Developer Copilot

Requirements:

Code generation
Programming assistance
Syntax awareness

Recommended Model:

Code model

Scenario 4: Image-Aware AI Assistant

Requirements:

Image analysis
OCR
Text generation

Recommended Model:

Multimodal model

Common AI-103 Exam Tips

Understand Model Categories

Know the differences between:

LLMs
SLMs
Code models
Multimodal models

Learn Deployment Concepts

Understand:

Endpoints
Real-time inference
Batch inference
Scaling

Learn Consumption Patterns

Know:

REST APIs
SDKs
Prompt engineering
System prompts

Understand Cost and Performance Tradeoffs

Know how:

Model size affects cost
Context size affects latency
Scaling impacts performance

Summary

Azure AI Foundry enables developers to deploy and consume a wide range of AI models.

For the AI-103 exam, you should understand:

LLMs
Small language models
Code models
Multimodal models
Deployment options
Model consumption patterns
Prompt engineering
Scaling strategies
Cost optimization
Responsible AI controls

Choosing the right model and deployment strategy is essential for building:

Scalable
Reliable
Efficient
Responsible AI solutions

These concepts are foundational for generative AI and agentic systems on Azure.

Practice Exam Questions

Question 1

What is a primary strength of large language models (LLMs)?

A. Minimal compute usage
B. Complex reasoning and broad knowledge
C. Guaranteed factual accuracy
D. Extremely low latency

Answer

B. Complex reasoning and broad knowledge

Explanation

LLMs excel at reasoning, conversation, and broad knowledge tasks.

Question 2

Which model type is best suited for lightweight, low-cost inference?

A. Large language model
B. Small language model
C. Multimodal model
D. Vision transformer only

Answer

B. Small language model

Explanation

SLMs are optimized for lower latency and reduced cost.

Question 3

Which model type is specifically optimized for programming tasks?

A. Vision model
B. Code model
C. Embedding model
D. Speech model

Answer

B. Code model

Explanation

Code models are trained for software development workflows.

Question 4

What is a defining feature of multimodal models?

A. They only process text
B. They process multiple input types
C. They eliminate inference costs
D. They require no prompting

Answer

B. They process multiple input types

Explanation

Multimodal models handle text, images, audio, and other media.

Question 5

Which deployment type is best for interactive AI chat applications?

A. Batch inference
B. Real-time inference
C. Archive deployment
D. Offline storage deployment

Answer

B. Real-time inference

Explanation

Interactive applications require low-latency real-time inference.

Question 6

What does the temperature parameter control?

A. Network throughput
B. Output randomness and creativity
C. Storage replication
D. GPU memory allocation

Answer

B. Output randomness and creativity

Explanation

Temperature affects how deterministic or creative outputs become.

Question 7

Which technique improves factual accuracy by using trusted data sources?

A. GPU scaling
B. Retrieval-Augmented Generation (RAG)
C. Semantic caching
D. Compression indexing

Answer

B. Retrieval-Augmented Generation (RAG)

Explanation

RAG grounds model outputs using retrieved enterprise data.

Question 8

What is a major benefit of streaming responses?

A. Reduced storage costs
B. Faster perceived response times
C. Elimination of monitoring
D. Improved vector indexing

Answer

B. Faster perceived response times

Explanation

Streaming improves user experience during response generation.

Question 9

Which authentication method supports passwordless access to Azure AI services?

A. Static credentials only
B. Managed identities
C. Anonymous access
D. Embedded API secrets in code

Answer

B. Managed identities

Explanation

Managed identities support secure, keyless authentication.

Question 10

Which model type is most appropriate for image understanding and OCR tasks?

A. Small language model
B. Multimodal model
C. Traditional relational database
D. Static rules engine

Answer

B. Multimodal model

Explanation

Multimodal models process images and text together.

Go to the AI-103 Exam Prep Hub main page

AI, AI-103, Microsoft Certification May 25, 2026

Integrate Foundry projects with Continuous Integration and Continuous Deployment (CI/CD) pipelines (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Plan and manage an Azure AI solution (25–30%)
   --> Set up AI solutions in Foundry
      --> Integrate Foundry projects with Continuous Integration and Continuous Deployment (CI/CD) pipelines

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

Modern AI applications and agent-based systems are continuously evolving.

Organizations frequently update:

AI models
Prompts
Agent workflows
APIs
Retrieval systems
Infrastructure
Security configurations

Manual deployment processes are slow, error-prone, and difficult to scale.

To solve these challenges, organizations use:

Continuous Integration (CI)
Continuous Deployment (CD)
Automated testing
Infrastructure-as-Code (IaC)
Automated validation pipelines

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your understanding of how to integrate Azure AI Foundry projects into CI/CD pipelines.

For the AI-103 exam, you should understand:

CI/CD concepts
Azure DevOps pipelines
GitHub Actions workflows
Infrastructure-as-Code
Automated AI deployment workflows
Model versioning
Deployment automation
Testing and validation
Environment management
Rollback strategies
Monitoring deployment health

What Is CI/CD?

CI/CD stands for:

Continuous Integration
Continuous Deployment (or Continuous Delivery)

CI/CD automates software and AI deployment processes.

Continuous Integration (CI)

Continuous Integration focuses on:

Automatically building code
Running automated tests
Validating changes
Detecting issues early

Developers frequently merge changes into shared repositories.

Continuous Deployment (CD)

Continuous Deployment automates:

Application releases
Model deployments
Infrastructure updates
Environment promotion

CD ensures new versions are deployed safely and consistently.

Why CI/CD Matters for AI Solutions

AI systems are more complex than traditional applications because they include:

Models
Prompts
Retrieval pipelines
Vector indexes
Agent workflows
Tool integrations

CI/CD helps ensure:

Reliable deployments
Repeatable processes
Faster releases
Reduced downtime
Safer experimentation

Azure AI Foundry and CI/CD

Azure AI Foundry integrates with:

Azure DevOps
GitHub Actions
Infrastructure-as-Code tools
Azure CLI
SDKs
REST APIs

This enables automated AI workflows.

Source Control for AI Projects

AI projects should use source control systems.

Common repositories include:

GitHub
Azure Repos

What Should Be Stored in Source Control?

Common AI assets include:

Application code
Prompt templates
Agent configurations
Infrastructure definitions
Deployment scripts
Evaluation workflows
Test cases
CI/CD pipeline definitions

What Should NOT Be Stored in Source Control?

Never store:

Secrets
API keys
Passwords
Certificates
Sensitive credentials

Use Azure Key Vault instead.

Azure DevOps

Azure DevOps provides:

Repositories
Build pipelines
Release pipelines
Work tracking
Artifact management

Azure DevOps is commonly used for enterprise AI deployments.

GitHub Actions

GitHub Actions supports:

Automated workflows
Build automation
Testing pipelines
Deployment automation
CI/CD orchestration

GitHub Actions is widely used for AI applications hosted in GitHub repositories.

Infrastructure-as-Code (IaC)

Infrastructure-as-Code automates infrastructure provisioning.

Instead of manually creating resources, infrastructure is defined in code.

Benefits of IaC

IaC provides:

Repeatability
Version control
Consistency
Automation
Reduced configuration drift

Common IaC Tools in Azure

Common Azure IaC tools include:

ARM templates
Bicep
Terraform

Bicep

Bicep is a declarative language for Azure infrastructure.

Used to deploy:

Azure OpenAI resources
Azure AI Search
Storage accounts
Networking resources
Key Vault
App Services

Terraform

Terraform is a multi-cloud Infrastructure-as-Code tool.

Useful for:

Hybrid environments
Multi-cloud deployments
Large enterprise automation

Automating Azure AI Resource Deployment

CI/CD pipelines can automatically provision:

Azure OpenAI
Azure AI Search
Cosmos DB
Azure Functions
App Service
Networking
Monitoring services

Automating Model Deployments

Model deployment pipelines may automate:

Model version selection
Deployment creation
Endpoint configuration
Scaling configuration
Rollback management

Model Versioning

Versioning is critical for AI deployments.

Benefits include:

Safer updates
Rollback support
Testing new versions
Comparing performance

Environment Management

AI solutions commonly use multiple environments.

Typical environments include:

Development
Testing
Staging
Production

Development Environment

Used for:

Experimentation
Initial testing
Prompt development
Rapid iteration

Testing Environment

Used for:

Automated testing
Integration testing
Validation workflows

Staging Environment

Used for:

Final validation
Production-like testing
User acceptance testing

Production Environment

Used for:

Live workloads
Enterprise applications
Customer-facing systems

Production environments require:

Strong monitoring
Security controls
Scalability
High availability

Automated Testing in AI Pipelines

Testing AI systems is more complex than traditional software testing.

AI pipelines should validate:

Functional behavior
Prompt quality
Retrieval quality
Latency
Safety
Reliability

Unit Testing

Unit testing validates:

Individual functions
APIs
Tool integrations
Components

Integration Testing

Integration testing validates interactions between:

Models
APIs
Search systems
Databases
Agents

Prompt Evaluation

Prompt evaluation helps assess:

Response quality
Groundedness
Hallucinations
Relevance
Consistency

Automated Evaluation Pipelines

Evaluation pipelines may measure:

Accuracy
Latency
Token usage
Toxicity
Retrieval precision

Prompt Flow and CI/CD

Prompt Flow can integrate into CI/CD pipelines.

Prompt Flow supports:

Workflow orchestration
Evaluation pipelines
Prompt testing
Tool integration

Deployment Strategies

Safe deployment strategies reduce risk.

Blue-Green Deployments

Blue-green deployments use two environments:

Current production environment
New deployment environment

Traffic switches after validation.

Benefits:

Reduced downtime
Easy rollback
Safer deployments

Canary Deployments

Canary deployments release updates gradually.

Benefits:

Reduced deployment risk
Easier issue detection
Controlled rollout

Rolling Deployments

Rolling deployments update systems incrementally.

Benefits:

Minimal downtime
Gradual infrastructure replacement

Rollback Strategies

Rollback mechanisms are critical.

Rollbacks may restore:

Previous model versions
Prior prompts
Earlier infrastructure states

Deployment Approval Gates

Approval gates help control production releases.

Approvals may be required before:

Production deployment
Model upgrades
Infrastructure changes

Security in CI/CD Pipelines

Security is a major AI-103 topic.

Azure Key Vault Integration

Pipelines should retrieve secrets securely from:

Azure Key Vault

Examples include:

API keys
Connection strings
Certificates

Managed Identities

Managed identities reduce the need for stored credentials.

Benefits:

Improved security
Simplified authentication
Reduced secret exposure

Role-Based Access Control (RBAC)

RBAC limits access to:

Deployments
Resources
Pipelines
Secrets

Monitoring CI/CD Pipelines

Pipelines should monitor:

Build failures
Deployment failures
Performance regressions
AI quality degradation

Azure Monitor

Azure Monitor supports:

Metrics
Alerts
Logging
Diagnostics

Application Insights

Application Insights helps monitor:

API latency
Failures
Dependency performance
User behavior

AI-Specific Monitoring

AI systems should monitor:

Token usage
Hallucination rates
Retrieval quality
Tool execution failures
Prompt performance

Common AI-103 CI/CD Scenarios

Scenario 1: Enterprise AI Copilot

Requirements:

Frequent prompt updates
Safe production releases
Automated testing

Recommended Approach:

GitHub Actions
Prompt Flow evaluations
Canary deployments

Scenario 2: Large-Scale AI Platform

Requirements:

Infrastructure automation
Multi-environment deployment
Enterprise governance

Recommended Approach:

Azure DevOps
Bicep or Terraform
Approval gates

Scenario 3: AI Agent Workflow System

Requirements:

Frequent workflow updates
Tool integration testing
Prompt validation

Recommended Approach:

Automated evaluation pipelines
Integration testing
Blue-green deployment strategy

Cost Optimization in CI/CD

CI/CD pipelines can increase operational costs.

Cost Optimization Strategies

Use Automated Cleanup

Remove:

Temporary environments
Test resources
Unused deployments

Optimize Test Frequency

Run expensive evaluations only when necessary.

Use Smaller Models for Testing

Smaller models reduce:

Token usage
Compute costs
Evaluation expenses

Common AI-103 Exam Tips

Understand CI/CD Fundamentals

Know:

Continuous Integration
Continuous Deployment
Automated testing
Deployment automation

Learn Deployment Strategies

Understand:

Blue-green deployments
Canary deployments
Rolling deployments
Rollback strategies

Know Infrastructure-as-Code Concepts

Understand:

Bicep
Terraform
ARM templates

Understand AI-Specific Testing

AI systems require testing for:

Prompt quality
Groundedness
Safety
Retrieval accuracy
Latency

Summary

Integrating Azure AI Foundry projects with CI/CD pipelines enables organizations to:

Automate deployments
Improve reliability
Increase scalability
Reduce operational risk
Accelerate AI delivery

For the AI-103 exam, you should understand:

CI/CD fundamentals
Azure DevOps pipelines
GitHub Actions workflows
Infrastructure-as-Code
Automated AI deployment strategies
Environment management
AI testing pipelines
Monitoring and observability
Secure deployment practices
Rollback and release strategies

Strong CI/CD practices are essential for building production-grade AI applications and agent-based systems on Azure.

Practice Exam Questions

Question 1

What does CI/CD stand for?

A. Continuous Integration and Continuous Deployment
B. Centralized Integration and Continuous Diagnostics
C. Continuous Inspection and Cloud Deployment
D. Centralized Infrastructure and Cloud Distribution

Answer

A. Continuous Integration and Continuous Deployment

Explanation

CI/CD automates software and AI deployment workflows.

Question 2

Which Azure service is commonly used for enterprise CI/CD pipelines?

A. Azure DevOps
B. Azure Backup
C. Azure DNS
D. Azure Files

Answer

A. Azure DevOps

Explanation

Azure DevOps provides build, release, and deployment pipeline capabilities.

Question 3

Which GitHub feature supports automated workflow execution for deployments?

A. GitHub Actions
B. GitHub Storage
C. GitHub Search
D. GitHub Monitor

Answer

A. GitHub Actions

Explanation

GitHub Actions automates workflows, testing, and deployments.

Question 4

Which deployment strategy uses two environments and switches traffic after validation?

A. Rolling deployment
B. Blue-green deployment
C. Canary deployment
D. Manual deployment

Answer

B. Blue-green deployment

Explanation

Blue-green deployments reduce downtime and simplify rollback.

Question 5

Which Azure service securely stores secrets for CI/CD pipelines?

A. Azure Key Vault
B. Azure Monitor
C. Azure Firewall
D. Azure CDN

Answer

A. Azure Key Vault

Explanation

Azure Key Vault securely stores secrets and credentials.

Question 6

Which Infrastructure-as-Code language is specifically designed for Azure?

A. Bicep
B. SQL
C. JavaScript
D. HTML

Answer

A. Bicep

Explanation

Bicep is a declarative Infrastructure-as-Code language for Azure.

Question 7

What is the primary purpose of canary deployments?

A. Eliminate monitoring
B. Gradually release updates to reduce risk
C. Replace version control
D. Encrypt model endpoints

Answer

B. Gradually release updates to reduce risk

Explanation

Canary deployments expose updates to a subset of users first.

Question 8

Which type of testing validates interactions between models, APIs, and databases?

A. Unit testing
B. Integration testing
C. Syntax testing
D. Deployment testing

Answer

B. Integration testing

Explanation

Integration testing validates component interactions.

Question 9

Which Azure service helps monitor application telemetry and diagnostics?

A. Application Insights
B. Azure DNS
C. Azure Backup
D. Azure Files

Answer

A. Application Insights

Explanation

Application Insights provides telemetry and monitoring capabilities.

Question 10

Which Azure feature reduces the need to store credentials directly in pipelines?

A. Managed identities
B. Public IP addresses
C. Azure CDN
D. Static tokens

Answer

A. Managed identities

Explanation

Managed identities provide secure authentication without storing credentials.

Go to the AI-103 Exam Prep Hub main page

AI, AI-103, Artificial Intelligence (AI), Microsoft Certification May 25, 2026

Configure model and agent deployments (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Plan and manage an Azure AI solution (25–30%)
   --> Set up AI solutions in Foundry
      --> Configure model and agent deployments

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

One of the most important responsibilities for Azure AI developers is configuring and managing model and agent deployments.

Modern AI applications depend on properly configured:

Large Language Models (LLMs)
Embedding models
Multimodal models
AI agents
Retrieval systems
Tool integrations
Orchestration workflows

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your ability to configure AI solutions in Azure AI Foundry and related Azure services.

For the AI-103 exam, you should understand:

Azure OpenAI model deployments
Deployment types
Provisioned throughput
Model versioning
Deployment scaling
Agent configuration
Tool and function integration
Retrieval integration
Security configuration
Monitoring and evaluation
Deployment lifecycle management

What Is a Model Deployment?

A model deployment is a configured instance of an AI model that applications can access through APIs.

Deployments allow developers to:

Choose models
Configure capacity
Control scaling
Manage versions
Apply security controls
Monitor usage

A deployment acts as the operational endpoint for AI inference.

Azure AI Foundry

Azure AI Foundry provides tools and services for:

Deploying AI models
Configuring AI agents
Managing workflows
Evaluating AI systems
Monitoring AI applications

It integrates with:

Azure OpenAI
Azure AI Search
Prompt Flow
Azure AI Content Safety
Azure Functions

Types of Models in Azure AI

Common model types include:

Large Language Models (LLMs)
Small Language Models (SLMs)
Embedding models
Multimodal models
Vision models
Speech models

Large Language Models (LLMs)

LLMs are used for:

Chatbots
AI copilots
Summarization
Reasoning
Tool calling
Content generation

Examples include GPT-based models.

Embedding Models

Embedding models convert content into vector representations.

Used for:

Vector search
Semantic retrieval
Similarity matching
RAG systems

Multimodal Models

Multimodal models process multiple input types such as:

Text
Images
Audio
Documents

Used for:

Image analysis
Visual reasoning
OCR workflows
Multimodal agents

Azure OpenAI Deployments

Azure OpenAI deployments expose models through API endpoints.

Deployment configuration includes:

Model selection
Deployment name
Capacity allocation
Version selection
Region selection
Content filtering settings

Deployment Names

Each deployment has a unique deployment name.

Applications use the deployment name when making API requests.

Example:

gpt4-copilot-prod
embeddings-search-dev

Model Versioning

Models evolve over time.

Versioning helps:

Maintain stability
Test upgrades
Support rollback strategies
Compare model behavior

Why Model Versioning Matters

Different versions may:

Behave differently
Produce different outputs
Affect latency
Affect costs
Impact prompt performance

Deployment Types

Azure AI commonly supports:

Standard deployments
Provisioned throughput deployments

Standard Deployments

Standard deployments use shared infrastructure.

Advantages:

Simpler setup
Lower upfront costs
Flexible usage

Limitations:

Shared capacity
Variable latency under heavy load

Provisioned Throughput Deployments

Provisioned throughput reserves dedicated model capacity.

Advantages:

Predictable performance
Consistent latency
Enterprise-grade scaling

Limitations:

Higher cost
Capacity planning required

When to Use Standard Deployments

Use standard deployments when:

Workloads are moderate
Usage is variable
Cost optimization matters
Development/testing environments are used

When to Use Provisioned Throughput

Use provisioned throughput when:

High traffic is expected
Predictable latency is required
Enterprise SLAs exist
Production copilots are deployed

Scaling Model Deployments

AI deployments must support varying workloads.

Autoscaling

Autoscaling adjusts resources dynamically based on demand.

Benefits:

Improved performance
Better cost efficiency
Reduced manual intervention

Horizontal Scaling

Horizontal scaling adds additional instances or capacity.

Useful for:

High concurrency
Enterprise AI systems
Large-scale chatbots

Latency Considerations

Latency refers to response time.

Factors affecting latency:

Model size
Throughput load
Geographic distance
Retrieval pipelines
Tool execution

Choosing the Correct Model

Choosing the correct model is critical.

Use Larger Models When:

Advanced reasoning is required
Complex workflows exist
High-quality generation matters

Use Smaller Models When:

Cost efficiency matters
Low latency is important
Simpler tasks are performed

Agent Deployments

AI agents combine:

Models
Memory
Retrieval
Tool calling
Workflow orchestration

Agent deployment involves configuring all these components together.

Agent Configuration Components

Common agent configuration elements include:

System prompts
Tool definitions
Function calling
Knowledge sources
Retrieval settings
Memory configuration
Safety settings

System Prompts

System prompts define:

Agent behavior
Role instructions
Response style
Operational constraints

Well-designed system prompts improve:

Reliability
Consistency
Safety

Tool and Function Integration

Agents may use tools such as:

APIs
Databases
Search services
External systems

Function calling enables agents to invoke these tools dynamically.

Retrieval Integration

Many AI agents use Retrieval-Augmented Generation (RAG).

RAG systems commonly integrate:

Azure AI Search
Embedding models
Vector search
Knowledge indexes

Knowledge Sources

Agents may connect to:

Enterprise documents
Databases
APIs
SharePoint
Blob Storage
Internal knowledge bases

Memory Configuration

Agents may use:

Short-term memory
Long-term memory
Semantic memory

Common storage systems include:

Azure Cosmos DB
Azure SQL Database
Azure AI Search

Security Configuration

Security is a major AI-103 exam topic.

Microsoft Entra ID

Microsoft Entra ID supports:

Authentication
Authorization
RBAC
Identity management

Azure Key Vault

Azure Key Vault securely stores:

API keys
Secrets
Certificates
Connection strings

Content Safety Configuration

Azure AI Content Safety helps:

Detect harmful content
Filter unsafe outputs
Apply safety policies

Network Security

Enterprise AI deployments may use:

VNets
Private Endpoints
Firewalls
API gateways

Monitoring Deployments

AI deployments require operational monitoring.

Azure Monitor

Azure Monitor provides:

Metrics
Logging
Alerts
Diagnostics

Application Insights

Application Insights supports:

Telemetry
Request tracing
Error diagnostics
Performance monitoring

Metrics to Monitor

Common metrics include:

Latency
Token usage
Error rates
Throughput
Tool call failures
Retrieval quality

Evaluating AI Deployments

AI systems should be evaluated for:

Accuracy
Groundedness
Safety
Relevance
Reliability

Prompt Flow

Prompt Flow supports:

Workflow orchestration
Prompt chaining
Tool integration
Evaluation pipelines

Prompt Flow is an important AI-103 topic.

CI/CD for AI Deployments

AI deployment pipelines should support:

Automated testing
Version control
Safe releases
Rollbacks

Blue-Green Deployments

Blue-green deployments:

Reduce downtime
Support safer releases
Simplify rollback

Canary Deployments

Canary deployments:

Roll out changes gradually
Reduce deployment risk
Support controlled testing

Common AI-103 Deployment Scenarios

Scenario 1: Enterprise AI Copilot

Requirements:

High concurrency
Secure retrieval
Enterprise search
Low latency

Recommended Configuration:

Provisioned throughput
Azure AI Search
Entra ID
Autoscaling

Scenario 2: Development Chatbot

Requirements:

Low cost
Rapid experimentation
Flexible scaling

Recommended Configuration:

Standard deployment
App Service
Basic monitoring

Scenario 3: AI Agent with Tool Calling

Requirements:

API integrations
Workflow execution
Multi-step reasoning

Recommended Configuration:

Azure OpenAI
Azure Functions
Prompt Flow
Tool definitions

Scenario 4: Enterprise Knowledge Assistant

Requirements:

Grounded responses
Semantic retrieval
Document search

Recommended Configuration:

Embedding models
Azure AI Search
Hybrid search
RAG pipelines

Cost Optimization Considerations

AI deployments can become expensive.

Common Cost Drivers

Token usage
Provisioned throughput
Search indexing
Embedding generation
Large models
High concurrency

Cost Optimization Strategies

Use Smaller Models When Possible

Smaller models reduce:

Latency
Compute costs
Token usage

Optimize Retrieval

Efficient retrieval reduces:

Prompt size
Token costs
Latency

Use Autoscaling

Autoscaling prevents overprovisioning.

Common AI-103 Exam Tips

Understand Deployment Types

Know the differences between:

Standard deployments
Provisioned throughput deployments

Learn Agent Configuration Components

Understand:

System prompts
Tool integration
Retrieval settings
Memory configuration

Know Security Best Practices

Use:

Entra ID
RBAC
Key Vault
Private networking

Understand Monitoring Concepts

Know how to monitor:

Latency
Token usage
Throughput
Errors
AI quality

Summary

Configuring model and agent deployments is a critical skill for Azure AI developers.

For the AI-103 exam, you should understand:

Azure OpenAI deployment configuration
Model versioning
Deployment scaling
Agent architecture
Tool integration
Retrieval integration
Memory configuration
Security controls
Monitoring and evaluation
Deployment lifecycle management

Well-configured deployments improve:

Reliability
Performance
Scalability
Security
Cost efficiency
User experience

These concepts are foundational for building enterprise-grade AI applications and agent-based systems on Azure.

Practice Exam Questions

Question 1

Which deployment type provides dedicated capacity for Azure OpenAI workloads?

A. Shared deployment
B. Provisioned throughput deployment
C. Batch deployment
D. Basic deployment

Answer

B. Provisioned throughput deployment

Explanation

Provisioned throughput reserves dedicated processing capacity.

Question 2

What is the primary purpose of model versioning?

A. Increase storage size
B. Manage model updates and rollback strategies
C. Reduce API authentication
D. Eliminate monitoring

Answer

B. Manage model updates and rollback strategies

Explanation

Versioning helps maintain stability and supports rollback.

Question 3

Which Azure service is MOST commonly used for semantic retrieval in RAG systems?

A. Azure AI Search
B. Azure Backup
C. Azure CDN
D. Azure DNS

Answer

A. Azure AI Search

Explanation

Azure AI Search supports vector and semantic retrieval.

Question 4

What is the purpose of a system prompt in an AI agent?

A. Encrypt embeddings
B. Define agent behavior and instructions
C. Replace APIs
D. Configure storage replication

Answer

B. Define agent behavior and instructions

Explanation

System prompts guide the agent’s role, constraints, and response style.

Question 5

Which Azure service securely stores API keys and secrets?

A. Azure Key Vault
B. Azure Monitor
C. Azure Backup
D. Azure CDN

Answer

A. Azure Key Vault

Explanation

Azure Key Vault securely stores sensitive credentials.

Question 6

Which deployment strategy gradually rolls out updates to a small percentage of users first?

A. Full deployment
B. Canary deployment
C. Offline deployment
D. Batch deployment

Answer

B. Canary deployment

Explanation

Canary deployments reduce deployment risk through gradual rollout.

Question 7

Which type of model is specifically designed for vector generation and semantic similarity?

A. Vision model
B. Embedding model
C. Speech model
D. OCR model

Answer

B. Embedding model

Explanation

Embedding models generate vector representations for semantic retrieval.

Question 8

Which Azure service provides telemetry and request tracing for AI applications?

A. Application Insights
B. Azure DNS
C. Azure Files
D. Azure Firewall

Answer

A. Application Insights

Explanation

Application Insights provides application telemetry and diagnostics.

Question 9

Which feature dynamically adjusts resources based on workload demand?

A. Static allocation
B. Autoscaling
C. Encryption scaling
D. Semantic routing

Answer

B. Autoscaling

Explanation

Autoscaling automatically adjusts capacity based on traffic.

Question 10

Which Azure service is commonly used for workflow orchestration and prompt chaining in AI solutions?

A. Prompt Flow
B. Azure CDN
C. Azure Backup
D. Azure Front Door

Answer

A. Prompt Flow

Explanation

Prompt Flow orchestrates prompts, tools, and AI workflows.

Go to the AI-103 Exam Prep Hub main page

AI, AI-103, Artificial Intelligence (AI), Microsoft Certification May 25, 2026

Choose appropriate deployment options (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Plan and manage an Azure AI solution (25–30%)
   --> Set up AI solutions in Foundry
      --> Choose appropriate deployment options

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

One of the most important responsibilities for Azure AI developers is selecting the correct deployment option for AI applications and agent-based solutions.

Modern AI systems can be deployed in many different ways depending on:

Scalability requirements
Cost constraints
Security requirements
Latency expectations
Geographic distribution
Operational complexity
AI workload patterns
Enterprise governance needs

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your understanding of how to choose appropriate deployment options for:

Generative AI applications
AI agents
APIs
RAG systems
Vector search solutions
Multimodal applications
Enterprise AI systems

For the AI-103 exam, you should understand:

Azure deployment models
Hosting options
Serverless deployments
Containerized deployments
Kubernetes deployments
Regional deployments
High availability strategies
Scaling approaches
CI/CD deployment pipelines
Model deployment considerations
Infrastructure tradeoffs

What Is a Deployment Option?

A deployment option refers to the method used to host and run an AI application or service.

Deployment choices affect:

Performance
Reliability
Cost
Security
Scalability
Maintainability

Choosing the wrong deployment strategy can:

Increase costs
Reduce performance
Complicate maintenance
Create scaling problems

Common Azure AI Deployment Components

AI solutions commonly include:

AI models
APIs
Search systems
Databases
Agent orchestration
Storage systems
Monitoring tools
Security services

Each component may use different deployment approaches.

Azure OpenAI Deployment Options

Azure OpenAI allows developers to deploy:

GPT models
Embedding models
Multimodal models
Fine-tuned models

Deployment considerations include:

Region availability
Throughput requirements
Latency requirements
Cost optimization
Capacity planning

Standard Deployments

What Are Standard Deployments?

Standard deployments provide shared model hosting infrastructure.

Advantages:

Lower operational complexity
Managed infrastructure
Easier setup

Disadvantages:

Shared capacity
Potential throughput limitations

Provisioned Throughput Deployments

What Is Provisioned Throughput?

Provisioned throughput reserves dedicated processing capacity.

Advantages:

Predictable performance
Dedicated throughput
Lower latency consistency

Disadvantages:

Higher cost
Capacity planning required

When to Use Provisioned Throughput

Use provisioned throughput when:

Workloads are high volume
Predictable latency is critical
Enterprise SLAs are required
Large-scale copilots are deployed

Serverless Deployment Options

What Is Serverless?

Serverless computing automatically manages infrastructure.

Developers focus on code instead of servers.

Azure Functions

Azure Functions provides event-driven serverless compute.

Common AI use cases:

Tool calling
Workflow execution
API processing
Lightweight orchestration
Event-triggered AI actions

Advantages of Azure Functions

Automatic scaling
Pay-per-use pricing
Rapid deployment
Minimal infrastructure management

Limitations of Azure Functions

Execution duration limits
Cold starts
Less suitable for large persistent workloads

When to Use Azure Functions

Use Azure Functions when:

Workloads are event-driven
Execution is lightweight
Cost optimization is important
Rapid scaling is required

Azure Container Apps

Azure Container Apps provides serverless container hosting.

Useful for:

AI middleware
APIs
Agent orchestration
Background workers
Lightweight microservices

Advantages of Container Apps

Simplified container deployment
Autoscaling support
Event-driven scaling
Lower operational overhead than Kubernetes

Kubernetes Deployments

Azure Kubernetes Service (AKS)

AKS provides enterprise-grade container orchestration.

Common AI uses:

Multi-agent systems
Large-scale AI platforms
Distributed AI services
Complex orchestration
High-volume APIs

Advantages of AKS

High scalability
Advanced orchestration
Fine-grained control
Container portability
Enterprise-grade deployments

Limitations of AKS

Higher operational complexity
More infrastructure management
Requires Kubernetes expertise

When to Use AKS

Use AKS when:

Large-scale deployments exist
Multiple microservices interact
High traffic is expected
Advanced orchestration is needed

Platform-as-a-Service (PaaS) Deployments

Azure App Service

Azure App Service hosts:

Web apps
APIs
AI front ends
Lightweight enterprise applications

Advantages of App Service

Managed platform
Easy deployment
Autoscaling support
Simplified maintenance

When to Use App Service

Use App Service when:

Hosting AI web applications
Managing APIs
Rapid development is needed
Full Kubernetes orchestration is unnecessary

Edge and Hybrid Deployments

Some AI workloads require local or hybrid deployments.

Reasons include:

Low latency
Regulatory requirements
Limited connectivity
On-premises data processing

Azure Arc

Azure Arc extends Azure management to:

On-premises systems
Multi-cloud environments
Edge deployments

Useful for hybrid AI environments.

Deployment Considerations for AI Agents

AI agents often require multiple deployment layers.

Examples include:

LLM hosting
Retrieval systems
Tool execution services
Workflow orchestration
Persistent memory systems

Multi-Service Architectures

AI agents commonly use:

Azure OpenAI
Azure AI Search
Azure Functions
Cosmos DB
APIs
Orchestration workflows

Different components may use different deployment options.

Geographic Deployment Considerations

AI systems may require global deployment strategies.

Regional Deployments

Deploying resources in a specific region helps:

Reduce latency
Meet compliance requirements
Improve user experience

Multi-Region Deployments

Multi-region deployments improve:

Availability
Disaster recovery
Global performance

Availability Zones

Availability Zones provide redundancy across isolated datacenters.

Benefits include:

Higher uptime
Fault tolerance
Improved resilience

High Availability Design

Enterprise AI applications often require:

Redundant infrastructure
Automatic failover
Load balancing
Disaster recovery

Load Balancing

Azure Load Balancer and Azure Application Gateway distribute traffic across services.

Benefits:

Scalability
High availability
Traffic optimization

Autoscaling

Autoscaling dynamically adjusts infrastructure based on demand.

Supported by:

AKS
Azure Functions
App Service
Container Apps

Deployment Security Considerations

Security is a major AI-103 exam topic.

Microsoft Entra ID

Microsoft Entra ID supports:

Authentication
Authorization
Identity management
RBAC

Azure Key Vault

Azure Key Vault securely stores:

Secrets
API keys
Certificates
Connection strings

Private Endpoints

Private Endpoints provide secure private connectivity between Azure services.

Useful for:

Enterprise AI systems
Sensitive data workloads
Compliance-driven deployments

CI/CD for AI Deployments

What Is CI/CD?

CI/CD stands for:

Continuous Integration
Continuous Deployment

CI/CD automates:

Testing
Deployment
Validation
Release management

Azure DevOps

Azure DevOps supports:

Build pipelines
Release pipelines
Source control
Automated deployments

GitHub Actions

GitHub Actions supports:

Workflow automation
CI/CD pipelines
Deployment automation

Commonly used for AI application deployments.

Blue-Green Deployments

Blue-green deployments reduce downtime during releases.

How it works:

One environment remains active
A second environment receives updates
Traffic shifts after validation

Benefits:

Safer releases
Reduced downtime
Easier rollback

Canary Deployments

Canary deployments release updates gradually to a small percentage of users.

Benefits:

Reduced deployment risk
Easier issue detection
Safer experimentation

Monitoring Deployment Health

AI deployments should monitor:

Latency
Throughput
Token usage
Errors
Model failures
Tool call failures
Retrieval quality

Azure Monitor

Azure Monitor provides:

Metrics
Logging
Alerts
Diagnostics

Application Insights

Application Insights supports:

Telemetry
Request tracing
Dependency tracking
Error diagnostics

Cost Optimization Considerations

AI deployments can become expensive.

Common Cost Drivers

Token consumption
GPU usage
High-scale orchestration
Search indexing
Storage
Data transfer

Cost Optimization Strategies

Use Smaller Models When Appropriate

Smaller models reduce:

Compute costs
Token usage
Latency

Use Serverless When Appropriate

Serverless deployments reduce idle infrastructure costs.

Use Autoscaling

Autoscaling prevents overprovisioning.

Common AI-103 Deployment Scenarios

Scenario 1: Enterprise AI Chatbot

Requirements:

High availability
Secure authentication
Enterprise search

Recommended Deployment:

Azure OpenAI
App Service
Azure AI Search
Entra ID

Scenario 2: Large-Scale AI Agent Platform

Requirements:

Multiple AI agents
Heavy orchestration
High concurrency

Recommended Deployment:

AKS
Azure Functions
Cosmos DB
Prompt Flow

Scenario 3: Lightweight AI API

Requirements:

Rapid deployment
Cost optimization
Moderate scale

Recommended Deployment:

Azure Functions
Container Apps

Scenario 4: Global AI Application

Requirements:

Global users
Low latency
Disaster recovery

Recommended Deployment:

Multi-region deployment
Availability Zones
Load balancing

Common AI-103 Exam Tips

Understand Deployment Tradeoffs

Know when to use:

App Service vs AKS
Functions vs Containers
Standard vs Provisioned Throughput

Know High Availability Concepts

Understand:

Availability Zones
Multi-region deployments
Load balancing
Failover strategies

Learn Security Best Practices

Know how to use:

Entra ID
RBAC
Key Vault
Private Endpoints

Understand Agent Deployment Needs

AI agents commonly require:

Tool orchestration
Retrieval systems
Persistent memory
API integrations

Summary

Choosing the correct deployment option is critical for successful AI applications and agent-based systems.

For the AI-103 exam, you should understand:

Azure deployment models
Serverless deployment options
Kubernetes deployments
PaaS hosting options
Multi-region architectures
High availability design
Security considerations
CI/CD pipelines
Scaling strategies
AI deployment tradeoffs

Strong deployment architecture skills help ensure AI systems are:

Reliable
Scalable
Secure
Cost-effective
Maintainable

Practice Exam Questions

Question 1

Which Azure service is BEST suited for enterprise-scale container orchestration for AI applications?

A. Azure App Service
B. Azure Kubernetes Service (AKS)
C. Azure DNS
D. Azure Backup

Answer

B. Azure Kubernetes Service (AKS)

Explanation

AKS provides enterprise-grade container orchestration and scalability.

Question 2

Which deployment option provides dedicated throughput capacity for Azure OpenAI models?

A. Shared deployment
B. Provisioned throughput deployment
C. Consumption deployment
D. Basic deployment

Answer

B. Provisioned throughput deployment

Explanation

Provisioned throughput reserves dedicated model processing capacity.

Question 3

Which Azure service is MOST appropriate for lightweight event-driven AI workflows?

A. Azure Functions
B. Azure Firewall
C. Azure Backup
D. Azure CDN

Answer

A. Azure Functions

Explanation

Azure Functions supports serverless event-driven execution.

Question 4

What is the primary benefit of Availability Zones?

A. Lower token usage
B. Increased embedding size
C. Improved fault tolerance
D. Reduced API authentication

Answer

C. Improved fault tolerance

Explanation

Availability Zones provide redundancy across isolated datacenters.

Question 5

Which Azure service is commonly used to host AI web applications and APIs with minimal infrastructure management?

A. Azure App Service
B. Azure Load Balancer
C. Azure DNS
D. Azure Monitor

Answer

A. Azure App Service

Explanation

Azure App Service is a managed PaaS platform for hosting web applications and APIs.

Question 6

Which deployment strategy gradually releases updates to a subset of users first?

A. Blue-green deployment
B. Canary deployment
C. Full rollback deployment
D. Batch deployment

Answer

B. Canary deployment

Explanation

Canary deployments release updates incrementally to reduce risk.

Question 7

Which Azure service securely stores API keys and secrets for AI applications?

A. Azure Key Vault
B. Azure CDN
C. Azure Firewall
D. Azure Backup

Answer

A. Azure Key Vault

Explanation

Azure Key Vault securely manages secrets and credentials.

Question 8

Which Azure deployment option is MOST appropriate for serverless container hosting?

A. Azure Container Apps
B. Azure Backup
C. Azure DNS
D. Azure Files

Answer

A. Azure Container Apps

Explanation

Azure Container Apps provides simplified serverless container deployment.

Question 9

Which deployment architecture improves global application availability and disaster recovery?

A. Single-region deployment
B. Multi-region deployment
C. Local-only deployment
D. Single-container deployment

Answer

B. Multi-region deployment

Explanation

Multi-region deployments improve resilience and geographic performance.

Question 10

Which Azure monitoring service provides application telemetry and request diagnostics?

A. Application Insights
B. Azure CDN
C. Azure DNS
D. Azure Policy

Answer

A. Application Insights

Explanation

Application Insights provides monitoring and telemetry for applications.

Go to the AI-103 Exam Prep Hub main page

AI, AI-103, Artificial Intelligence (AI), Microsoft Certification May 25, 2026

Design Azure infrastructure for AI Apps and agent-based solutions (AI-103 Exam Prep)

This post is a part of the AI-103: Develop AI Apps and Agents on Azure Exam Prep Hub. 
This topic falls under these sections:
Plan and manage an Azure AI solution (25–30%)
   --> Set up AI solutions in Foundry
      --> Design Azure infrastructure for AI Apps and agent-based solutions

Note that there are 10 practice questions (with answers and explanations) at the end of each section to help you solidify your knowledge of the material. Also, there are 2 practice tests with 60 questions each available from the hub's main page below the exam topics section.

Introduction

Designing infrastructure for AI applications and agent-based systems is one of the most important responsibilities for Azure AI developers.

Modern AI solutions are not simply standalone models. They are distributed cloud systems that combine:

AI services
APIs
Databases
Search systems
Storage
Networking
Security controls
Monitoring systems
Agent orchestration components

The AI-103: Develop AI Apps and Agents on Azure certification exam tests your ability to design Azure infrastructure that supports:

Generative AI applications
AI agents
Retrieval-Augmented Generation (RAG)
Vector search
Multimodal AI systems
Scalable AI architectures
Secure enterprise AI deployments

For the AI-103 exam, you should understand:

Core Azure infrastructure services
AI architecture patterns
Scalability and performance design
Networking and security
Identity and access management
Storage and databases
Monitoring and observability
Cost optimization
High availability and disaster recovery
Infrastructure choices for AI agents

Core Components of AI Infrastructure

AI applications commonly require multiple infrastructure layers.

Typical components include:

AI model services
Compute resources
Storage systems
Search and retrieval systems
Networking components
Security services
Monitoring systems
Workflow orchestration
API management
Identity management

Azure AI Services Layer

Azure OpenAI

Azure OpenAI provides:

Large Language Models (LLMs)
Embedding models
Multimodal models
Conversational AI capabilities

Azure OpenAI is commonly used for:

AI copilots
Chatbots
AI agents
Summarization
Content generation
Tool calling

Azure AI Search

Azure AI Search supports:

Vector search
Semantic search
Hybrid search
Enterprise retrieval
RAG architectures

It is commonly used for:

Knowledge grounding
Enterprise search
AI assistant retrieval

Azure AI Vision

Azure AI Vision provides:

OCR
Image analysis
Object detection
Caption generation
Visual understanding

Azure AI Document Intelligence

Azure AI Document Intelligence supports:

Invoice extraction
Form processing
Layout analysis
OCR workflows
Structured document extraction

Compute Infrastructure for AI Applications

Azure App Service

Azure App Service is commonly used to host:

Web applications
AI front ends
APIs
Lightweight AI services

Advantages:

Managed platform
Easy scaling
Simplified deployment

Azure Kubernetes Service (AKS)

AKS provides container orchestration for:

Large-scale AI applications
Microservices
Agent orchestration systems
Distributed AI workloads

Advantages:

High scalability
Container management
Advanced orchestration
Enterprise-grade deployments

When to Use AKS

Use AKS when:

Complex orchestration is required
Multiple services interact
High scalability is needed
Microservice architectures are used

Azure Functions

Azure Functions provides serverless compute.

Common AI use cases:

Tool execution
Event-driven workflows
API integrations
Lightweight processing
Agent tool calling

Advantages:

Pay-per-use pricing
Automatic scaling
Fast development

Azure Container Apps

Azure Container Apps provides simplified container hosting.

Useful for:

API services
AI middleware
Lightweight agent services
Event-driven AI components

Choosing the Correct Compute Service

Use Azure App Service When:

Hosting simple AI web apps
Managing APIs
Rapid deployment is needed

Use AKS When:

Large-scale orchestration is required
Complex microservices exist
Advanced scalability is necessary

Use Azure Functions When:

Event-driven execution is needed
Tool calling is required
Lightweight compute is sufficient

Use Azure Container Apps When:

Container simplicity is preferred
Serverless containers are desired

Storage Infrastructure

AI systems often require multiple storage solutions.

Azure Blob Storage

Azure Blob Storage supports:

Document storage
Training data
Images
Videos
Logs
AI datasets

Common AI uses:

RAG document storage
Knowledge repositories
Media storage

Azure Cosmos DB

Azure Cosmos DB provides:

Globally distributed NoSQL storage
Low-latency access
High scalability

Common AI uses:

Agent memory
Session storage
User profiles
Conversation history

Azure SQL Database

Azure SQL Database supports:

Structured enterprise data
Relational workloads
Transactional systems

Common AI uses:

Enterprise integration
Business systems
Structured metadata

Vector Storage

Vector-enabled storage supports:

Embedding storage
Similarity search
Semantic retrieval

Common services include:

Azure AI Search
Azure Cosmos DB
Azure SQL Database

Networking Infrastructure

AI solutions require secure and scalable networking.

Virtual Networks (VNets)

VNets provide:

Network isolation
Secure communication
Private connectivity

Use VNets when:

Enterprise security is required
Private networking is necessary
Sensitive data is involved

Private Endpoints

Private Endpoints allow Azure services to be accessed privately through VNets.

Benefits:

Improved security
Reduced public exposure
Enterprise compliance support

API Management

Azure API Management helps:

Secure APIs
Throttle requests
Monitor API usage
Apply policies
Manage agent APIs

This is important for:

AI agents
Tool integrations
Enterprise API governance

Load Balancing

Azure Load Balancer and Application Gateway help:

Distribute traffic
Improve availability
Scale AI applications

Identity and Security

Security is a major AI-103 exam topic.

Microsoft Entra ID

Microsoft Entra ID provides:

Authentication
Authorization
Identity management
Role-based access control (RBAC)

AI applications use Entra ID for:

User authentication
API access control
Secure enterprise integration

Role-Based Access Control (RBAC)

RBAC ensures users and services only access authorized resources.

Examples:

Restricting AI model access
Controlling storage access
Securing search indexes

Azure Key Vault

Azure Key Vault stores:

Secrets
API keys
Certificates
Connection strings

Never hardcode secrets in AI applications.

Azure AI Content Safety

Azure AI Content Safety helps:

Detect harmful content
Filter unsafe outputs
Support responsible AI practices

Monitoring and Observability

AI systems require monitoring for:

Reliability
Performance
Cost
Failures
Hallucinations
API latency

Azure Monitor

Azure Monitor collects:

Metrics
Logs
Alerts
Performance data

Application Insights

Application Insights supports:

Application telemetry
Request tracing
Error tracking
Dependency monitoring

Useful for:

AI apps
APIs
Agent workflows

Logging AI Systems

AI systems should log:

Prompts
Responses
Errors
Tool calls
Latency
Retrieval quality

Logging helps:

Troubleshooting
Auditing
Evaluation
Compliance

Scalability Design

AI applications may experience:

High traffic
Large token volumes
Heavy retrieval workloads
Concurrent agent operations

Infrastructure must scale effectively.

Horizontal Scaling

Horizontal scaling adds more instances.

Examples:

Additional API servers
More containers
More worker nodes

Vertical Scaling

Vertical scaling increases resource capacity.

Examples:

More CPU
More memory
Larger VM sizes

Autoscaling

Autoscaling dynamically adjusts resources based on demand.

Common services supporting autoscaling:

AKS
Azure Functions
App Service
Container Apps

High Availability and Disaster Recovery

Enterprise AI systems require resilience.

Availability Zones

Availability Zones improve fault tolerance.

Benefits:

Redundancy
Improved uptime
Reduced outage risk

Geo-Redundancy

Geo-redundancy replicates data across regions.

Useful for:

Disaster recovery
Business continuity
Global applications

Backup and Recovery

AI systems should back up:

Knowledge indexes
Databases
Configuration data
Logs
Agent memory

Infrastructure for AI Agents

AI agents often require additional infrastructure components.

Agent Orchestration

AI agents may require orchestration services such as:

Prompt Flow
Azure Functions
Logic Apps
AKS workflows

Retrieval Infrastructure

Agent systems commonly use:

Azure AI Search
Embeddings
Vector indexes
RAG pipelines

Persistent Memory Infrastructure

Persistent memory may use:

Azure Cosmos DB
Azure SQL Database
Blob Storage

Tool Integration Infrastructure

Agents often integrate with:

REST APIs
Databases
External SaaS systems
Enterprise workflows

Common AI-103 Architecture Scenarios

Scenario 1: Enterprise AI Copilot

Requirements:

Conversational AI
Enterprise search
Secure authentication
Document retrieval

Recommended Infrastructure:

Azure OpenAI
Azure AI Search
Entra ID
Blob Storage
App Service

Scenario 2: Large-Scale Multi-Agent System

Requirements:

Multiple AI agents
High scalability
Distributed orchestration

Recommended Infrastructure:

AKS
Azure Functions
Prompt Flow
Cosmos DB

Scenario 3: AI Invoice Processing Solution

Requirements:

OCR
Document extraction
Workflow automation

Recommended Infrastructure:

Azure AI Document Intelligence
Blob Storage
Logic Apps
Azure Functions

Scenario 4: Global AI Chat Platform

Requirements:

Global availability
High concurrency
Disaster recovery

Recommended Infrastructure:

Geo-redundant storage
Availability Zones
Load balancing
Autoscaling

Cost Optimization Considerations

AI infrastructure can become expensive.

Common Cost Drivers

Token usage
Vector storage
GPU workloads
Data transfer
Search indexing
High-scale orchestration

Cost Optimization Strategies

Use Smaller Models When Appropriate

Smaller models reduce:

Compute usage
Token costs
Latency

Use Autoscaling

Autoscaling reduces idle resource costs.

Optimize Retrieval Pipelines

Efficient chunking and indexing reduce:

Search costs
Storage requirements
Retrieval latency

Common AI-103 Exam Tips

Understand Infrastructure Tradeoffs

Know when to use:

AKS vs App Service
Functions vs Containers
Cosmos DB vs SQL Database

Learn Security Best Practices

Know how to use:

Entra ID
RBAC
Key Vault
Private Endpoints

Understand RAG Infrastructure

RAG commonly uses:

Azure OpenAI
Azure AI Search
Embeddings
Storage systems

Know Agent Infrastructure Patterns

AI agents commonly require:

Workflow orchestration
Tool integration
Persistent memory
Retrieval systems

Summary

Designing Azure infrastructure for AI applications requires balancing:

Scalability
Security
Performance
Cost
Reliability
Maintainability

For the AI-103 exam, you should understand:

Azure AI service architecture
Compute options
Storage design
Networking and security
Monitoring and observability
High availability
Agent infrastructure patterns
RAG infrastructure
Infrastructure scaling strategies

Strong infrastructure design skills are essential for deploying production-grade AI apps and agent-based systems on Azure.

Practice Exam Questions

Question 1

Which Azure service is MOST appropriate for enterprise vector search and RAG retrieval?

A. Azure AI Search
B. Azure Backup
C. Azure CDN
D. Azure DNS

Answer

A. Azure AI Search

Explanation

Azure AI Search supports vector search, semantic search, and retrieval for RAG systems.

Question 2

Which Azure compute service is BEST suited for large-scale containerized AI microservices?

A. Azure App Service
B. Azure Kubernetes Service (AKS)
C. Azure Files
D. Azure CDN

Answer

B. Azure Kubernetes Service (AKS)

Explanation

AKS provides advanced container orchestration and scalability.

Question 3

Which Azure service is MOST appropriate for storing API keys and secrets securely?

A. Azure Key Vault
B. Azure Monitor
C. Azure DNS
D. Azure Load Balancer

Answer

A. Azure Key Vault

Explanation

Azure Key Vault securely stores secrets, certificates, and keys.

Question 4

Which Azure service provides serverless execution for lightweight AI workflows and tool calling?

A. Azure Functions
B. Azure Backup
C. Azure CDN
D. Azure Firewall

Answer

A. Azure Functions

Explanation

Azure Functions supports event-driven serverless compute.

Question 5

What is the primary purpose of Availability Zones?

A. Reduce token usage
B. Improve fault tolerance and uptime
C. Replace backups
D. Encrypt embeddings

Answer

B. Improve fault tolerance and uptime

Explanation

Availability Zones provide redundancy across isolated datacenter locations.

Question 6

Which Azure service is MOST commonly used for globally distributed NoSQL storage in AI applications?

A. Azure Cosmos DB
B. Azure DNS
C. Azure Files
D. Azure CDN

Answer

A. Azure Cosmos DB

Explanation

Azure Cosmos DB provides scalable globally distributed NoSQL storage.

Question 7

Which Azure networking feature enables private access to Azure services from a VNet?

A. Private Endpoint
B. Public IP
C. Load Balancer
D. Traffic Manager

Answer

A. Private Endpoint

Explanation

Private Endpoints provide secure private connectivity.

Question 8

Which Azure monitoring service provides application telemetry and request tracing?

A. Application Insights
B. Azure CDN
C. Azure Policy
D. Azure ExpressRoute

Answer

A. Application Insights

Explanation

Application Insights provides telemetry and diagnostics for applications.

Question 9

Which Azure identity service provides authentication and RBAC support for AI applications?

A. Microsoft Entra ID
B. Azure CDN
C. Azure Firewall
D. Azure Front Door

Answer

A. Microsoft Entra ID

Explanation

Microsoft Entra ID provides identity and access management.

Question 10

Which scaling strategy adds additional instances to support increased AI workload demand?

A. Vertical scaling
B. Horizontal scaling
C. Encryption scaling
D. Semantic scaling

Answer

B. Horizontal scaling

Explanation

Horizontal scaling adds more instances to distribute workloads.

Go to the AI-103 Exam Prep Hub main page