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

Define agent roles, goals, conversation-tracking approach, and tool schemas (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 agents by using Foundry
      --> Define agent roles, goals, conversation-tracking approach, and tool schemas

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

AI agents are rapidly becoming one of the most important components of modern AI systems.

Unlike basic chatbots, agents can:

  • Reason through tasks
  • Maintain context
  • Use tools
  • Execute workflows
  • Coordinate multistep actions
  • Interact with external systems

Azure AI Foundry provides tools and frameworks for building agentic systems.

For the AI-103: Develop AI Apps and Agents on Azure certification exam, understanding agent design principles is critical.

This topic focuses on:

  • Agent roles
  • Agent goals
  • Conversation tracking
  • Tool schemas
  • Tool orchestration
  • State management
  • Memory design
  • Workflow coordination

What Is an AI Agent?

An AI agent is an AI system capable of:

  • Understanding objectives
  • Making decisions
  • Using tools
  • Maintaining context
  • Performing actions
  • Adapting to changing inputs

Agents are more autonomous than standard prompt-response systems.

Characteristics of AI Agents

Agents commonly include:

  • Reasoning
  • Planning
  • Memory
  • Tool usage
  • Workflow orchestration
  • Goal-oriented behavior

Agent Roles

An agent role defines:

  • The agent’s responsibilities
  • Behavioral expectations
  • Scope of operation
  • Allowed actions

Why Agent Roles Matter

Clearly defined roles help:

  • Improve consistency
  • Reduce unsafe behavior
  • Prevent scope creep
  • Improve reliability

Examples of Agent Roles

Examples include:

  • Customer support assistant
  • Financial analyst
  • Research assistant
  • Scheduling coordinator
  • Coding assistant
  • IT operations assistant

Specialized vs General-Purpose Agents

Specialized Agents

Focused on narrow tasks.

Benefits:

  • Higher reliability
  • Better governance
  • Easier evaluation

General-Purpose Agents

Handle broad tasks.

Benefits:

  • Greater flexibility
  • Wider applicability

Tradeoff:

  • Increased complexity and risk

Defining Agent Goals

Goals define:

  • Desired outcomes
  • Success criteria
  • Task objectives

Goal-Oriented Design

Good goals are:

  • Clear
  • Measurable
  • Constrained
  • Actionable

Examples of Agent Goals

Examples include:

  • Resolve customer tickets
  • Retrieve accurate company policies
  • Generate code suggestions
  • Schedule meetings
  • Summarize documents

Constraints in Goal Design

Goals should include:

  • Safety boundaries
  • Compliance rules
  • Tool restrictions
  • Escalation conditions

Agent Instructions and System Prompts

Agents typically receive:

  • System instructions
  • Behavioral guidance
  • Operational constraints

These instructions influence agent behavior.

Conversation Tracking

Conversation tracking maintains:

  • Dialogue history
  • User context
  • Workflow state
  • Interaction continuity

Why Conversation Tracking Matters

Without conversation tracking:

  • Agents lose context
  • Responses become inconsistent
  • Multistep workflows fail

Short-Term Conversation Memory

Short-term memory may store:

  • Recent prompts
  • Recent responses
  • Current workflow state

Long-Term Memory

Long-term memory may store:

  • User preferences
  • Historical interactions
  • Persistent knowledge

Session State Management

State management tracks:

  • Current tasks
  • Workflow progress
  • Tool outputs
  • Active context

Stateless vs Stateful Agents

Stateless Agents

Do not retain context between interactions.

Benefits:

  • Simpler design
  • Lower storage requirements

Stateful Agents

Maintain conversation history and workflow state.

Benefits:

  • Better continuity
  • Improved multistep reasoning

Context Window Management

LLMs have limited context windows.

Applications may need to:

  • Trim conversation history
  • Summarize prior interactions
  • Retrieve external memory

Memory Strategies

Common memory strategies include:

  • Rolling conversation windows
  • Summarization memory
  • Vector memory
  • Persistent storage

Retrieval-Augmented Memory

Agents may retrieve:

  • Historical conversations
  • Knowledge documents
  • Workflow data

This improves continuity.

Conversation Persistence

Persistent conversation storage may use:

  • Databases
  • Search indexes
  • Vector stores

Tool Usage in Agent Systems

Agents often interact with:

  • APIs
  • Databases
  • Search systems
  • External applications
  • Workflow services

What Is a Tool Schema?

A tool schema defines:

  • Tool name
  • Purpose
  • Input parameters
  • Output structure
  • Validation rules

Purpose of Tool Schemas

Tool schemas help:

  • Standardize interactions
  • Reduce ambiguity
  • Improve reliability
  • Enable function calling

Tool Schema Components

Tool schemas commonly include:

  • Function name
  • Description
  • Parameters
  • Data types
  • Required fields

Example Tool Schema

Example:

  • Tool: GetWeather
  • Inputs:
    • City name
    • Date
  • Output:
    • Temperature
    • Forecast

Structured Tool Invocation

Structured tool schemas allow agents to:

  • Generate valid requests
  • Interact predictably with systems
  • Reduce execution failures

Function Calling

Function calling enables models to:

  • Invoke external tools
  • Execute structured operations
  • Retrieve external data

Tool Selection Logic

Agents may decide:

  • Whether a tool is needed
  • Which tool to invoke
  • How to sequence tool calls

Multi-Tool Workflows

Complex agents may use:

  • Multiple tools
  • Sequential workflows
  • Conditional branching

Tool Access Controls

Organizations may restrict:

  • Which tools agents can use
  • When tools can be invoked
  • Which users may trigger actions

Safety Considerations for Tool Usage

Improper tool usage can:

  • Leak data
  • Execute unsafe actions
  • Cause workflow failures

Human Approval Workflows

Some actions may require:

  • Human review
  • Approval checkpoints
  • Escalation workflows

Agent Planning

Agents may perform:

  • Task decomposition
  • Sequential planning
  • Goal prioritization

Multistep Reasoning

Agents may:

  • Gather information
  • Use tools
  • Analyze results
  • Generate conclusions

Orchestration Frameworks

Orchestration frameworks coordinate:

  • Agent logic
  • Tool execution
  • Workflow progression
  • State transitions

Error Handling in Agents

Agents should handle:

  • Invalid tool outputs
  • API failures
  • Missing data
  • Ambiguous user requests

Monitoring Agent Behavior

Organizations should monitor:

  • Tool usage
  • Conversation quality
  • Safety violations
  • Goal completion rates

Trace Logging

Trace logs may capture:

  • Prompt sequences
  • Tool calls
  • Workflow decisions
  • Agent reasoning steps

Evaluation of Agent Systems

Organizations should evaluate:

  • Goal completion
  • Accuracy
  • Relevance
  • Safety
  • Tool reliability

Governance and Compliance

Enterprise agent systems may require:

  • Access controls
  • Audit logging
  • Compliance policies
  • Responsible AI governance

Real-World Scenario

Scenario: Enterprise IT Support Agent

Requirements:

  • Resolve common IT requests
  • Access ticketing systems
  • Maintain user context
  • Escalate high-risk actions

Recommended Design:

  • Specialized support role
  • Defined goals
  • Stateful conversation tracking
  • Structured tool schemas
  • Human approval workflows

Common AI-103 Exam Tips

Understand Agent Roles

Know:

  • Specialized vs general-purpose agents
  • Role boundaries
  • Behavioral constraints

Learn Conversation Tracking Concepts

Understand:

  • Stateful vs stateless agents
  • Memory approaches
  • Context management

Understand Tool Schemas

Know:

  • Function definitions
  • Parameters
  • Structured tool invocation
  • Function calling

Learn Governance Concepts

Understand:

  • Tool access controls
  • Human approvals
  • Audit logging
  • Safety constraints

Summary

Agent design is a core part of modern AI systems.

For the AI-103 exam, you should understand:

  • Agent roles
  • Goal-oriented behavior
  • Conversation tracking
  • Memory management
  • Stateful workflows
  • Tool schemas
  • Function calling
  • Tool orchestration
  • Workflow planning
  • Safety controls
  • Human approvals
  • Monitoring and governance

These concepts are foundational for building secure, scalable, and reliable agentic systems using Azure AI Foundry.

Practice Exam Questions

Question 1

What is the primary purpose of an agent role?

A. Increase GPU utilization
B. Define responsibilities and behavioral boundaries
C. Eliminate tool usage
D. Remove workflow orchestration

Answer

B. Define responsibilities and behavioral boundaries

Explanation

Agent roles establish scope, expectations, and operational constraints.

Question 2

Why are clearly defined agent goals important?

A. They eliminate monitoring
B. They provide measurable objectives and task direction
C. They reduce storage requirements only
D. They remove authentication needs

Answer

B. They provide measurable objectives and task direction

Explanation

Goals help agents focus on desired outcomes.

Question 3

What is the purpose of conversation tracking?

A. Increase vector dimensions
B. Maintain context and workflow continuity
C. Disable memory systems
D. Remove APIs

Answer

B. Maintain context and workflow continuity

Explanation

Conversation tracking preserves interaction history and state.

Question 4

What is a key benefit of stateful agents?

A. They avoid all storage requirements
B. They maintain continuity across interactions
C. They eliminate workflows
D. They remove tool schemas

Answer

B. They maintain continuity across interactions

Explanation

Stateful agents retain memory and conversation context.

Question 5

What is a tool schema?

A. A GPU optimization technique
B. A structured definition of tool inputs and outputs
C. A firewall policy
D. A token compression method

Answer

B. A structured definition of tool inputs and outputs

Explanation

Tool schemas standardize external tool interactions.

Question 6

What is the purpose of function calling?

A. Eliminate orchestration
B. Allow models to invoke external tools dynamically
C. Replace APIs entirely
D. Remove authentication

Answer

B. Allow models to invoke external tools dynamically

Explanation

Function calling enables structured tool execution.

Question 7

Why are tool access controls important?

A. They reduce GPU memory usage
B. They restrict unsafe or unauthorized tool usage
C. They eliminate monitoring
D. They disable workflows

Answer

B. They restrict unsafe or unauthorized tool usage

Explanation

Access controls improve safety and governance.

Question 8

What is a common challenge with large conversation histories?

A. Unlimited context windows
B. Context window limitations in LLMs
C. Elimination of memory usage
D. Reduced orchestration complexity

Answer

B. Context window limitations in LLMs

Explanation

LLMs can only process limited amounts of context.

Question 9

What is the purpose of human approval workflows?

A. Increase hallucinations
B. Provide oversight for sensitive or high-risk actions
C. Remove governance requirements
D. Disable trace logging

Answer

B. Provide oversight for sensitive or high-risk actions

Explanation

Human review reduces operational risk.

Question 10

What should organizations monitor in agent systems?

A. Only GPU temperatures
B. Tool usage, safety, conversation quality, and task completion
C. Only token counts
D. Only API latency

Answer

B. Tool usage, safety, conversation quality, and task completion

Explanation

Comprehensive monitoring improves reliability and governance.

Go to the AI-103 Exam Prep Hub main page

Leave a comment