Free Arch-302 sample questions

Correct answer: Person Accounts

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.

Correct answer: B2C Commerce Business Manager User Login via OCAPI 'Agent' Header

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.

Correct answer: Implement the 'Behavioral Triggers' feature in Marketing Cloud coupled with the Collect Tracking Code on the B2C Commerce storefront.

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.

Correct answer: The B2C Commerce Customer Number

The B2C Commerce Customer Number is a unique, system-generated immutable ID for a customer profile in B2C Commerce. Best practice integration patterns store this Customer Number in a custom field on the Service Cloud Person Account (often named 'B2C_Customer_No__c') and use it as an external ID for upsert operations to ensure accurate linking and prevent duplicates.

Correct answer: Salesforce Order Management (SOM)

Salesforce Order Management (SOM) contains the logic and data structures (Change Orders) to handle complex return calculations. While the tax calculation itself might be delegated to an external tax provider integration triggered by SOM, SOM itself orchestrates the logic to determine the refundable amount based on the return policy and original order data.

Correct answers: Pre-built API designs and implementations for common retail use cases (e.g., Inventory, Order, Products); Implementation of best practices for reliability, error handling, and retry mechanisms

The Accelerator provides pre-built assets, including RAML specifications and implementation templates, which significantly accelerate the development of standard retail integrations.

Accelerators encapsulate architectural best practices, ensuring that the resulting integrations are robust, scalable, and maintainable from day one.