Salesforce Fundamentals18% of the exam
AgentExchange listings, installs and package licenses
How to extend an org from AgentExchange (formerly AppExchange): solutions versus consultants, the three trial options, pre-install checks, the install security options and their standard-profile gap, and the post-install steps for objects, permission sets and licenses.
Identify common scenarios for extending an org using the AgentExchange.
~8 min read · 9 practice questions ·
What the exam expects
- Decide whether a requirement calls for an AgentExchange solution or a consultant listing.
- Choose between a test drive, a sandbox trial and a Trialforce trial for an evaluation.
- List the checks to run before installing in production (edition, custom object and tab limits, external services) and who can install.
- Pick an install security option and explain why standard-profile users can still lack access afterward.
- Complete the post-install steps: deploy custom objects, assign packaged permission sets, assign package licenses.
- Key terms: AgentExchange (formerly AppExchange, the Salesforce marketplace for apps, agents, components and consultants); managed package (provider-controlled, upgradeable, namespaced); unmanaged package (editable copy, upgraded only by reinstalling); Trialforce trial (writable trial org you can keep); In Development (custom object status that hides the object from standard users).
Key facts
Listing kinds
- Detail
- Solutions (plug in) and consultants (build custom solutions)
Test drive
- Detail
- Read-only, provider-configured Developer Edition org with sample data
Trialforce trial
- Detail
- Writable Developer Edition org, limited time, keep it if you buy
Install permission
- Detail
- Download AgentExchange Packages (or a Salesforce admin)
Get It Now
- Detail
- Installs in production only; Try It for a sandbox
Install for All Users
- Detail
- Internal custom profiles only; standard profiles get no access
Group and Professional Editions
- Detail
- No security option; all profiles get full access
Package custom objects
- Detail
- Install as In Development; set to Deployed to roll out
Publicly listed managed package
- Detail
- Outside the edition allocation, inside the org's total limit
Managed permission sets
- Detail
- Not editable; clones don't receive upgrades
Package licenses
- Detail
- Manage Licenses on the installed managed package
Sources for this section (4)
- When is a consultant listing a better fit than a solution listing?
- Why can users still miss a package's objects after you granted access?
- Which three checks come before any install, per the best-practices article?
- Why does cloning a managed permission set cause drift?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Platform App Builder pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 26 lessons of the Platform App Builder guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (9 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams