ARC-801 Design and Implement B2B Multi-Cloud Solutions Exam Topics and Questions
These Salesforce Design and Implement B2B Multi-Cloud Solutions (ARC-801) exam topics are organized according to official exam domains to help candidates quickly verify coverage and focus on assessment rather than theory. Each domain is paired with topic-wise ARC-801 sample questions that reflect how objectives are tested in the actual exam. This structure enables efficient review, targeted self-assessment, and rapid identification of weak areas when preparing for the Salesforce Design and Implement B2B Multi-Cloud Solutions certification exam.
Let's Practice Free Salesforce ARC-801 Questions Aligned with Official Exam Topics
The B2B Solution Architect role sits at the intersection of business strategy and technical delivery across the Salesforce platform. This topic establishes the mental model the rest of the exam builds on: what distinguishes a solution architect from a functional consultant or a developer, where architectural decisions carry the most risk, and how the role operates across complex, multi-stakeholder B2B environments. Getting this foundation wrong skews every subsequent topic. How Introduction to B2B Solution Architect is tested Because no weighting...
The B2B Solution Architect role sits at the intersection of business strategy and technical delivery across the Salesforce platform. This topic establishes the mental model the rest of the exam builds on: what distinguishes a solution architect from a functional consultant or a developer, where architectural decisions carry the most risk, and how the role operates across complex, multi-stakeholder B2B environments. Getting this foundation wrong skews every subsequent topic.
How Introduction to B2B Solution Architect is tested
Because no weighting is published for this topic, treat it as foundational context rather than a place to bank marks. Items drawn from this area tend to probe whether you understand the scope of the architect role: when to escalate a decision, how to balance competing stakeholder priorities, and what separates an architectural recommendation from a configuration choice. Candidates lose ground here by applying a developer or admin mindset, choosing options that solve the immediate technical problem without accounting for the broader solution impact. The strongest responses reflect an understanding that the architect's job is to align delivery decisions to business outcomes, not to pick the cleverest technical approach. Expect scenario framing that puts you inside a client engagement and asks you to identify the right next move at the architectural level.
The ITExamsTopics practice test covers every topic in this exam, including the foundational material here. Running through the full bank before you sit shows you which areas need more work, so you are not guessing at your own gaps on exam day.
The question below tests how well you understand the architect's role when business and technical priorities pull in different directions.
Widgets Wonderful, a manufacturing company, wants to provide a better customer experience and enable field service resources to provide a quote to customers while still on site. The company has complex products that come with warranties that include preventativemaintenance work. Additionally, certain warranty repair work has specific SLAs associated with it. There are 10 Field Service team members and 20 sales representatives, all of whom need to view Salesforce Field Service objects and be able to create quotesfor the customer.
Widgets Wonderful's project owner has some questions regarding the number and types of licenses needed for the users and would like to better understand how warranties will be addressed.
Which two combined options should a Solution Architect suggest?
Choose 2 answers
Where the first topic defines what a solution architect is, this one defines what they do at the start of an engagement. Discovery is the phase where architectural mistakes are cheapest to fix, and the exam tests whether you know how to run it well. The risk is underestimating the breadth: discovery here spans stakeholder identification, document analysis, and structured inquiry, and the exam expects precision about each. β Framing the problem before proposing anything The earliest steps in discovery...
Where the first topic defines what a solution architect is, this one defines what they do at the start of an engagement. Discovery is the phase where architectural mistakes are cheapest to fix, and the exam tests whether you know how to run it well. The risk is underestimating the breadth: discovery here spans stakeholder identification, document analysis, and structured inquiry, and the exam expects precision about each.
β Framing the problem before proposing anything
The earliest steps in discovery are about resisting the urge to jump to a solution. Grasping the business issue means understanding what the customer is actually trying to change, which is often different from what they say they want. Outlining the use case turns that business issue into a scoped, structured problem statement that the rest of the design can be tested against. Candidates who skip this step in the exam, by choosing options that move straight to technical design, consistently pick the wrong path. The exam rewards the architect who slows down, validates the problem definition, and only then begins shaping a solution. Getting started with discovery properly also means setting up the right conditions: agreeing on scope, establishing access to the right people, and ensuring you are solving the right problem from day one.
β Stakeholder identification and structured conversation
Pinpointing key players is an architectural skill, not an administrative one. The exam tests whether you know which roles carry decision-making authority versus which carry institutional knowledge, and why conflating the two causes problems later. Talking to key players and various teams then demands a different approach for each audience: executives need business-case framing, technical teams need specificity, and end users need process-level conversation. Responding to discovery inquiries is the reverse flow: handling the questions that come back at you, particularly when they expose gaps or conflict with earlier assumptions. The exam places you in situations where a stakeholder's answer changes the design direction, and the strongest response is always the one that acknowledges the implication and adapts, rather than defending the original approach.
β Working with existing documentation
Architectural diagrams, customer journey maps, and process maps each reveal something different about the current state. An architectural diagram shows you the technical landscape; a journey map shows you where customers experience friction; a process map shows you where work actually flows versus where it is supposed to flow. The exam expects you to know what each document type tells you and, more importantly, what it cannot tell you. Candidates lose marks by treating a journey map as a substitute for a process map, or by accepting an architectural diagram as an accurate picture of the current system without verifying it. Document review in discovery is a cross-check, not a shortcut. The skill being tested is knowing when documentation confirms your understanding and when it raises a question you still need to answer.
How Discovery and Customer Success is tested
Items in this topic are scenario-heavy. You will be placed inside a live discovery conversation or handed a partial set of documents and asked what to do next. The exam rewards the response that follows the right sequence: understand the business issue before outlining a use case, identify the right stakeholders before conducting interviews, and treat documents as inputs to validate rather than answers to accept. Marks are lost when candidates jump ahead, choosing options that propose a solution before the problem is fully scoped, or that talk to the wrong stakeholder at the wrong stage. A second trap is treating all stakeholders as equivalent. The exam distinguishes between who approves, who knows, and who is affected, and the strongest options reflect that distinction. Expect at least one scenario where a document and a stakeholder contradict each other, and you have to decide which one to act on.
Working through a timed set of scenario-based items from the ITExamsTopics practice test is the most efficient way to check whether your discovery sequencing instincts are exam-ready, without re-reading theory you may already know.
The question below puts you in a discovery scenario and asks you to choose the right architectural move given what has and has not yet been established.
A Solution Architect has gathered requirements from discovery with Northern Trail Hot Tubs below:
* Northern Trail Hot Tubs sells through a B2B2C model with Dealers.
* Northern Trail Hot Tubs tracks Dealer Opportunities in Salesforce, but wishes to have more insight into the sales process from its Dealers.
* Dealers would like to be able to get custom Hot Tub pricing quickly from Northern Trail Hot Tubs without having to wait for configuration estimates to come back from Northern Trail Hot Tubs.
* Northern Trail Hot Tubs supports itsDealers and Customers directly, and Dealers would like better insight into support that their Customers receive.
Which capabilities should a Solution Architect suggest to provide to Northern Trail Hot Tub Dealers?
After the discovery phase, the exam shifts into solution design territory, and the cart-to-quote process is one of the most technically layered areas in B2B Salesforce work. This topic covers the end-to-end commercial transaction flow: how a buyer moves from product selection through configuration, pricing, and quoting. The design decisions here touch CPQ, Commerce, and the integrations that connect them, and the exam tests whether you can make the right call when those systems interact under real business constraints. How...
After the discovery phase, the exam shifts into solution design territory, and the cart-to-quote process is one of the most technically layered areas in B2B Salesforce work. This topic covers the end-to-end commercial transaction flow: how a buyer moves from product selection through configuration, pricing, and quoting. The design decisions here touch CPQ, Commerce, and the integrations that connect them, and the exam tests whether you can make the right call when those systems interact under real business constraints.
How Designing Cart to Quote Solutions is tested
No weighting is published for this topic. Items here tend to be design-decision scenarios: given a set of business requirements around product configuration, pricing rules, or quote generation, which architectural approach best satisfies them. The exam rewards candidates who understand the functional boundary between a shopping cart experience and a formal CPQ quoting process, and who can identify where a custom build introduces unnecessary risk versus where it is genuinely required. A common trap is choosing the most technically sophisticated option when a standard platform capability covers the requirement. Another is failing to account for downstream impacts: a pricing rule change in CPQ, for example, ripples into billing and revenue recognition, and the exam expects you to see that chain. Candidates who treat cart-to-quote as a single system rather than a coordinated set of capabilities consistently pick options that solve one layer while breaking another.
The ITExamsTopics PDF and practice test together give you coverage across every topic, including cart-to-quote design scenarios. The PDF is useful for focused review; the practice test shows you how these items behave under timed conditions.
The question below presents a cart-to-quote design requirement and asks you to select the approach that best fits the stated constraints.
Cart-to-quote design decisions do not live in isolation; they depend on clean data flows and well-governed integrations across the wider enterprise system landscape. This topic is where the exam tests your ability to reason across system boundaries. ERP, CRM, APIs, MuleSoft, Salesforce Billing, and data governance all appear here, and the questions are designed to expose candidates who understand each piece individually but cannot reason about how they interact. β ERP, CRM, and the line between them The exam does...
Cart-to-quote design decisions do not live in isolation; they depend on clean data flows and well-governed integrations across the wider enterprise system landscape. This topic is where the exam tests your ability to reason across system boundaries. ERP, CRM, APIs, MuleSoft, Salesforce Billing, and data governance all appear here, and the questions are designed to expose candidates who understand each piece individually but cannot reason about how they interact.
β ERP, CRM, and the line between them
The exam does not ask you to be an ERP specialist. It asks you to know where ERP ends and CRM begins, and what goes wrong when that line is blurred in a solution design. ERP systems own financial records, inventory, and supply chain processes. CRM owns the customer-facing commercial relationship. Placing business logic in the wrong system creates data integrity problems, synchronisation failures, and audit risks. The examinable point is not the definition of either system but the consequences of misaligning them. Understanding how ERP fits within a system interaction framework means being able to read an architectural diagram and identify which system should be the system of record for a given data entity, and what the integration contract between the two systems needs to enforce.
β Salesforce APIs and MuleSoft as integration tools
Knowing the Salesforce API surface means knowing which API is appropriate for which integration pattern: bulk data loads, real-time event-driven updates, and synchronous callouts each demand a different approach. The exam tests whether you can match the integration requirement to the right API capability without over-engineering the solution. MuleSoft sits above that layer as an integration platform: it handles orchestration, transformation, and protocol mediation across systems that would otherwise require bespoke point-to-point connections. The architectural question the exam poses is not whether to use MuleSoft but when its introduction is justified by the complexity of the integration landscape. Candidates who treat MuleSoft as the default answer for every integration scenario, or who ignore it when it is clearly the right tool, both lose marks.
β Salesforce Billing, data governance, and the value of governing well
Salesforce Billing extends the quote-to-cash process into revenue recognition and invoicing, and the exam expects you to know where it connects to CPQ and where it connects to ERP. The integration points are the examinable surface, not the billing configuration detail. Data governance, in this context, means the policies, ownership rules, and quality standards that determine which data can be trusted and acted on across the enterprise. The exam distinguishes between knowing that data governance exists and understanding the specific advantages it delivers: reduced integration failure rates, clearer audit trails, and faster resolution of data conflicts. Candidates who treat data governance as a compliance checkbox rather than an architectural enabler choose options that defer governance decisions to implementation, where they cost far more to fix.
How Governing of Data and Integration Processes is tested
This topic generates some of the most technically demanding items in the exam. Scenarios typically present a multi-system landscape, describe a data flow or integration requirement, and ask which design decision best satisfies the stated constraints. The exam rewards candidates who can identify the correct system of record, choose the appropriate API or integration pattern, and flag governance risks before they become architectural problems. Marks are lost in two places. First, candidates who know the individual components but cannot reason about their interactions will choose options that solve the immediate technical problem while creating a downstream data conflict. Second, candidates who treat Salesforce Billing or MuleSoft as standalone topics, disconnected from the broader integration governance picture, miss the scenarios where those tools are the answer precisely because of how they connect to other systems. The governance sub-topic is frequently embedded inside a larger scenario rather than tested in isolation.
If this topic is a weak area, checking it with targeted questions from the ITExamsTopics bank is faster than re-reading documentation. You will quickly see whether your gaps are in API selection, ERP/CRM boundary reasoning, or governance application.
The question below places you in a multi-system integration scenario and asks you to identify the architectural decision that best preserves data integrity across the landscape.
Once the commercial transaction is complete, the architectural challenge shifts to the service relationship. Service Cloud is the primary platform for post-sales engagement in B2B Salesforce environments, and this topic tests whether you can design service solutions that match the operational complexity of enterprise accounts. The integration points with Sales Cloud, the data model for cases and entitlements, and the configuration decisions that affect agent productivity all sit within scope here. How Engaging with Customers Post-Sales (Service Cloud) is tested...
Once the commercial transaction is complete, the architectural challenge shifts to the service relationship. Service Cloud is the primary platform for post-sales engagement in B2B Salesforce environments, and this topic tests whether you can design service solutions that match the operational complexity of enterprise accounts. The integration points with Sales Cloud, the data model for cases and entitlements, and the configuration decisions that affect agent productivity all sit within scope here.
How Engaging with Customers Post-Sales (Service Cloud) is tested
No weighting is published for this topic. Items here are typically scenario-based: a B2B customer has a post-sales support requirement, and you need to identify which Service Cloud capability or design decision best addresses it. The exam rewards candidates who understand the difference between configuring Service Cloud for a consumer context versus a B2B enterprise context, where account hierarchies, entitlements, and SLA enforcement are architectural concerns rather than optional features. A frequent trap is choosing a solution that works for a single-contact consumer case but fails when applied to an enterprise account with multiple contacts, contract-level entitlements, and escalation rules. Another is underestimating the integration surface between Service Cloud and the systems that feed it: ERP data about order status, CPQ data about what was sold, and billing data about payment status all affect how service cases are handled and resolved.
The ITExamsTopics practice test includes Service Cloud scenarios alongside every other topic in the exam. Seeing how post-sales items are framed before you sit helps you recognise the B2B-specific angle the exam consistently applies.
The question below tests your ability to design a Service Cloud solution that meets the specific demands of a B2B enterprise account structure.
Post-sales service and pre-sales marketing often share the same customer data but operate on very different timelines and logic. Marketing Cloud Account Engagement, formerly Pardot, handles B2B marketing automation: lead nurturing, scoring, and the handoff to sales. The exam tests whether you can position it correctly within a multi-cloud architecture, particularly where it connects to Sales Cloud and where its data model creates design constraints you need to plan around. How Marketing Cloud Account Engagement (Pardot) is tested No weighting...
Post-sales service and pre-sales marketing often share the same customer data but operate on very different timelines and logic. Marketing Cloud Account Engagement, formerly Pardot, handles B2B marketing automation: lead nurturing, scoring, and the handoff to sales. The exam tests whether you can position it correctly within a multi-cloud architecture, particularly where it connects to Sales Cloud and where its data model creates design constraints you need to plan around.
How Marketing Cloud Account Engagement (Pardot) is tested
No weighting is published for this topic. The exam is not testing Pardot administration. It is testing whether you, as a solution architect, can make the right design decisions about where Pardot fits in a broader multi-cloud solution. Items reward candidates who understand the sync relationship between Pardot and Sales Cloud: what syncs, what does not, and what breaks when the two systems hold conflicting records. The lead-to-opportunity handoff is a common scenario anchor, and the strongest responses account for both the marketing logic that triggers the handoff and the sales process that receives it. Candidates lose marks by treating Pardot as an isolated marketing tool rather than a system with a defined integration contract with the rest of the Salesforce platform. Expect scenarios where a business requirement touches both marketing automation and CRM data, and you need to identify the architectural decision that keeps both systems consistent.
The ITExamsTopics question bank spans every topic in this exam. For a topic like this one, where the exam tests architectural positioning rather than configuration depth, volume of practice items helps you calibrate how much detail is actually expected.
The question below asks you to make an architectural decision about how Marketing Cloud Account Engagement integrates with the broader Salesforce solution.
The final topic pulls everything together in the format that puts the most pressure on candidates: a case study requiring you to design, communicate, and defend a solution across multiple Salesforce clouds and multiple orgs. The earlier topics gave you the components; this one tests whether you can assemble them into a coherent design under realistic constraints, respond to feedback without losing architectural integrity, and demonstrate the kind of leadership that distinguishes a solution architect from a senior developer. β...
The final topic pulls everything together in the format that puts the most pressure on candidates: a case study requiring you to design, communicate, and defend a solution across multiple Salesforce clouds and multiple orgs. The earlier topics gave you the components; this one tests whether you can assemble them into a coherent design under realistic constraints, respond to feedback without losing architectural integrity, and demonstrate the kind of leadership that distinguishes a solution architect from a senior developer.
β From brief to design
Creating a solution design from a case study starts with reading the scenario carefully enough to identify what is actually being asked. The exam rewards candidates who anchor their design in the stated business requirements rather than defaulting to the most technically sophisticated option available. Illustrating a solution design means being able to communicate it clearly to different audiences: the business stakeholder who needs to understand the value, and the technical team who needs to build it. The exam tests both directions. Refining the design according to feedback is where many candidates struggle, because it requires holding your original reasoning firmly enough to defend it when the feedback is wrong, and loosening it quickly enough to adapt when the feedback is right. The skill is not stubbornness and not compliance; it is architectural judgement.
β Leadership and multi-org complexity
Demonstrating business, delivery, and technical leadership in a case study context means showing that you can operate across all three registers simultaneously. Business leadership means keeping the design connected to the commercial outcome. Delivery leadership means accounting for implementation risk, timeline, and team capability. Technical leadership means making the call on architecture when the options are genuinely ambiguous. The exam places you in scenarios where these three pull in different directions, and the strongest response balances all three rather than optimising for one at the expense of the others. Analysing a case study involving multiple organisations and cloud platforms adds the structural complexity of org boundaries: data sharing, identity, and process handoffs all behave differently when they cross an org boundary, and the exam expects you to know which assumptions break and which hold.
How Case Study:Multi-Cloud and Multi-Org is tested
No weighting is published for this topic. Case study items are the most scenario-dense in the exam. You are typically given a business context that spans multiple Salesforce products and organisational boundaries, then asked to make or evaluate a design decision. The exam rewards candidates who can trace the impact of a design choice across the full solution: a decision about org structure affects integration patterns, which affects data governance, which affects the service experience. Candidates who evaluate each layer in isolation consistently choose options that solve one problem while creating another. A second area of lost marks is the leadership dimension. Items that ask how an architect should respond to stakeholder feedback, conflicting technical opinions, or a delivery constraint are testing judgement, not product knowledge. The strongest options in those scenarios reflect an architect who shapes the outcome rather than one who simply reports the trade-offs.
The ITExamsTopics practice test lets you work through multi-cloud scenario items in the same timed, single-attempt conditions the real exam uses. That pressure is part of what the case study format is testing, and you want to have felt it before exam day.
The question below presents a multi-org scenario and asks you to identify the design decision that best satisfies the architectural and business constraints described.
Ready to Start Practicing?
Access all questions and start your exam preparation journey
Upgrade to Full ARC-801 Exam Questions π