Explanation

UC already mastered product and pricing data inside B2B Commerce. To support Salesforce CPQ and Sales Cloud, the cleanest architecture is to continue using B2B Commerce as the single source of truth and share that controlled data with CPQ. CPQ will then apply discounting rules, approval chains, and quoting logic. This approach keeps catalog consistency while maintaining ERP as the fulfillment system.

🟩 Correct Option: B — Product & Pricing mastered in B2B Commerce, integrated to CPQ
Maintaining the product and pricing catalog in B2B Commerce preserves the single source of truth that UC already uses. CPQ can consume this information through lightweight REST integrations, enabling quoting, discounting, approvals, and upsell logic. After orders are created, passing the final transaction to the ERP for fulfillment preserves UC’s current operational model without introducing unnecessary system shifts.

❌ Incorrect Options

A — Master data in ERP and integrate to both systems
Changing the master data source to ERP introduces major redesign and disrupts the proven B2B Commerce catalog management flow. It increases integration complexity and contradicts UC’s current architecture. It also delays benefits for the Sales team because ERP-based catalog changes would require new governance processes and additional development effort.

C — Products in B2B Commerce, pricing in CPQ
Splitting products and pricing across two different master systems creates significant complexity. Product and pricing need to remain tightly linked for catalog consistency, promotions, and variant rules. Dividing ownership leads to synchronization issues, mismatched pricing scenarios, and additional integration overhead between CPQ and Commerce.

D — Master in CPQ and push to B2B Commerce
This reverses UC’s existing architecture and forces all product/pricing management to move into CPQ, which is not designed to manage full commerce catalogs. CPQ is optimized for selling workflows, not large-scale B2B Commerce catalog administration. This adds effort, disrupts existing teams, and creates unnecessary dependencies.

Summary
B2B Commerce is already the authoritative source for UC’s product and pricing. Extending that data to CPQ enables Sales teams to quote consistently using the same catalog as customers. CPQ then layers discounting and approval logic, while ERP continues handling fulfillment. This solution remains aligned with UC’s existing systems and avoids unnecessary architectural complexity.

📚 Reference
Salesforce B2B Commerce & CPQ Data Strategy Guidance

Explanation

Universal Export explicitly wants to protect existing investment and avoid new licenses. Building a custom duplicate of an existing Salesforce product directly contradicts that goal, creates long-term technical debt, and increases maintenance cost. The architect’s role is to challenge the custom approach and redirect toward the out-of-the-box module while quantifying the real business value.

Correct Answers

✅ B. Advise the customer to use the out-of-the-box approach to avoid unnecessary technical debt.
Reinventing a native Salesforce feature with custom code creates ongoing upgrade risk, higher support cost, and slower release cycles. Advising the use of the standard product respects the customer’s stated goal of maximizing current investments and is the core responsibility of a Solution Architect.

✅ D. Evaluate the business benefit of the requested functionality to see if it justifies investment in the Salesforce product.
Even if the module requires additional licenses, the architect must quantify the ROI (faster time-to-value, lower TCO, future-proofing, reduced risk) versus building and maintaining a custom clone. This evidence-based comparison helps the customer make an informed licensing decision instead of defaulting to “build”.

Incorrect Answers

❌ A. Begin requirements gathering for integrations and data migration
Starting detailed technical work assumes the custom-build decision is already approved. This is premature and signals acceptance of the wrong path when the architect should first push back on duplicating native functionality.

❌ C. Consult with the IT department to review the extension requirements.
Engaging IT to scope a custom extension again accepts the build direction too early. The architect must first address the strategic misalignment (re-creating something Salesforce already provides) before diving into technical reviews.

Summary
Respect the customer’s “no new products” stance by strongly recommending the native Salesforce module (B) and performing a clear business-value vs. license-cost analysis (D). Only if the standard product truly fails to meet critical needs should custom development even be considered.

Reference
Well-Architected Framework

Explanation

The core challenge when implementing a new B2B Commerce channel is mitigating channel conflict and addressing the sales team's commission fears. The Solution Architect must articulate a strategy where the portal is a complementary asset, defining a clear operational boundary. This separation must position the human sales force for high-value, complex, and strategic activities that justify their commissions.

✅ Correct Option

A. Highlight that the B2B portal is meant to tackle more routine, low-complexity sales, allowing the Sales team to focus on the more complex sales and priority accounts.
This strategic distinction is essential for adoption. By automating repetitive, transactional, and low-complexity orders, the portal reduces the administrative workload on the sales team. This enables them to dedicate valuable time and expertise to closing larger, custom deals and nurturing high-value, priority accounts, which typically yield higher commissions.

D. Highlight that the B2B portal will help the company grow and expand into new geographies where the company does not currently have a sales footprint, resulting in more rewards for everyone.
Presenting the B2B portal as a market expansion tool effectively addresses the fear of cannibalization. By targeting new customer segments or unserved geographic regions where the sales team lacks a presence, the portal generates new, incremental revenue. This expands the overall market opportunity, ensuring more rewards for the entire sales ecosystem.

❌ Incorrect Option

