Free B2C-Solution-Architect Practice Test Questions (2026)

Explanation:

The company has high-volume order data (~200 million orders/year from 2 million customers) and requires:
- Full lifetime order history access.
- Lifetime engagement tracking.
- Customer Lifetime Value (LTV) calculation based on orders.

B2C Commerce stores orders but is not designed for long-term historical querying or analytics at this scale.

Why these three systems:

B. Service Cloud
Using Person Accounts (B2C standard), Service Cloud provides the unified 360-degree customer profile. Integrated with B2C Commerce (via b2c-crm-sync) and Order Management, it displays lifetime order history and engagement tracking (cases, interactions, purchases) in the Service Console—essential for agents and self-service portals.

E. Marketing Cloud
With Marketing Cloud Connect and data feeds from B2C Commerce/Order Management, it tracks lifetime multi-channel engagement (emails, SMS, behavioral events via collect.js). It includes Einstein LTV scoring and calculated insights to calculate and segment by Lifetime Value based on order history—critical for personalized campaigns.

F. Salesforce Order Management
SOM ingests and consolidates all orders from B2C Commerce (native connector), maintaining a complete lifetime order list in scalable Core objects (Order, OrderSummary). This offloads historical order storage/querying from B2C Commerce, enables fulfillment orchestration, and feeds order data to Service Cloud and Marketing Cloud for history and LTV.

Why the others are incorrect:

A. Sales Cloud
Suitable for B2B but not ideal for high-volume B2C consumer profiles (Person Accounts are Service Cloud-focused in B2C scenarios).

C. Heroku (likely "Heroku")
Custom external platform—unnecessary when native Salesforce tools handle the requirements.

D. Materials Written
Appears to be a typo/garbled option with no relevance.

This trio (Service Cloud + Marketing Cloud + Order Management) is Salesforce's recommended B2C architecture for lifetime customer insights at scale.

References:
Salesforce B2C Solution Architect resources: SOM for order consolidation, Service Cloud for 360-view, Marketing Cloud for engagement/LTV.
Documentation: SOM connector, Einstein LTV features.

Explanation:

✅ Summary:
This scenario is about ensuring a single, consistent customer identity across B2C Commerce, Service Cloud, and Marketing Cloud. Since customer data exists across multiple platforms, the key challenge is aligning identity and consent. Subscriber Key in Marketing Cloud and customer profiles in Service Cloud/Commerce need alignment to provide a unified 360-degree customer view.

🟢 Correct Option A:
Sending the Marketing Cloud Subscriber Key to Service Cloud and B2C Commerce provides a consistent customer identifier across all systems. This avoids duplicate records and allows Marketing Cloud to target the right customer, while Service and Commerce can reference the same key for personalization and service.

🟢 Correct Option D:
Using Service Cloud as the system of record for customer data and consent preferences ensures governance and accuracy. Since Service Cloud is designed to store and manage customer data, it becomes the best place to centralize information and then propagate it to Marketing Cloud and Commerce for campaigns and personalization.

🔴 Incorrect Option B:
Engaging Marketing Cloud Professional Services for a subscriber key migration is unnecessary unless the subscriber key strategy is deeply flawed. In most cases, companies can use existing Subscriber Keys and extend them across other Salesforce Clouds without a complete migration.

🔴 Incorrect Option C:
Migrating Marketing Cloud data into B2C Commerce is not advisable, as Commerce is not intended to serve as the master database for customers. B2C Commerce is optimized for transactional storefront operations, not as a system of record for customer identity.

📖 Reference:
Salesforce Help: Subscriber Key Best Practices
Salesforce Help: Customer 360 Identity

Explanation:

The company has a structured CI/CD process with multiple developer sandboxes, regular QA integration, weekly staging, and production releases. Adding Marketing Cloud + Marketing Cloud Connect requires an environment strategy that supports parallel development, testing, and data isolation while minimizing costs.

Why A is the best recommendation:
Use a single Marketing Cloud account (cheapest licensing model).
Create two Business Units (BUs):
- One BU for production (live campaigns, real subscribers).
- One BU for testing/non-production (development, QA, staging).

Configure Marketing Cloud Connect to link the testing BU to all developer, QA, and staging sandboxes (Connect supports multiple Salesforce orgs connected to different BUs in the same MC account).
This provides:
- Data segregation: Test emails, journeys, tracking, and subscriber data stay isolated in the test BU.
- Cost efficiency: No additional full MC accounts/licenses.
- Alignment with CI/CD: Developers test synchronizations and journeys in the test BU; changes are replicated/promoted to the production BU during releases.

Why the other options are inferior:

B: Two full MC instances (separate accounts) doubles licensing costs unnecessarily. Connecting only to staging limits developer/QA testing.

