B2C Commerce Setup11% of the exam
Code versions, WebDAV upload and dw.json
How realms, instances and code version directories fit together, how dw.json and the sgmf-scripts npm commands push cartridges over WebDAV, and how activation, rollback and Code Replication decide which code actually runs.
Given a sandbox environment, configure an IDE to use WebDAV to deploy cartridges to the correct version directories.
~8 min read · 7 practice questions ·
What the exam expects
- Describe a realm and its instance types (sandbox, staging, development, production) and say which ones accept direct code uploads.
- Configure
dw.jsonso the upload tool reaches the right instance and the right version directory, and pick thesgmf-scriptsnpm command for the job (whole repository, one cartridge, one file, watch). - Reach a code version over WebDAV with Business Manager credentials and know where Business Manager lists every WebDAV URL.
- Activate, roll back, add and delete code versions on the Code Deployment page, and fix "my upload didn't show up".
- Move a release from staging to production with an inactive version and Code Replication.
Key terms: realm (the set of instances you develop, test and run sites on); code version (a folder of custom cartridges); active code version (the one the instance runs); compatibility mode (an API version activated with its code version); Code Replication (copies the active code version from staging to production or development).
Key facts
What an instance runs
- Detail
- Only the active code version
Activation side effect
- Detail
- Cached items are cleared
Rollback
- Detail
- Activates the previous version and its compatibility mode; fails if it was deleted
Code version retention
- Detail
- 3 to 20, default 10; active and previously active never removed
dw.json location
- Detail
- Repository top-level folder, sibling of
cartridges
dw.json keys
- Detail
hostname,username,password,code-version
WebDAV login
- Detail
- Business Manager username and password
Selected code version file
- Detail
.../Cartridges/.version
Node.js in SFRA
- Detail
- Version 18 tested; used only for npm dependency management
Code Replication
- Detail
- Copies the active version from staging to production or development
- Why does B2C Commerce install Node.js for SFRA?
- When does a code version show no activation time on Manage Code Versions?
- Which names does Business Manager refuse when you create or rename a release folder?
- Why must you write
dw.jsonyourself for the cartridges that ship with SFRA?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the B2C Commerce Developer pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 28 lessons of the B2C Commerce Developer guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (7 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