B2C-Solution-Architect Exam Questions With Explanations
The best B2C-Solution-Architect practice exam questions with research based explanations of each question will help you Prepare & Pass the exam!
Over 15K Students have given a five star review to SalesforceKing
Why choose our Practice Test
By familiarizing yourself with the B2C-Solution-Architect exam format and question types, you can reduce test-day anxiety and improve your overall performance.
Up-to-date Content
Ensure you're studying with the latest exam objectives and content.
Unlimited Retakes
We offer unlimited retakes, ensuring you'll prepare each questions properly.
Realistic Exam Questions
Experience exam-like questions designed to mirror the actual B2C-Solution-Architect test.
Targeted Learning
Detailed explanations help you understand the reasoning behind correct and incorrect answers.
Increased Confidence
The more you practice, the more confident you will become in your knowledge to pass the exam.
Study whenever you want, from any place in the world.
Salesforce B2C-Solution-Architect Exam Sample Questions 2026
Start practicing today and take the fast track to becoming Salesforce B2C-Solution-Architect certified.
21524 already prepared
Salesforce 2026 Release152 Questions
4.9/5.0
Universal Containers has an existing loyalty program that rewards its customers for purchases and frequent shopping with points that can be redeemed in store or online. They want to transform their existing loyalty program by investing in tools like Marketing Cloud, Salesforce Loyally Management and COP- They want to start segmenting their most loyal customers based or their online engagement and purchase history.
Which three actions should a Solution Architect recommend they consider taking with the tools they are investing In?
Choose 3 answers
A. Curate tiered experiences in Marketing Cloud
B. Segment Individuals within CDP C.Q Segment Journeys within CDP
C. Curate tiered experiences in Loyalty Management
D. Create Journeys by tiers in Marketing Cloud
C. Curate tiered experiences in Loyalty Management
D. Create Journeys by tiers in Marketing Cloud
Explanation:
Universal Containers wants to transform their loyalty program using Marketing Cloud, Salesforce Loyalty Management, and CDP (Data Cloud). The primary goal is to segment most loyal customers based on online engagement (e.g., email opens, site behavior) and purchase history (from B2C Commerce or other sources), then deliver personalized, tiered experiences.
Option A (Correct): Curate tiered experiences in Marketing Cloud.
Marketing Cloud excels at delivering personalized communications and cross-channel experiences. Once loyalty tiers are calculated (in Loyalty Management or Data Cloud), Marketing Cloud can use tier attributes to curate tier-specific content, offers, emails, SMS, or mobile push notifications (e.g., exclusive previews for top-tier members).
Option C (Correct): Curate tiered experiences in Loyalty Management.
Salesforce Loyalty Management natively supports tiered programs (e.g., Silver, Gold, Platinum) with rules for earning/promotion based on points, spend, or activity. It allows curating tier-specific benefits such as bonus points multipliers, exclusive promotions, early access, or partner offers directly within the loyalty platform.
Option D (Correct): Create Journeys by tiers in Marketing Cloud.
Using Journey Builder, tier attributes (synced from Loyalty Management or calculated in Data Cloud) can be used as entry criteria or decision splits to build tier-specific journeys (e.g., VIP re-engagement, tier upgrade celebration, downgrade prevention). This enables automated, personalized nurture or retention flows based on loyalty status.
Option B (Incorrect): Segment Individuals within CDP.
While Data Cloud (CDP) is excellent for unifying customer data (ingesting purchase history from B2C Commerce, engagement from Marketing Cloud, loyalty data from Loyalty Management) and creating calculated insights (e.g., loyalty tier, LTV, churn risk), the primary segmentation for activation happens in the downstream tools (Marketing Cloud for journeys/emails, Loyalty Management for program benefits). "Segment Individuals" is not a specific action or feature name in Data Cloud—segmentation there produces audiences for activation, not direct tier experiences.
References:
Salesforce Help/Trailhead: Loyalty Management – tier configuration and benefits management.
Marketing Cloud Journey Builder – using loyalty tier attributes for segmentation and personalized paths.
Data Cloud for Loyalty use cases – unification and calculated insights (e.g., tier score), activation to Marketing Cloud and Loyalty Management.
B2C Solution Architect exam topics: Loyalty program transformation leverages Loyalty Management for core program/tier logic, Marketing Cloud for tiered communications/journeys, and Data Cloud for unified segmentation insights.
A customer is using B2C Commerce, Marketing Cloud, Service Cloud, and Experience Cloud. They would like to leverage Salesforce CMS to create common content that can be leveraged across customer touchpoints.
Which two products can leverage Salesforce content without custom integration?
Choose 2 answers
A. Experience Cloud
B. B2C Commerce
C. Marketing Cloud
D. Service Cloud
B. B2C Commerce
Explanation:
A. Experience Cloud
Why it is correct: Salesforce CMS was originally built specifically to power Experience Cloud. Within Experience Builder, there is a native CMS Component that allows users to drag and drop content (like banners, news articles, or product spotlights) directly into a site. No custom integration or API work is required because both products live on the core Salesforce platform and share the same underlying architecture.
B. B2C Commerce
Why it is correct: There is a native integration between Salesforce CMS and B2C Commerce. Within B2C Commerce Page Designer, merchants can browse and select content stored in Salesforce CMS to display on their storefront. This allows marketing teams to manage high-quality assets in the "Core" CMS and have them appear on the Commerce storefront without writing custom integration code to bridge the two clouds.
Detailed Analysis of Incorrect Answers
C. Marketing Cloud
Why it is incorrect: While Marketing Cloud has its own "Content Builder," it does not natively "consume" Salesforce CMS content without a custom integration or the use of specific connectors (like the Salesforce CMS for Marketing Cloud app). Unlike Experience Cloud, Marketing Cloud lives on a different infrastructure stack, making "zero-config" sharing less direct.
D. Service Cloud
Why it is incorrect: Service Cloud primarily uses Salesforce Knowledge for articles and documentation. While Service Cloud can display CMS content if it is embedded in an Experience Cloud site (the Help Center), the Service Console itself does not have a native component to leverage marketing content without customization.
References
Salesforce Help: Salesforce CMS Overview – Details the native connections to Experience Cloud and Commerce.
B2C Commerce Documentation: Connect Salesforce CMS to Page Designer – Explains the native integration using CMS channels.
Salesforce Architects: CMS Content Strategy – Discusses how to centralize content for multi-channel delivery.
A company wants to use Marketing Cloud to send customer electronic receipts that originate from its point of sale (POS) system. The company has a need for the receipt to be sent no more than 10 minutes after purchase and would like to track allemail sends that are being placed to that customer, The Marketing Cloud Contact Key should be the Service Cloud Contact ID.
What solution should a Solution Architect recommend to achieve this need?
A. Make an API call from the POS to Marketing Cloud to send the electronic receipt and then call Service Cloud to add the customer if they do not exist. Use an automation in Marketing Cloud nightly to remove any duplicate contacts that may be introduced with Marketing Cloud Connect.
B. Make an API call from the POS to Service Cloud to retrieve the Service Cloud Contact ID. If the customer does not exist, submit a POST to Service Cloud to create the Contact ID, then send the Contact ID to Marketing Cloud via an API to send the electronic receipt.
C. Make an API call from the POS to Service Cloud to add the customer if they do not exist; leverage a custom object to send details to Marketing Cloud via Marketing Cloud Connect and synchronized data sources to send the electronic receipt.
D. Make an API call from the POS to Marketing Cloud te send the electronic receipt. No call is required to Service Cloud to fetch the Contact IO as this information is already available at the POS.
Explanation
Let's analyze the requirements:
Trigger: Purchase at POS.
Action: Send email receipt within 10 minutes.
Key Constraint: Marketing Cloud Contact Key must be the Service Cloud Contact ID.
Tracking: All sends must be trackable to the customer.
Why B is Correct:
Maintains the Single Source of Truth: The POS system first interacts with Service Cloud, which is designated as the system of record for the customer (Contact). This ensures the Contact ID created or retrieved is authoritative.
Guarantees Correct Contact Key: By retrieving or creating the Contact in Service Cloud first, the POS knows the correct, official Service Cloud Contact ID. It can then pass this ID to Marketing Cloud as the Contact Key, perfectly satisfying the core identity requirement.
Supports Real-Time Timeline: The sequence of API calls (POS → Service Cloud → Marketing Cloud) can be orchestrated to complete within the 10-minute SLA. While not instantaneous, this is a synchronous, event-driven flow appropriate for a receipt.
Enables Tracking: Using the correct Contact Key ensures all sends (transactional receipts) are properly attributed to the unified customer profile in Marketing Cloud, enabling accurate tracking and reporting.
Why A is Incorrect:
Creates Identity Chaos: Sending the receipt before ensuring the customer exists in Service Cloud risks using an incorrect or temporary ID as the Contact Key. This would break the core identity mandate.
Poor Data Hygiene: The "clean up duplicates nightly" approach is reactive and unreliable. It would lead to untrackable sends and a broken customer journey in the critical first 24 hours. It violates the principle of "get the identity right at the point of entry."
Why C is Incorrect:
Violates the 10-Minute SLA: Marketing Cloud Connect and Synchronized Data Sources operate on a polling schedule (e.g., every 15-30 minutes, sometimes longer). This is not a real-time mechanism. A purchase event captured in a custom object might not synchronize to Marketing Cloud for up to an hour, missing the 10-minute receipt window.
Why D is Incorrect:
Assumes Identity is Known: It states "this information is already available at the POS," which is an unfounded and risky assumption. The POS may have its own customer ID, but the requirement explicitly states the Marketing Cloud Contact Key must be the Service Cloud Contact ID. The POS cannot know this ID without querying Service Cloud. This approach would almost certainly use the wrong key, breaking the identity model and all downstream tracking.
Architectural Reference & Key Concept
Reference: Marketing Cloud Connect Integration Patterns & Identity Management. This tests the understanding of the "System of Record" principle and real-time vs. batch integration.
Key Concept:
Identity-First Design: When a system (Marketing Cloud) must use an identifier from another system (Service Cloud Contact ID), the integration must start by resolving that identifier in its source system. You cannot guess it or use a placeholder.
Integration Pattern Selection: For real-time, event-driven communications (like a post-purchase receipt), you must use real-time APIs (REST/SOAP). You cannot rely on batch or polling-based synchronization tools (like Marketing Cloud Connect's standard sync) for the initial trigger.
The architect must recommend a flow that respects the identity constraint, uses real-time APIs for the time-sensitive event, and ensures Service Cloud remains the authoritative source for the customer record. Option B is the only one that follows this pattern correctly.
A company is implementing a multi-locale solution that includes B2C Commerce, Service Cloud, and Marketing Cloud. Order confirmation emails are triggered from either B2C Commerce or Service Cloud and sent from Marketing Cloud.
What are two possible reasons why the shipping method name and description can be missing when these emails are triggered for languages other than US English, while other translated content appears correctly?
Choose 2 answers
A. The name and description for the shipping method are not set up correctly in B2C Commerce or Service Cloud for the requested locale.
B. The subscriber in Marketing Cloud does not have a preferred locale set.
C. The locale is not set correctly in the body of the email template.
D. The ShippingMethods data extension is missing the label and description field for the corresponding locale.
D. The ShippingMethods data extension is missing the label and description field for the corresponding locale.
Explanation:
Order confirmation emails in this multi-locale, multi-cloud setup are transactional emails sent from Marketing Cloud, triggered either by B2C Commerce (via the Marketing Cloud Connector cartridge and Transactional Messaging API) or by Service Cloud (via Marketing Cloud Connect triggered sends). Dynamic content such as shipping method name and description is typically pulled from B2C Commerce data (e.g., order summary or shipping method details) and inserted into the email using AMPscript or personalization strings.
Common reasons why shipping method name and description specifically can appear missing or in the wrong language (while other translated content works fine):
Option A (Correct): The name and description for the shipping method are not set up correctly in B2C Commerce or Service Cloud for the requested locale.
In B2C Commerce, shipping methods are configured in Business Manager with locale-specific display names and descriptions. If these fields are left blank or only populated for en_US (or the primary locale), no translated value will be available when the order is placed in another locale. The connector passes the shipping method ID and the requested locale to Marketing Cloud, but if no translation exists in B2C Commerce, the email will receive null/empty values for name and description—even though other content (e.g., product names, static email text) is correctly translated via Marketing Cloud content blocks or B2C catalog translations.
Option D (Correct): The ShippingMethods data extension is missing the label and description field for the corresponding locale.
Many implementations import or synchronize the shipping methods catalog into a ShippingMethods data extension in Marketing Cloud (often via Automation Studio or connector). This DE is then used in AMPscript Lookup functions to retrieve localized name/description based on the shipping method ID and locale passed from the order trigger. If the data extension rows lack populated label and description columns for non-en_US locales (or use flat fields instead of locale-specific columns like label_fr_FR, description_es_ES), the lookup will return empty values for those languages.
Option B (Incorrect): The subscriber's preferred locale in Marketing Cloud affects default language fallback for journeys and preference center, but transactional order confirmation emails are driven by the order/checkout locale from B2C Commerce (or case locale from Service Cloud), not the subscriber's profile locale. Missing shipping details are not caused by this.
Option C (Incorrect): The locale in the email template body (e.g., via Content Builder language variants or AMPscript SetLanguage) controls static content translation, but dynamic shipping method details are pulled separately via data from the trigger or lookups. Correct template locale settings explain why other content translates properly, but not the shipping method fields.
References:
Salesforce Help: B2C Commerce Connector – Shipping method localization handled in Business Manager; passed values depend on locale-specific configuration.
Marketing Cloud Documentation: Transactional Messaging API and order trigger payloads include locale context; recommended to use localized ShippingMethods DE for dynamic lookups.
B2C Solution Architect exam topics: Multi-locale considerations, data synchronization for transactional emails, and common pitfalls with shipping/payment method localization.
Universal Containers (UC) is in the process of implementing a B2C Commerce site for their storefront, and Experience Cloud for their support and help desk. UC wants to ensure that there is a single login and data experience between the two sites while also being relatively seamless.
Given the need for a single login experience, what should the primary system before all authentication?
A. Salesforce Identity
B. B2C Commerce
C. Service Cloud
D. Experience Cloud
Explanation:
Universal Containers is implementing B2C Commerce and Experience Cloud for their storefront and support portal. They need a single login experience to ensure seamless customer access across both platforms. The Solution Architect must recommend a primary authentication system that integrates both sites, maintains security, and provides a unified data experience. The solution should be scalable, align with Salesforce best practices, and simplify the customer’s login process across the storefront and help desk.
🔐 Correct Option:
Option A: Salesforce Identity:
Salesforce Identity provides a centralized authentication system for single sign-on (SSO) across B2C Commerce and Experience Cloud. It ensures customers use one login for both platforms, creating a seamless experience. For example, a customer logging into the storefront can access the help desk without re-authenticating. This scalable, secure solution aligns with Salesforce best practices, unifying user data and simplifying access management across multiple Salesforce clouds.
🔐 Incorrect Option:
Option B: B2C Commerce:
B2C Commerce manages storefront authentication but isn’t designed to be the primary system for cross-platform SSO. It lacks the robust identity management capabilities needed to unify logins with Experience Cloud. Using B2C Commerce as the primary system would require complex custom integrations, making it less efficient and secure compared to Salesforce Identity, which is built for seamless, centralized authentication across Salesforce platforms.
Option C: Service Cloud:
Service Cloud is designed for customer service, not centralized authentication. It doesn’t natively support SSO across B2C Commerce and Experience Cloud. Using Service Cloud for authentication would require significant custom development, leading to inefficiencies and potential security gaps. Salesforce Identity is the better choice, as it’s purpose-built for unified login experiences, ensuring seamless and secure access across both platforms.
Option D: Experience Cloud:
Experience Cloud supports user authentication for community portals but isn’t optimized as the primary system for SSO across B2C Commerce and other Salesforce clouds. It lacks the comprehensive identity management capabilities of Salesforce Identity. Relying on Experience Cloud for authentication would complicate integration with B2C Commerce, making it less seamless and scalable compared to using Salesforce Identity for a unified, secure login experience.
🔐 Reference:
Salesforce Help: “Salesforce Identity Overview”
Salesforce Commerce Cloud Help: “B2C Commerce Authentication”
Prep Smart, Pass Easy Your Success Starts Here!
Transform Your Test Prep with Realistic B2C-Solution-Architect Exam Questions That Build Confidence and Drive Success!