B. Highlight that the B2B portal will be a useful tool to help improve customer communications and enhance customer engagement by providing faster updates on their orders as they are fulfilled.
While providing faster order updates is a key benefit of B2B self-service, this feature primarily addresses the customer experience and operational transparency. It fails to directly address the executive sponsor's crucial concern regarding sales channel conflict and the threat to their commission structure.

C. Highlight that the B2B portal is meant to handle high-complexity sales that are ideal for automation, leaving the Sales team to handle less complex, higher-margin sales.
This statement is structurally incorrect regarding B2B sales roles. High-complexity sales demand human consultation, negotiation, and relationship management, making them unsuitable for full automation. The sales team typically handles high-margin complexity. Automating high-complexity sales would directly threaten their most valuable activities.

Summary
To gain executive and sales team buy-in, the Solution Architect must define the B2B portal's role clearly. It should serve as a self-service engine for routine, transactional, low-complexity orders, thereby freeing up the human sales team to concentrate on strategic accounts and complex negotiations. Additionally, leveraging the portal for market expansion ensures it generates new revenue rather than cannibalizing existing sales channels.

Reference
These strategic deployment principles are aligned with best practices defined in Official Salesforce B2B Commerce Documentation and Trailhead Content pertaining to channel strategy and sales force enablement.

Explanation

The architect must design a data flow that enables a seamless cart-to-quote journey across B2B Commerce and CPQ, while ensuring the external ERP receives accurate information for order fulfillment. The core challenge is to prevent data silos and define clear handoff points between systems.

✅ A. Product and Pricing are set up with CPQ as the source of record.
This establishes CPQ as the master system for all product and pricing data. Using a single source of truth is critical to ensure that prices, discounts, and configured products are consistent between the customer's self-service cart (B2B Commerce) and the sales rep's quote (CPQ).

✅ B. The source for the data feed to ERP is the CPQ Order object.
Since fulfillment occurs in a third-party ERP, the architect must define what data is sent and from which object. The Order object in CPQ holds the final, approved transaction details and is the correct system of record to initiate the fulfillment process in the external system.

❌ C. All data points on products should be mapped and replicated between CPQ and B2B Commerce.
This approach of replicating all data is inefficient and creates a risk of inconsistency. The correct integration strategy is to have one source system (CPQ) and share necessary data with B2B Commerce, not to duplicate all information in both places.

❌ D. Cart and Order record owners are mapped to Quote and Quote Line record owners.
While user ownership is a configuration item, it is not a primary consideration for the overall data flow design. The key data flow decisions concern the master source of product data and the integration point for order fulfillment, not record ownership mappings.

📝 Summary
The architect's main data flow considerations are to centralize product and pricing data in CPQ to ensure consistency and to designate the CPQ Order object as the official source for sending data to the ERP. This creates a reliable, integrated process from the initial cart to final fulfillment.

Reference:
This aligns with the data governance and integration strategy principles covered in the official Salesforce B2B Solution Architect Exam Guide, particularly regarding designing data flows for multi-cloud solutions and integrations with external systems like ERP.

Explanation:

Why D is optimal

Single pricing/catalog pipeline:
The Salesforce CPQ ↔️ B2B Commerce connector is designed to sync product/pricing objects from CPQ into B2B Commerce—a one-way push that keeps the storefront aligned with CPQ quoting and contract pricing logic. You feed CPQ from the ERP (the upstream master), then publish to Commerce via the connector.

Promotions belong in Commerce:
Seasonal events, coupons, qualifiers/segments, and storefront discounts are managed natively in B2B Commerce Promotions, which target specific customer groups and campaigns on the site.

Billing is the SoR for invoices:
Salesforce Billing handles invoice generation, payments, and revenue processes. You then present invoices to portal buyers on your B2B Commerce/Experience site via Lightning/Experience components or Transaction Management exposure—don’t author invoices in Commerce.

Why the other options fall short

A:
Says ERP ➜ B2B Commerce via the CPQ Connector to CPQ — the direction is wrong. The connector syncs from CPQ to B2B Commerce, not ERP to B2B Commerce or B2B to CPQ. Promotions and surfacing Billing data are fine, but the core product/pricing flow is incorrect.

B:
Puts promotions in CPQ and invoicing in B2B Commerce pushed to Billing. Promotions should be storefront-driven (Commerce), and Billing, not Commerce, must own invoices.

C:
Proposes pushing ERP to both CPQ and B2B Commerce in parallel. That duplicates pricing/catalog governance and bypasses the standard CPQ ➜ B2B Commerce sync path, risking drift between channels.

References
CPQ ↔️ B2B Commerce Connector (sync CPQ product/pricing to Commerce) — Trailhead & Help.
B2B Commerce Promotions (seasonal discounts, coupons, segments).
Salesforce Developers
Salesforce Billing (invoicing/payments as SoR) and surfacing in Experience/B2B sites.

Final pick: D — aligns with standard patterns: ERP (master) ➜ CPQ (Salesforce pricing/quote brain) ➜ B2B Commerce (storefront), with promotions in Commerce and invoicing in Billing, displayed in the portal.