Deploying sites with change sets and Metadata API
How to move an Experience Cloud site between orgs: a full-site change set with the Network component, what it leaves out and overwrites, partial Digital Experience deployments for enhanced LWR sites, and Metadata API with ExperienceBundle or DigitalExperienceBundle.
Describe the capabilities of different Experience deployments and migrations.
~8 min read · 11 practice questions ·
What the exam expects
- Pick the component type for a deployment: Network for a full site, Digital Experience for partial content of an enhanced LWR site.
- List what a full-site change set leaves out (dependencies to add by hand, settings to reconfigure) and what it overwrites.
- Apply the release-version rule, the Members then Login & Registration order, the required permissions, and the publish step after deploying.
- Choose the Metadata API type by framework: ExperienceBundle for Aura and non-enhanced LWR sites, DigitalExperienceBundle with DigitalExperienceConfig for enhanced LWR sites.
- Avoid the first-deploy failure of a non-enhanced LWR site.
Key terms: Network, the change set component that represents a whole site; Digital Experience, the component for partial enhanced LWR site content; ExperienceBundle, readable JSON site metadata for Aura and non-enhanced LWR sites; DigitalExperienceBundle / DigitalExperienceConfig, the pair that defines an enhanced LWR site; deployment connection, the sandbox-to-production link change sets need.
Key facts
- Detail
- Network, for Experience Builder and Salesforce Tabs + Visualforce sites
- Detail
- Members profiles and permission sets; custom list views for standard-object menu links
- Detail
- Deploy Change Sets and Modify All Data (or Modify Metadata Through Metadata API Functions)
- Detail
- Create and Upload Change Sets, Create AppExchange Packages, Upload AppExchange Packages
- Detail
- Overwrites the site in the target org
- Detail
- Can't deploy to a target org on an earlier release
- Detail
- Separate change sets, Members first
- Detail
- Enhanced LWR sites created Winter '23 or later; same-named site must exist in target
- Detail
- DigitalExperienceBundle and DigitalExperienceConfig; non-enhanced uses ExperienceBundle
- Detail
- Enable ExperienceBundle Metadata API; managed packages not supported
- Why must a release manager add a new permission set to a site change set by hand?
- When can you deploy a site from a sandbox already on the next release?
- Which metadata types define an enhanced LWR site?
- Why do members still see old pages after a successful deployment?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Experience Cloud Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 37 lessons of the Experience Cloud Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (11 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams