Category: Agentic AI

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:

  1. Application
  2. Authentication layer
  3. Foundry project endpoint
  4. 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

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

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

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:

  1. User submits request
  2. Model determines tool requirement
  3. Model generates function call
  4. External tool executes
  5. Results return to model
  6. 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:

  1. Retrieve customer data
  2. Analyze account status
  3. Generate recommendations
  4. 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