Historical learning notes and practice questions. See the issuer notice above for credential status and current learning options.
Independent study resource
Exam objectives and policies can change. Confirm current details with the certification issuer.
Check current objectives
Use the official exam guide as the source for current objectives and section weights.
Practice for learning
Use sample questions to review concepts and identify topics for further study.
Works on Any Device
Full practice experience on phone, tablet, or desktop
Free, No Sign-Up
Start practicing immediately, no account or email required
Salesforce Certified B2C Commerce Architect – Complete 2026 Guide
Historical learning notes for Salesforce Certified B2C Commerce Architect. See the issuer notice above for credential status and current learning options.
Recommended Prerequisites
We recommend completing this certification first to prepare you better.
Current exam registration and delivery are unavailable. See the issuer notice above for current learning options.
Exam Topics
Last updated:
Who may use this historical learning reference?
- Senior SFCC architects: You have led B2C Commerce builds and want proof that you can design whole storefront programmes, not just features.
- Technical leads evaluating commerce patterns: You decide between SFRA and a headless storefront, and you plan integrations, caching and site operations.
- Solution architects: You work on retail projects where B2C Commerce has to fit with Order Management, Marketing Cloud and outside systems.
Official references: Use the issuer’s current materials to confirm exam objectives, format, and fees before booking.
Official sources: Exam guide·Salesforce exam pricing·Independent exam-prep resource; details may change.
B2C Commerce Architect: Key Concepts
Architecture Patterns & Scalability
A B2C Commerce realm holds several instances: sandboxes for developers, then Development, Staging and Production. Code and data are built and tested on Staging, then replicated to Production. A realm can run many sites, which share code but can have their own catalogs, prices and settings. For a retailer with several brands or countries, the usual design is one master catalog for products, separate storefront catalogs per site to control what each one shows, and separate price books per currency or market. Scale comes from the platform, but your code must still be efficient: avoid heavy logic on every page request and use jobs for batch work.
Storefront Architecture & Headless Commerce
SFRA (Storefront Reference Architecture) is the standard server-rendered storefront. You customise it by adding your own cartridges on top, without editing the base code. Composable Storefront (PWA Kit with Managed Runtime) is the headless option: a React front end that calls the B2C Commerce APIs. Headless gives more freedom in the front end and fits teams with strong JavaScript skills, but it means more to build and run yourself. Pick SFRA when speed to market and standard features matter most, and headless when the brand needs a very custom experience or one front end for several back ends.
Integration Architecture: OCAPI, SCAPI & Connectors
SCAPI (Salesforce Commerce API), including the Shopper APIs, is the modern API set and is the default for new headless builds. OCAPI (Open Commerce API) is the older API, still used on many sites. SLAS handles shopper login and tokens for headless storefronts. For outside systems, use service framework definitions in Business Manager so calls have timeouts, logging and circuit breakers. Large data such as product feeds and inventory usually come in through scheduled jobs that import XML or CSV files. Payment, tax and address providers usually plug in through certified LINK cartridges.
Performance, Caching & CDN Strategy
Page caching is the biggest performance lever. Cache whole pages or page parts with the iscache tag, and keep user-specific bits, like the mini cart, as small uncached includes loaded separately. Set sensible cache times and clear the cache when catalog or content changes. The eCDN serves images and static files from locations close to the shopper. Watch the platform quotas, which limit things like the number of objects or API calls per request, and fix code that breaks them before peak season. Test with realistic traffic before big sale days.
Security, Compliance & Site Operations
Never store raw card numbers on the platform. Use a payment provider's cartridge so card data goes straight to them as a token, which keeps you out of most PCI scope. Use role-based access in Business Manager so each team only sees what it needs. Handle shopper privacy requests, consent and cookie rules for each country. For operations, plan code deployments through Staging with replication, schedule jobs outside peak hours, and set up log monitoring and alerts. Have a clear plan for peak trading such as Black Friday, including code freezes.
Requests hit a CDN first (static assets, cached pages), then an application cache layer; and only reach the origin server for truly dynamic content, this layering is what lets a storefront handle Black Friday-scale traffic.
Salesforce Certified B2C Commerce Architect Practice Questions (With Explanations)
Test your knowledge with these 15 sample questions.
Question 1: A retailer runs three brands in five countries. Most products are shared, but each brand shows a different range and each country has its own prices. What is the best catalog design?
Key takeaway: A shared master catalog avoids duplicating products.
Show correct answer and explanation
Correct answer: A. One master catalog, storefront catalogs, price books
A shared master catalog avoids duplicating products. Storefront catalogs control what each site shows, and price books handle prices per market.
- Prices in custom attributes skip the price book system and are hard to manage.
- Separate master catalogs duplicate shared products and make updates harder.
- One shared storefront catalog can't show a different range per brand.
Question 2: A developer needs to change how the checkout page works on an SFRA site. Where should the change go?
Key takeaway: Cartridges on the left override those on the right.
Show correct answer and explanation
Correct answer: B. In a custom cartridge earlier on the cartridge path
Cartridges on the left override those on the right. Putting changes in your own cartridge keeps the base untouched, so upgrades are easier.
- Site preferences change settings, not page logic.
- A cartridge on the right is overridden by the base, so the change wouldn't apply.
- Editing the base makes future SFRA upgrades painful.
Question 3: A brand wants a highly custom, app-like front end built by their React team, with fast page loads. Which approach fits best?
Key takeaway: Composable Storefront is the headless option built on React and the Commerce APIs, and it suits teams that want full control of the front end.
Show correct answer and explanation
Correct answer: C. Composable Storefront on the Commerce APIs
Composable Storefront is the headless option built on React and the Commerce APIs, and it suits teams that want full control of the front end.
- ISML is SFRA's template language. Calling OCAPI from it isn't a headless design.
- SFRA is server-rendered and less suited to an app-like React experience.
- Content slots manage content, not the whole front-end design.
Question 4: Category pages load slowly at peak. Each page includes the shopper's mini cart. What should the architect recommend?
Key takeaway: Caching the main page and loading the shopper-specific mini cart separately gives fast pages without showing the wrong cart.
Show correct answer and explanation
Correct answer: D. Cache the page, load the mini cart uncached
Caching the main page and loading the shopper-specific mini cart separately gives fast pages without showing the wrong cart.
- Jobs run in the background and can't serve live pages.
- Turning off caching makes the slowdown worse.
- More images slow the page further.
Question 5: A new headless storefront needs shoppers to log in and get tokens to call the Shopper APIs. What should be used?
Key takeaway: SLAS is the service for shopper login and API tokens in headless B2C Commerce builds.
Show correct answer and explanation
Correct answer: A. Shopper Login and API Access Service
SLAS is the service for shopper login and API tokens in headless B2C Commerce builds.
- Business Manager accounts are for staff, not shoppers.
- A shared key in the front end can be copied by anyone.
- Basic auth isn't how the Shopper APIs authenticate shoppers.
Question 6: The retailer must avoid storing card numbers on the platform to reduce PCI scope. What is the right design?
Key takeaway: With tokenisation, the card data goes to the payment provider and the site only keeps a token, which greatly reduces PCI scope.
Show correct answer and explanation
Correct answer: A. A provider LINK cartridge that tokenises
With tokenisation, the card data goes to the payment provider and the site only keeps a token, which greatly reduces PCI scope.
- Encrypted cards on the platform still bring the site into PCI scope.
- Emailing card details is insecure and breaks PCI rules.
- Session data still passes through and stores card data.
Question 7: Inventory levels for 500,000 products arrive from the warehouse system every hour. How should they be loaded?
Key takeaway: Scheduled jobs that import inventory files are the standard way to handle large, regular feeds.
Show correct answer and explanation
Correct answer: D. A scheduled inventory import job
Scheduled jobs that import inventory files are the standard way to handle large, regular feeds.
- Half a million API calls per hour is wasteful and may hit quotas.
- Updating stock on page views slows pages and doesn't keep stock in sync.
- Manual updates can't keep up at this scale.
Question 8: Code has been tested on Staging and is ready for Production. How does it usually reach Production?
Key takeaway: Code and data are prepared on Staging and then replicated to Production, which keeps the two in step.
Show correct answer and explanation
Correct answer: B. Replication from Staging to Production
Code and data are prepared on Staging and then replicated to Production, which keeps the two in step.
- Uploading straight to Production skips testing and is not the standard flow.
- Rebuilding by hand is slow and error-prone.
- FTP isn't how code is deployed to Production.
Question 9: A call to an outside tax service sometimes hangs and slows checkout. What should the architect use for this call?
Key takeaway: Service definitions in the service framework let you set timeouts, logging and a circuit breaker, so one slow service doesn't stall checkout.
Show correct answer and explanation
Correct answer: B. The service framework with a timeout and circuit breaker
Service definitions in the service framework let you set timeouts, logging and a circuit breaker, so one slow service doesn't stall checkout.
- Tax is needed during checkout, not overnight.
- No timeout lets the call hang and block the shopper.
- Calling from the browser exposes the integration and is hard to secure.
Question 10: A new site is being built from scratch with a headless front end. Which API set should be the default choice?
Key takeaway: SCAPI is the current API set for headless builds and is where Salesforce is investing.
Show correct answer and explanation
Correct answer: C. SCAPI and the Shopper APIs
SCAPI is the current API set for headless builds and is where Salesforce is investing.
- SOAP isn't the storefront API for B2C Commerce.
- OCAPI still works but is the older choice for new builds.
- There is no direct database access on the platform.
Question 11: Before Black Friday, a load test shows some pages breaking platform quotas. What should the team do?
Key takeaway: Quotas are enforced on Production.
Show correct answer and explanation
Correct answer: D. Fix the code that breaks the quotas before peak
Quotas are enforced on Production. Code that breaks them can fail under load, so it must be fixed before peak trading.
- Asking shoppers to wait isn't a real fix.
- Quotas apply in Production too.
- Turning off the eCDN would make performance worse.
Question 12: The merchandising team should manage promotions but must not change site code or payment settings. How is this controlled?
Key takeaway: Business Manager roles let you grant only the modules each team needs, such as promotions, without wider access.
Show correct answer and explanation
Correct answer: A. Business Manager roles with least privilege
Business Manager roles let you grant only the modules each team needs, such as promotions, without wider access.
- Full admin access gives far more than the team needs.
- Removing promotions stops the team doing their job.
- Shared logins remove accountability and are a security risk.
Question 13: Product images load slowly for shoppers in Asia, while the site is hosted in Europe. What helps most?
Key takeaway: The eCDN serves static files from locations close to the shopper, which cuts load times far from the main site.
Show correct answer and explanation
Correct answer: B. Serve images and static files via eCDN
The eCDN serves static files from locations close to the shopper, which cuts load times far from the main site.
- Images in cartridges still come from the same place and bloat code.
- Page caching helps speed. Turning it off makes things worse.
- Larger images load more slowly.
Question 14: When should an architect choose SFRA over a headless storefront?
Key takeaway: SFRA gives a working storefront with standard features out of the box, so it is often the faster route to launch.
Show correct answer and explanation
Correct answer: C. When speed to market and standard commerce features matter most
SFRA gives a working storefront with standard features out of the box, so it is often the faster route to launch.
- Every B2C Commerce storefront relies on the platform either way.
- Strong React teams wanting full control is the case for headless.
- Sharing one front end across channels is a strength of headless, not SFRA.
Question 15: A retailer wants to show different home page banners per country without code changes. What should be used?
Key takeaway: Content slots and assets let merchandisers manage banners per site or locale in Business Manager without a deployment.
Show correct answer and explanation
Correct answer: C. Content slots and assets in Business Manager
Content slots and assets let merchandisers manage banners per site or locale in Business Manager without a deployment.
- Hard-coded banners need a code change every time.
- Separate cartridges per country add needless code.
- HTML in custom objects is hard to manage and skips the content tools.
Salesforce Certified B2C Commerce Architect Exam FAQs
- What is covered on the Salesforce Certified B2C Commerce Architect exam?
- This page shows the section-wise exam weightage so you know exactly which topics carry the most weight. Use the exam topics and practice questions above to align your study with the official outline.
- What does a B2C Commerce Architect do?
- B2C Commerce Architects design e-commerce architectures, plan storefront experiences, integrate with external systems, and ensure performance, security, and scalability.
- Do I need B2C Commerce Developer before Architect?
- Yes, B2C Commerce Developer is typically required. Architect builds on development knowledge with focus on architecture, integration patterns, and enterprise design.
- Are there free practice questions for the Salesforce Certified B2C Commerce Architect exam?
- Yes. This page includes free sample practice questions with explanations. Use them alongside the current official documentation.
- How do I prepare for the Salesforce Certified B2C Commerce Architect certification?
- Use the exam tips, prerequisites, and study strategy on this page. Focus first on the highest-weighted sections, then take the sample practice questions. Schedule the exam when you consistently score well on practice tests.
Next Architect Certifications
After B2C Commerce Architect, many people move toward the wider architect credentials:
Honest Cert Breakdown
Difficulty: Hard
4/5Niche B2C Commerce (Salesforce Commerce Cloud) architecture exam. Requires hands-on SFCC platform experience, hard to fake.
Salary Range
$120,000–$160,000 / year
US average for certified professionals • Updated Summer '26 • Source: Salesforce Talent Ecosystem
Is it worth it?
Valuable in e-commerce-focused organizations. Limited in scope, only worth pursuing if Commerce Cloud is your core platform.
Weightings by Section
Designing B2C Commerce solutions for enterprise retailers: multi-site architecture, instance topology, and site design patterns.
OMS integration, payment gateway architecture, ERP integration patterns, headless commerce architecture, and API-first design.
SFRA architecture decisions, storefront performance strategies, PWA Kit considerations, and mobile commerce design.
CDN configuration, page caching strategies, pipeline performance, load testing, and high-traffic event architecture.
PCI DSS compliance architecture, shopper data protection, GDPR considerations, and B2C Commerce security settings.
Questions Candidates Ask
- What is the Salesforce B2C Commerce Architect certification?
- The Salesforce Certified B2C Commerce Architect validates expertise in designing enterprise-scale B2C Commerce (Salesforce Commerce Cloud) solutions. It covers multi-site architecture, integration design, headless commerce patterns, performance optimisation, and security compliance. It is the architect-level credential in the B2C Commerce track, building on the B2C Commerce Developer certification.
- What is the B2C Commerce Architect exam format?
- The exam consists of 60 multiple-choice and multiple-select questions with a 120-minute time limit. The passing score is approximately 65%. The exam costs $400 for the first attempt, with a 65% discount retake voucher after a failed attempt. It can be taken online (proctored) or at a Kryterion testing centre.
- What prerequisites are recommended for B2C Commerce Architect?
- Salesforce recommends holding the B2C Commerce Developer certification before attempting the Architect exam. The exam assumes deep hands-on experience implementing B2C Commerce solutions, typically 3–5+ years of development and architecture experience on the platform. Knowledge of SFRA, Commerce APIs, integration patterns, and headless commerce architecture is essential.
- What is headless commerce and how does it relate to this exam?
- Headless commerce decouples the frontend (storefront UI) from the backend (commerce engine), communicating via APIs. Salesforce supports headless B2C Commerce via the Commerce APIs and PWA Kit (Progressive Web App Kit). The Architect exam tests when to recommend headless vs SFRA-based architectures, the tradeoffs of each approach, and how to design API-first commerce solutions for enterprise retailers.
- What integration patterns are covered in the B2C Commerce Architect exam?
- The exam covers integration patterns for: OMS (Order Management System), real-time vs asynchronous order sync; ERP, product, price, and inventory synchronisation; PIM (Product Information Management), catalogue data feeds and product import; payment gateways: PCI compliant tokenisation and checkout flow design; and Customer Service Cloud, case creation from commerce events. Understanding which pattern is appropriate for each integration type is key.
Practice B2C Commerce Architect Questions
Free practice questions for the Salesforce B2C Commerce Architect exam.
Plan Your Next Certification
After this certification, consider: Application Architect, System Architect, or Technical Architect (CTA).
Topic Difficulty Heatmap
Which topics are a gimme vs which ones trap confident candidates. Use this to prioritise your final-week revision. These are our own topic groupings for study planning, not the official exam sections, those and their weightings are in the credential's exam guide.
| Topic | Difficulty | Study Tip |
|---|---|---|
| B2C Commerce Architecture | Hard | Site architecture and scalability. Know the platform limits. |
| Storefront and Experience | Moderate | Storefront customization and headless options, when to use which. |
| Integration and Data | Trap ⚠ | OCAPI vs Open API and data sync, commonly confused. |
| Performance and Security | Moderate | Performance tuning and security, standard architect topics. |
Difficulty based on analysis of common candidate errors across each exam section.
Ready to Test Your Knowledge?
Try the B2C Commerce Architect free practice exam, scored with full explanations.
B2C Commerce Architect Free Practice Exam →Quick Answer: What B2C Commerce Architect Tests
- Architecture and design: SFRA vs. Headless Commerce selection, multi-site architecture design, cartridge dependency management at scale, Business Manager configuration governance, and how to structure a large Commerce implementation across regions and brands.
- Integration architecture: OC API (Open Commerce API) vs. SCAPI (Salesforce Commerce API) selection, integration with ERP (SAP, Oracle) for order fulfilment, payment gateway integration patterns, and Marketing Cloud integration for personalised commerce experiences.
- Performance and security: CDN strategy for static assets, caching layers (page-level, partial-page, fragment), PCI DSS compliance for payment data, and how to design high-traffic peak performance (Black Friday scale).
Highest-Weight Exam Sections
Architecture + Integration + Performance = 77%. The SFRA vs. headless decision and integration patterns are the highest-value study areas.
Scenario Strategy: How to Approach B2C Commerce Architect Questions
Questions present a commerce architecture requirement and ask which design decision, API approach, or integration pattern is correct. Think about long-term maintainability and upgrade compatibility, architect decisions have multi-year implications.
- For SFRA vs. headless questions: SFRA = managed front-end, faster implementation, less flexibility. Headless = custom front-end, maximum flexibility, more complex to build and maintain. Choose headless when: aggressive front-end customisation is required, PWA or native mobile is needed, or the team has strong React/Vue skills. Choose SFRA when: time-to-market is critical, front-end flexibility is not the priority.
- For API questions: OCAPI is the legacy REST API for B2C Commerce, still used for many integrations. SCAPI (Salesforce Commerce API) is the newer API with better performance and easier authentication. For new integrations, prefer SCAPI. When a question says ’modern integration’ or ’headless storefront’, SCAPI is the answer.
- For performance questions: page-level caching (full page HTML cache) is the most impactful for anonymous users. Partial page caching for components that change per session. Avoid caching personalised content at the page level, use client-side rendering for personalised sections. CDN placement for static assets (images, CSS, JS) reduces origin server load.
Mock-Test Benchmark Before Booking
75%+ on 3 timed full mocks before booking
B2C Commerce Architect is the highest Commerce Cloud certification. Most candidates earn B2C Commerce Developer first and gain 3+ years of Commerce Cloud project experience before attempting Architect. Without real multi-site Commerce implementations and integration architecture experience, this exam is extremely difficult.
3 Concepts That Fail Most B2C Commerce Architect Candidates
These are not the hardest topics; they are the ones where candidates are most confidently wrong. Learn the distinction early.
1. Site Architecture: One Site vs Multiple Sites for Multi-Region
B2C Commerce supports multiple storefronts within one realm. A single site can serve multiple locales using site preferences and localisation. Candidates recommend one site per region, the exam expects multi-locale configuration on a single site unless business processes are completely separate (separate catalogs, pricing, and fulfilment), in which case separate sites are justified.
2. OCAPI vs SCAPI: Legacy vs Modern API Layer
Open Commerce API (OCAPI) is the legacy REST API for B2C Commerce. Salesforce Commerce API (SCAPI) is the modern replacement, built on headless architecture. Exam scenarios about new integrations expect SCAPI recommendations. Candidates default to OCAPI because it is more familiar from study materials. Know that Headless Reference Architecture (SFRA) uses SCAPI for new implementations.
3. Quota Limits: Why Performance Degrades Under Load
B2C Commerce enforces pipeline/controller quota limits (CPU time, memory, custom objects per request). Exceeding these causes degraded performance or errors. Candidates diagnose performance issues by looking at code logic, the exam expects checking quota consumption first. Know the key quotas: custom object record limit per session, pipeline dictionary size, and API call rate limits.
Frequently Asked Questions
- What is the Salesforce B2C Commerce Architect exam format?
- The Salesforce B2C Commerce Architect exam has 60 multiple-choice questions, a 105-minute time limit, a 65% passing score, and a $200 fee ($100 retake). It tests expert-level B2C Commerce architecture: SFRA design patterns, performance architecture, security, scalability, and integration with external systems.
- What are the highest-weight B2C Commerce Architect exam sections?
- Architecture and Design (35%) and Integration Patterns (22%) together account for 57% of the exam. Designing scalable SFRA cartridge architectures, integration with payment gateways and ERP systems, performance optimisation, and B2C Commerce security are the most heavily tested areas.
- How does B2C Commerce Architect differ from B2C Commerce Developer?
- B2C Commerce Developer tests hands-on development skills: building cartridges, writing controllers, configuring Business Manager. B2C Commerce Architect tests systems design: how to architect the overall Commerce platform, select between Headless Commerce vs. SFRA, design integration patterns with external systems, optimise for performance at scale, and govern a multi-site implementation.
- What is Headless Commerce and does the B2C Commerce Architect exam test it?
- Headless Commerce separates the front-end presentation layer from the B2C Commerce back-end; the storefront is built with a custom front-end (React, Vue) consuming Commerce APIs (OCAPI or SCAPI). Yes, the Architect exam tests when to choose Headless vs. SFRA: Headless for maximum front-end flexibility, SFRA for faster time-to-market with a managed front-end framework.
- What concepts do most B2C Commerce Architect candidates get wrong?
- The most commonly misunderstood topics for the B2C Commerce Architect exam are: (1) Site Architecture: One Site vs Multiple Sites for Multi-Region; (2) OCAPI vs SCAPI: Legacy vs Modern API Layer; (3) Quota Limits: Why Performance Degrades Under Load. Candidates are most confidently wrong on these. Learn the distinctions early to avoid losing marks on questions you expect to get right.
- Why do most B2C Commerce Architect candidates fail questions about Site Architecture?
- B2C Commerce supports multiple storefronts within one realm. A single site can serve multiple locales using site preferences and localisation. Candidates recommend one site per region, the exam expects multi-locale configuration on a single site unless business processes are completely separate (separate catalogs, pricing, and fulfilment), in which case separate sites are justified.
- Why do most B2C Commerce Architect candidates fail questions about OCAPI vs SCAPI?
- Open Commerce API (OCAPI) is the legacy REST API for B2C Commerce. Salesforce Commerce API (SCAPI) is the modern replacement, built on headless architecture. Exam scenarios about new integrations expect SCAPI recommendations. Candidates default to OCAPI because it is more familiar from study materials. Know that Headless Reference Architecture (SFRA) uses SCAPI for new implementations.
- Why do most B2C Commerce Architect candidates fail questions about Quota Limits?
- B2C Commerce enforces pipeline/controller quota limits (CPU time, memory, custom objects per request). Exceeding these causes degraded performance or errors. Candidates diagnose performance issues by looking at code logic, the exam expects checking quota consumption first. Know the key quotas: custom object record limit per session, pipeline dictionary size, and API call rate limits.
Related Exam Tips
Start B2C Commerce Architect Prep
After this exam, consider Application Architect or System Architect next.
Share or cite this study guide
Free to link from a forum post, study repo or article. Copy the Markdown and paste it anywhere.