UUS Practice Tests⌕ Search
IT Certifications · Arch-301

Salesforce B2B Solution Architect Exam Practice Test

B2B solution architecture connects Salesforce data and workflows to the needs of business buyers, sales teams, and external systems. The practice material uses scenarios involving account hierarchies, order-data validation, contract pricing, approval paths, audit history, and secure access to portal documents. These examples help frame architectural choices around data quality, maintainability, integration behavior, and confidentiality.

Exam overview

Exam providerSalesforce
Exam codeArch-301
CategoryIT Certifications

About the Salesforce B2B Solution Architect Exam

Architects must translate business policies into platform designs that remain consistent across user interfaces, automation, and integrations. Relevant decisions include when to enforce cross-field and required-value rules, how to separate frequently revised pricing logic from application code, and how to route sensitive credit-limit changes for review without delaying routine updates. Data modeling also matters: account relationships can represent parent organizations, subsidiaries, and business units, while large historical datasets call for targeted retrieval rather than loading every record at once. Integration design includes supporting incremental reads that resume from a successful checkpoint. Security and governance work includes protecting documents exposed through a B2B portal and selecting field-history capabilities for audit needs. These scenarios emphasize matching Salesforce mechanisms to the scope, change frequency, volume, and risk of each requirement.

Sample Practice Questions

Review a selection from this exam's published US Practice Tests practice bank.

Question 1

A business wants to prevent users from entering an invalid combination of values across two fields, such as requiring a delivery method to match the selected delivery location. Which platform feature is the most direct fit?

  1. AA validation rule that evaluates the related field values
  2. BA dashboard filter
  3. CA sharing rule
  4. DA list view chart
Show answerCorrect answer: A

A validation rule can evaluate multiple fields and block saving when their combination violates a business constraint. Dashboards and list view charts display information, while sharing rules govern record access.

Question 2

A business needs to calculate a contract price using several rules that change frequently and must be reviewed by pricing specialists. Which solution approach best separates pricing policy from application code?

  1. AHard-code each contract's price into storefront page logic.
  2. BMaintain pricing rules in an appropriate configurable pricing capability and have the purchasing flow use its results.
  3. CAsk buyers to enter the final negotiated price on each order.
  4. DCreate a new Salesforce user for each price rule.
Show answerCorrect answer: B

Frequently changing business rules are generally easier to govern when represented in a configurable pricing capability rather than embedded in page code. The purchasing flow can consume the calculated result while preserving appropriate review and control.

Question 3

A company wants its sales team to see a consolidated view of a customer organization, including its subsidiaries and related business units. Which Salesforce data-modeling approach is the most direct starting point?

  1. ARepresent the organization and its subsidiaries with parent-child Account relationships.
  2. BCreate a separate Contact for each subsidiary and use Contact roles to connect them.
  3. CStore subsidiary names in a multiselect picklist on the parent Account.
  4. DCreate a custom object for every organizational level and avoid Account relationships.
Show answerCorrect answer: A

The Account hierarchy is designed to represent parent and subsidiary organizations and supports navigation across related accounts. A multiselect picklist cannot model independent subsidiary records or their relationships.

Question 4

A business needs to ensure that changes to a customer's credit limit are reviewed, but routine updates to the customer’s phone number should remain immediate. Which design best separates these behaviors?

  1. ARequire every account edit to be approved
  2. BUse a controlled approval process for credit-limit changes and leave routine fields outside that process
  3. CPrevent all users from editing accounts
  4. DSend a weekly report of all account field changes
Show answerCorrect answer: B

A targeted approval process can require review for the sensitive credit-limit change without unnecessarily blocking unrelated routine maintenance. Requiring approval for every edit creates avoidable friction, while a report does not enforce review before a change takes effect.

Question 5

A team is designing an integration that reads Salesforce records frequently but rarely changes them. The external system needs to resume from the last successful run without reprocessing the entire dataset. Which approach is most appropriate?

  1. AUse a query strategy with a persisted checkpoint such as the last processed modification time or identifier
  2. BDownload every record on each run and discard duplicates afterward
  3. CUse a manual export performed by an administrator each day
  4. DStore a complete copy of the dataset in a URL parameter
Show answerCorrect answer: A

A persisted checkpoint lets the integration request records changed since its last successful point and resume predictably. The checkpoint must be designed carefully for ordering, overlapping updates, and failures, but it is more efficient and manageable than repeatedly exporting everything.

Question 6

A company must retain a history of changes to a small set of important fields on customer records for audit review. Which Salesforce capability should the architect evaluate first?

  1. AField History Tracking
  2. BA custom tab color
  3. CA compact layout
  4. DA list view chart
Show answerCorrect answer: A

Field History Tracking records changes to selected fields, including information such as the prior and new values, the user, and the time of change, subject to platform limits and retention considerations. Page presentation and list-view features do not provide an audit trail.

Question 7

A business wants to ensure that an order cannot be submitted unless required delivery information is present and valid. Where should the core data-quality rule be enforced so it applies consistently across user interfaces and integrations?

  1. AOnly in storefront JavaScript validation.
  2. BOnly in a training guide for order-entry users.
  3. CWith server-side Salesforce validation appropriate to the order data model.
  4. DOnly in a report that flags incomplete orders after submission.
Show answerCorrect answer: C

Server-side validation provides a consistent enforcement point for records created through different interfaces, including integrations. Client-side checks can improve usability but should not be the only control.

How to use this practice test

The free US Practice Tests practice bank contains 50 published questions; each session presents up to 20 random questions. Use a session to identify which architecture decisions need more work, then review the displayed results to spot patterns across data quality, integrations, security, and governance.

Preparation tips

  • For validation scenarios, distinguish record-level rules that must apply across interfaces and integrations from checks limited to a particular screen or interaction.
  • Compare ways to keep frequently changing contract-pricing policies reviewable by pricing specialists and separate from application code.
  • Sketch account relationships for organizations with subsidiaries and business units; consider how users will navigate the hierarchy and access related records.
  • For large historical objects, plan indexed or selective retrieval and incremental integration checkpoints rather than attempting to load the full dataset repeatedly.
  • Map sensitive changes and portal documents to the required approval, record access, and field-history controls; verify that routine updates remain unaffected.
Official sourceOfficial exam page ↗