Lesson 36 of 41 · All lessons
Salesforce Agentforce Specialist
0 of 41 complete
1Exam Overview
  1. 1.1Agentforce Specialist Complete Exam Overview
2Prompt Engineering20%
  1. 2.1When to Use Prompt Builder
  2. 2.2Prompt Template Access Controls
  3. 2.3Field Generation and Flex Prompt Template Types
  4. 2.4Grounding Techniques for Prompt Templates
  5. 2.5Creating, Activating, and Executing Prompt Templates
  6. 2.6Best Practices for Writing Effective Prompts
  7. 2.7Trust Layer Security and Privacy Features
  8. 2.8Managing and Preventing Specific Models from Being Accessed
3Data 360 Fundamentals20%
  1. 3.1Agentforce Data Library
  2. 3.2Data 360 Concepts for Agentforce
  3. 3.3Chunking
  4. 3.4Indexing
  5. 3.5Retrievers
  6. 3.6Choosing a Grounding Approach for a Scenario
4AI Agents35%
  1. 4.1How an Agentforce Agent Works
  2. 4.2Agent Building Blocks and Agent Script
  3. 4.3Hybrid Reasoning and Deterministic Behavior
  4. 4.4Agentforce Builder: Canvas and Script Views
  5. 4.5Filters, Variables, and Template Expressions
  6. 4.6Standard and Custom Topics
  7. 4.7Standard and Custom Agent Actions
  8. 4.8Configure Topics, Instructions, and Actions for a Use Case
  9. 4.9Connecting Agents to Digital Experience, Email, Voice, and Slack
  10. 4.10Agent Security Context and Action Execution
  11. 4.11Choosing Between Employee and Service Agents
  12. 4.12When to Use Agent API
5Testing, Deployment, and Maintenance10%
  1. 5.1Testing Agents with Testing Center
  2. 5.2Understanding Testing Center Evaluations
  3. 5.3Deploying Agents from Sandbox to Production
  4. 5.4Deploying Prompt Templates Between Environments
  5. 5.5Reviewing Agent Behavior After Changes
6Governance and Observability10%
  1. 6.1Managing and Monitoring Agents
  2. 6.2Agent Analytics and Performance Signals
  3. 6.3Identifying Opportunities to Optimize Agent Behavior
  4. 6.4Using Observations to Guide Improvements
7Multi-Agent Orchestration5%
  1. 7.1Choosing a Multi-Agent Architecture
  2. 7.2Orchestrators and Connected Subagents
  3. 7.3Handoff and Supervisor Modes
  4. 7.4Model Context Protocol (MCP)
  5. 7.5Agent-to-Agent (A2A) Communication

Section 6 · Governance and Observability · 10% of exam

6.4 Using Observations to Guide Improvements

3 min read Updated Nov 16, 2026

Exam objective

Describe a repeatable process for turning agent analytics, feedback, and session observations into validated improvements.

Start with an outcome and evidence

An observation becomes useful when it is tied to a defined outcome, such as resolving a task accurately, respecting a verification rule, reducing avoidable escalation, or responding within an acceptable time. Establish a baseline for the relevant agent, channel, and intents. Combine aggregate analytics with session transcripts, trace details, evaluation scores, user feedback, and release history. A metric alone may show where to look but not why performance changed. Confirm that the observation is representative and that the data source covers the sessions in question. Note any changes to models, data, instructions, channels, or permissions during the period. Translate findings into a change

Classify the issue before choosing a remedy. A knowledge gap may need an authoritative source update or retrieval adjustment. Incorrect routing may need clearer classification descriptions or topic scope. A missed action may require better instructions, a variable mapping, filter logic, or action configuration. A security issue may require permission or authentication changes, not just a prompt edit. A latency issue may call for trace analysis of a slow step. Keep the proposed change focused and record the expected effect. If the evidence does not identify a cause, gather more sessions or reproduce the behavior before editing production.

Validate before and after release

Use a sandbox or controlled testing environment to validate the proposed change. Add the representative failed interaction and neighboring scenarios to Testing Center. Rerun the test cases that measure the desired outcome and check that other important paths still work. Review the detailed trace and action results, not just an aggregate score. Promote the approved change through the organization’s release process, activate the intended agent version, and confirm the target environment has the needed data, permissions, and connections. After deployment, compare the same measures against the baseline and look for unintended side effects.

Build a continuous improvement loop

A useful monitoring plan defines what to watch, how often to review it, who owns each signal, and what action follows a threshold or trend. For example, a sustained rise in failed tasks might trigger session review; repeated low-quality answers for one intent might trigger a knowledge or instruction review; a trust signal might require immediate governance review. Add resolved incidents to the regression suite and update operational documentation. Close the loop by checking whether the change improved the intended outcome and whether users still encounter the issue. Avoid optimizing one metric at the expense of safety, accuracy, or a good handoff to a human.

Use a closed loop: observe a pattern, confirm it in session details, identify the responsible layer, test a focused fix, deploy it, and measure the result.

The data collected for monitoring can contain sensitive content. Maintain access controls and data masking while preserving enough context for authorized investigation.

Extra concept: A practical success measure is defined before the fix; choosing a threshold only after seeing results makes it harder to judge improvement objectively.

Official references:

  • Build an Agent Testing and Observability Plan https://help.salesforce.com/s/articleView?id=ai.agent_test_prep.htm&language=en_US&type=5
  • Observe Phase Observability Tools https://help.salesforce.com/s/articleView?id=ai.agentforce_observability_observe_phase_tools.htm&language=en_US&type=5
  • Set Up Agentforce Session Tracing https://help.salesforce.com/s/articleView?id=ai.generative_ai_session_trace_setup.htm&language=en_US&type=5

Key takeaways

  • Connect observations to defined outcomes and verify the evidence before changing configuration.
  • Test targeted fixes and related paths before release, then compare production behavior with a baseline.
  • Assign owners and follow-up actions to important monitoring thresholds and recurring patterns.

Check your knowledge

Answer exam-style Governance and Observability questions with answers and explanations.

Practice Governance and Observability
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Agentforce Specialist simulator: same number of questions, same time limit.

Get Complete Access