C: One MC instance per sandbox is prohibitively expensive and operationally unmanageable (dozens of accounts).

D: Marketing Cloud does not have true "sandboxes" like Salesforce CRM. A separate "sandbox" MC instance means a second full account (high cost), and connecting it to every developer sandbox is impractical.

Option A follows Salesforce's recommended pattern for enterprise multi-environment development with Marketing Cloud Connect: single account + BUs for isolation.

References:
Salesforce Marketing Cloud Documentation: Business Units for environment separation.
Marketing Cloud Connect Guide: Connecting multiple Salesforce orgs to specific BUs.
B2C/Multi-Cloud Architect best practices: Use BUs to balance cost and segregation.

Explanation:

An electronics company is migrating 3 million customer records from B2C Commerce to Service Cloud to enable the ‘Order on Behalf of’ feature. The Solution Architect needs an efficient method to export and import this large dataset. The solution must handle bulk data, ensure accuracy, and minimize manual effort. Using Salesforce tools for export and import ensures compatibility, scalability, and alignment with best practices for a one-time migration of customer records.

🗄️ Correct Option:

Option A: Use Business Manager to export and Data Loader to import the 3 million records into Service Cloud:
Business Manager in B2C Commerce allows exporting large datasets, like 3 million customer records, as CSV files. Salesforce Data Loader then imports these records into Service Cloud efficiently, handling bulk data with minimal errors. This method is ideal for a one-time migration, ensuring data integrity and compatibility. It’s a standard, supported approach in Salesforce, making it scalable and reliable for transferring large volumes of customer data accurately.

🗄️ Incorrect Option:

Option B: Use the Streaming API to push the 3 million customer records from B2C Commerce to Service Cloud:
The Streaming API is designed for real-time data updates, not bulk data migration. It’s unsuitable for transferring 3 million records at once, as it could overwhelm the system, cause delays, or exceed API limits. This method is better for ongoing, event-driven updates rather than a one-time batch migration, making it inefficient and impractical compared to using Business Manager and Data Loader for this scenario.

Option C: Use the Salesforce REST API to import the 3 million records into Service Cloud:
The Salesforce REST API is meant for programmatic, real-time data interactions, not bulk migrations. Importing 3 million records via REST API would be slow, resource-intensive, and prone to hitting governor limits. It requires complex custom coding, unlike the straightforward, supported approach of Data Loader. This makes it inefficient for a one-time transfer of large customer datasets from B2C Commerce to Service Cloud.

Option D: Use the Commerce Cloud REST API to import the 3 million records into Service Cloud:
The Commerce Cloud REST API is designed for accessing B2C Commerce data, not for importing data into Service Cloud. It would require custom development to extract and map 3 million records, which is complex and error-prone. This approach is less efficient than using Business Manager for export and Data Loader for import, which are built for bulk data transfers and align with Salesforce’s best practices.

🗄️ Reference:
Salesforce Help: “Data Loader Guide”
Salesforce Commerce Cloud Help: “Business Manager Data Export”

Explanation:

Centralized Identity Provider (IdP): Salesforce Identity is specifically designed to serve as the single source of truth for authentication across multiple platforms. By acting as the IdP for both the B2C Commerce storefront and the Experience Cloud community portal, it provides a seamless Single Sign-On (SSO) experience for customers.

Minimizing Data Migration: Using Salesforce Core/Identity as the primary authentication method allows customer profile data to be stored and managed in a single location—the Salesforce Core database (as Contacts or Person Accounts). This eliminates the need to migrate or duplicate the full profile data into B2C Commerce's internal database, keeping the architecture lean and reducing synchronization complexity.

Platform Synergy: Because Experience Cloud is built natively on the Salesforce Platform, it automatically leverages Salesforce Identity. Connecting B2C Commerce to this same identity pool through B2C Commerce Account Manager or Salesforce Customer Identity Plus creates a unified profile without the heavy lifting of traditional cross-cloud data replication.

Why Other Options Are Not Recommended

B. Salesforce CDP (Data Cloud):
While powerful for unifying data and creating segments for marketing, Data Cloud is not an authentication provider or a primary system for managing real-time login credentials.

C. Salesforce Marketing Cloud:
Marketing Cloud is an engagement engine, not an identity provider. Using it for primary authentication would be an architectural anti-pattern and would likely increase, rather than decrease, data migration needs.

D. Salesforce B2C Commerce:
While B2C Commerce can store customer profiles, using it as the primary authentication method for an Experience Cloud community would require complex, non-native integrations and often necessitates migrating more customer data into the commerce-specific database than required by a centralized Identity approach.

References
Salesforce Help: Configure Your Experience Cloud Site as an Identity Provider: Details on using Salesforce Core to manage external identities.
Salesforce Developers: B2C Commerce Architecture: Overview of how B2C Commerce interacts with the broader Salesforce ecosystem.
B2C Solution Architect: Identity Federation in B2C Commerce: Explains the setup for cross-cloud identity with Salesforce Identity.

Explanation:

A company is migrating its legacy storefront to B2C Commerce to address performance and scalability issues. With 200,000 subscribers, 10,000 daily visitors, and 1,000 daily emails, the solution must support mobile users and replace a tightly coupled custom marketing tool. The Solution Architect should recommend a scalable, mobile-responsive storefront and a robust marketing platform to ensure seamless customer engagement, high performance, and decoupled architecture for future flexibility.

📱 Correct Option:

Option A: Build the storefront using the Storefront Reference Architecture (SFRA) and adopt Marketing Cloud for customer engagement:
SFRA is Salesforce’s modern, mobile-responsive framework for B2C Commerce, ensuring scalability and performance for 10,000 daily visitors. Marketing Cloud supports robust email campaigns for 200,000 subscribers, replacing the custom tool with advanced personalization and automation. This combination addresses mobile usage, decouples marketing from the storefront, and aligns with Salesforce best practices, providing a scalable, efficient solution for the company’s engagement and performance needs.

📱 Incorrect Option:

Option B: Build the storefront using B2C Commerce SiteGenesis architecture and adopt Pardot for customer engagement:
SiteGenesis is an older B2C Commerce framework, less optimized for mobile responsiveness and scalability compared to SFRA. Pardot is designed for B2B marketing, not B2C email campaigns for 200,000 subscribers. It lacks the robust personalization and scale needed for daily emails, making this option unsuitable for the company’s B2C-focused storefront and engagement requirements compared to SFRA and Marketing Cloud.

Option C: Modify the frontend for the existing legacy storefront to be mobile responsive. Decouple the custom-built marketing tool so it is no longer tightly tied to the storefront:
Modifying the legacy storefront doesn’t address its performance and scalability issues, which are critical for 10,000 daily visitors. Decoupling the custom marketing tool is beneficial but insufficient without a robust replacement like Marketing Cloud. Retaining the legacy system risks ongoing issues, making this less effective than migrating to B2C Commerce’s SFRA, which offers modern scalability and mobile support for the company’s needs.

Option D: Build the storefront using a headless commerce architecture and adopt Pardot for customer engagement:
Headless commerce offers flexibility but is complex and unnecessary for the company’s scale of 200,000 subscribers and 10,000 visitors. Pardot, designed for B2B marketing, doesn’t support the B2C email volume and personalization needed for 1,000 daily emails. This option is less practical than SFRA and Marketing Cloud, which provide a simpler, B2C-optimized solution for mobile responsiveness, scalability, and effective customer engagement.

📱 Reference:
Salesforce Commerce Cloud Help: “Storefront Reference Architecture (SFRA)”
Salesforce Help: “Marketing Cloud Overview”

Explanation:

B. Use an ETL tool with a staging database in order to run data cleansing tools to obtain a clean data set.
With millions of legacy records and known duplicate/incomplete/low-quality data, you should not rely on in-org tools alone. The right approach is to:
- extract into a staging area,
- run profiling, standardization, deduplication, survivorship rules (golden record),
- then load a clean, governed dataset into Salesforce.
An ETL + staging database is the scalable way to do this and keep the migration timely.

C. Iteratively test smaller loads against a developer or partial copy sandbox and the full load against a full copy sandbox.
For scale and timeline assurance, you need progressive load testing:
- smaller iterative loads in a Dev / Partial Copy sandbox validate mappings, transforms, and error handling quickly, and
- a full load rehearsal in a Full Copy sandbox is critical to validate:
- performance at scale,
- batch sizes,
- index/selectivity impacts,
- dedupe logic behavior,
- overall run-time (timeliness),
- cutover playbooks.
This is the standard pattern to reduce risk and hit deadlines for large migrations.

Why the other options are not selected

A. Duplicate Management in Salesforce can be used to identify and manage duplicate records.
Duplicate Management is useful for ongoing prevention and user-facing matching, but it’s typically not sufficient by itself to remediate millions of dirty records during migration within tight timelines. You still need upstream cleansing/deduping at scale (option B).

D. Test smaller loads in a developer sandbox and full load in a partial copy sandbox.
A Partial Copy sandbox is not suitable for full-volume migration rehearsal. You need a Full Copy to validate run-time and performance at true scale.

✅ Final: B and C

Explanation:

(✔) Correct Option: B - Call real-time inventory services directly throughout the product grid and checkout...
This ensures the most accurate, real-time inventory count is displayed at every customer touchpoint. By checking live inventory from the source of truth (e.g., an OMS or ERP) before displaying stock levels, the risk of selling unavailable products is significantly reduced, directly mitigating overselling.

(✔) Correct Option: C - Use Order Management capabilities to support the redirection of orders...
If real-time checks fail to prevent an oversell (e.g., inventory changes between the cart and checkout pages), Order Management provides a positive customer experience. It can automatically source the order from an alternative location (another warehouse or store) to fulfill it, turning a potential stock-out into a successful sale.

(✔) Correct Option: E - Call real-time inventory services on product and cart pages to confirm that inventory has not changed.
This is a critical, secondary check. A real-time call on the cart page reconfirms inventory availability just before the customer commits to the purchase. This acts as a final safeguard against overselling that might have occurred due to high traffic and latency between the initial product page view and the checkout process.

(✗) Incorrect Option: A - Use Service Cloud to text all registered customers...
While a good post-sale customer service tool for back-in-stock notifications, this is a reactive measure, not a proactive one for mitigating overselling during a sale. It does not prevent the negative experience of a customer ordering an out-of-stock product in the first place.

(✗) Incorrect Option: D - Use both B2C Commerce and Marketing Cloud to offer email notifications...
Similar to option A, this is a valuable tool for re-engagement after an item has sold out. However, it is purely reactive and does nothing to architecturally prevent the overselling event during the high-traffic launch, which is the core requirement.

Summary:
The architecture must proactively prevent overselling and react gracefully if it occurs. Proactive measures include real-time inventory checks on key pages (B & E) to display accurate counts. The reactive measure involves using Order Management (C) to fulfill orders from alternative locations if needed, ensuring customer satisfaction even when local inventory is depleted.

Explanation:

(✔) Correct Option: D - Export the data using Business Manager, and import it into Salesforce using Data Loader.
Business Manager provides a native, no-code export function to generate CSV files of customer data. Data Loader is the robust Salesforce tool designed for handling large-volume (millions of records) data imports efficiently and reliably. This combination requires no custom development to move data from one system to the other for a one-time migration.

(✗) Incorrect Option: A - Export the data using B2C Commerce APIs, and import it into Salesforce using Data Loader.
Using APIs (like Open Commerce API) to export data requires custom script development to call the API, handle pagination, and format the data. This introduces development effort, contradicting the requirement for a solution "without additional development."

(✗) Incorrect Option: B - Export the data using B2C Commerce APIs, and import it into Salesforce using Data Import Wizard.
This option has two flaws. First, using APIs requires development, as explained in option A. Second, the Data Import Wizard is a Salesforce UI tool intended for smaller data volumes (typically < 50,000 records), not for efficiently migrating two million customer records.

(✗) Incorrect Option: C - Export the data using Business Manager, and import it into Salesforce using the Data Import Wizard.
While using Business Manager for export is correct, using the Data Import Wizard for the import is incorrect for this volume. Importing two million records via the Wizard would be extremely slow, prone to UI timeouts, and likely exceed the tool's operational limits. Data Loader is the correct tool for this task.

Summary:
For a one-time migration of two million records without custom code, the solution must use out-of-the-box tools. Business Manager's export feature provides the data extract without code. Data Loader is the official, high-volume tool for importing large datasets into Salesforce, making this the most efficient and supported approach.

Reference:
Exporting from Business Manager
Using Data Loader

Explanation:

A. The Salesforce Platform can be used for customer master and consent management, or it can integrate with a third-party Master Data Management system.
In a multi-cloud landscape (CRM + Commerce + Marketing + external systems), you must decide where master customer + consent lives. Salesforce can be the system of record (often via core CRM objects + preference/consent model), or you can integrate to an external MDM if that already exists and is the enterprise authority.

D. Salesforce products, including Sales Cloud, Service Cloud, Experience Cloud, and Order Management System (OMS) run on the same physical platform and share a common data model.
These products are Salesforce Platform–native and commonly share the same core object model (e.g., Account/Contact, Orders, etc.). This is a key consideration because it simplifies identity alignment, security model, reporting, and automation within the platform (compared to integrating with non-core-platform products like B2C Commerce / Marketing Cloud).

E. Marketing Cloud enables personalization, journey orchestration, and cross-channel messaging.
Marketing Cloud is the primary capability in this architecture for journey orchestration and cross-channel messaging (email/SMS/push, etc.), and it’s typically where personalized communications are executed—fed by customer, commerce, and behavioral data.

Why the other options are not correct
B is incorrect: Tableau can connect to many data sources directly (databases, files, cloud apps) and does not require MuleSoft to access non-Salesforce data.
C is incorrect: Salesforce Order Management (OMS) is not “a B2C Commerce product” and it does run on the core Salesforce Platform; it integrates with commerce storefronts (including B2C Commerce), but it’s platform-native.