Arch-302 B2C Solution Architect Practice Questions
Prepare for Arch-302 with more than an answer.
- 1
What is the primary function of the 'B2C Commerce - Service Cloud Connector' regarding the 'Order' object?
Show answer details
Correct answer: A
The connector typically uses a pattern of virtualization (often via Salesforce Connect or custom LWC components calling OCAPI) to display order history. This avoids massive data duplication costs in Service Cloud while giving agents real-time visibility into order status, shipments, and line items directly from the B2C Commerce database.
- 2
A company operates three separate B2C Commerce storefronts for different regions (US, EU, APAC). They want a single Service Cloud instance to handle support for all regions. What is a key architectural consideration for the Service Cloud implementation?
Show answer details
Correct answer: A
A single Service Cloud org can support multiple B2C Commerce sites. The architecture requires careful configuration of the connector to handle multi-site mappings, ensuring that orders and customers are tagged with their source storefront (e.g., using a 'Storefront' field or Record Type) so agents know which region policies apply.
- 3
Which Salesforce API is most appropriate for high-volume, bulk import of product catalog data into B2C Commerce from an external PIM system?
Show answer details
Correct answer: D
For large catalogs (thousands/millions of SKUs), REST APIs like OCAPI are too slow due to HTTP overhead per call. The standard, most performant pattern is to upload an XML catalog file via WebDAV (or SFTP) and trigger a standard Import Catalog job in B2C Commerce.
- 4
A global fashion retailer is implementing a multi-cloud solution involving Salesforce B2C Commerce, Service Cloud, and Marketing Cloud. They require a 'Golden Record' for customer data to ensure a unified view across all channels. The technical architect has decided to use Service Cloud as the master for customer data. Which standard Salesforce architecture object should be enabled and utilized to natively support individual consumers in this B2C scenario?
Show answer details
Correct answer: D
In a B2C Solution Architecture, enabling Person Accounts in Service Cloud is the standard best practice. Person Accounts combine the properties of Account and Contact objects into a single record, accurately modeling an individual consumer rather than a business entity. This aligns with the B2C Commerce customer model and simplifies the synchronization of customer profile data across the multi-cloud landscape.
- 5
A Solution Architect is designing an 'Order on Behalf Of' (OOBO) workflow where Service Agents in Service Cloud need to log in to the B2C Commerce storefront to place orders for customers. Which specific integration mechanism provides the secure authentication token required for the Service Agent to seamlessly access the storefront session without asking the customer for their password?
Show answer details
Correct answer: B
For OOBO, the standard pattern involves the Service Cloud Connector requesting a session on behalf of the agent. This is typically achieved using the B2C Commerce OCAPI (Open Commerce API) where a specialized call is made to establish a customer session context that is bridged to the agent's credentials, often utilizing a 'On-Behalf-Of' flow or specific agent authentication endpoints provided by the connector infrastructure, allowing the agent to inherit the customer's cart context securely.
- 6
A retail client wants to implement an Abandoned Cart journey in Marketing Cloud. The trigger for this journey must be near real-time. Which architecture pattern best supports this requirement while minimizing custom development?
Show answer details
Correct answer: B
The 'Behavioral Triggers' feature in Marketing Cloud, combined with the Collect Tracking Code (part of the Einstein/Analytics integration) on the B2C Commerce site, is the modern, productized solution for Abandoned Cart. It captures the cart abandonment event and pushes it to a Data Extension that can directly inject contacts into a Journey Builder interaction without heavy custom integration work.
