Productivity and Collaboration10% of the exam
AppExchange and AgentExchange apps and packages
When to extend an org from the Salesforce marketplace, how managed, unmanaged, and unlocked packages differ, who can publish listings, and how to evaluate and install packages that bring flows, prompt templates, and agent actions.
Identify use cases for AppExchange applications (awareness of managed or unmanaged packages, who is allowed to publish, prompts on AgentExchange, flows).
~7 min read · 6 practice questions
What the exam expects
- Recognize when a marketplace solution beats a custom build, and where to find partner-built apps, agents, and components (AppExchange, now branded AgentExchange).
- Distinguish managed, unmanaged, and unlocked packages by editability, upgrades, and effect on org limits.
- State who is allowed to publish a listing: Salesforce partners in the Partner Program whose solutions pass the security review.
- Know that packages can carry flows, prompt templates, agent actions, and agent topics, and where to look for reusable Agentforce building blocks.
- Evaluate and install a package safely: read the listing, test first, and choose who gets access during installation.
Key facts
Marketplace name
- Detail
- AgentExchange in current Salesforce content (formerly AppExchange)
Install permission
- Detail
- Download AppExchange Packages
Managed package code
- Detail
- Can't be viewed or changed by the installer
Managed package upgrades
- Detail
- Published by the provider; upgrades exist for managed packages only
Unmanaged package
- Detail
- Customizable; no upgrades, reinstall to update
Unmanaged components
- Detail
- Count against app, tab, and object limits
Unlocked packages
- Detail
- For internal business apps
Publishing prerequisite
- Detail
- Salesforce Partner Program membership plus AppExchange security review
Access options at install
- Detail
- Admins only, all users, or specific profiles
Test Drive
- Detail
- Read-only Developer Edition org with the package
Testing rule
- Detail
- Test in a Developer Edition org or sandbox before production
Agentforce components
- Detail
- Agent actions, agent topics, and prompt templates are packageable
Packaged permission sets
- Detail
- Not editable; clone them instead
Sources for this section (8)
- Get Started with AgentExchangetrailhead.salesforce.com (opens in a new tab)
- Install a Managed Packagehelp.salesforce.com (opens in a new tab)
- Install AgentExchange Packagestrailhead.salesforce.com (opens in a new tab)
- Upgrade Managed Packageshelp.salesforce.com (opens in a new tab)
- Packaging Release Noteshelp.salesforce.com (opens in a new tab)
- ISVforce Guidedeveloper.salesforce.com (opens in a new tab)
- Explore AgentExchange Listingstrailhead.salesforce.com (opens in a new tab)
- Packageable Componentsdeveloper.salesforce.com (opens in a new tab)
- Why don't universally required fields added by a package upgrade block existing records?
- Which user permission does an admin need to install a package?
- Which permission does a provider need to upload packages?
- When does an expired package's custom fields stop counting against the edition's field limit?
- Which package items can install with an upgrade even though they're missing from the Package Items list?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform Administrator pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 28 lessons of the Platform Administrator guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (6 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both