Free B2C-Commerce-Architect Practice Test Questions (2026)

Explanation:

✅ Option D: A custom attribute of type enum-of-string (single selectable value)

Since the products are categorized into three distinct types (boots, sandals, sneakers), and the business requirements specify that the messaging on the Product Detail page is different for each type and that customers should be able to filter their Product Search Results by product type, an enum-of-string attribute with a single selectable value is the best choice. This allows the customer to select one value for each product, which makes it easier to differentiate between boots, sandals, and sneakers, both for displaying different messages and for filtering search results.

Why "enum-of-string (single selectable value)" works:
1. It provides a predefined set of options (boots, sandals, sneakers), ensuring consistent categorization.
2. Since only one product type is applicable at a time, the single-select nature of the enum is appropriate.
3. This format also allows easy filtering for customers, as search filters typically rely on a single, well-defined value.

❌ Option A: A custom attribute of type string containing comma separated values.

This option would store the product types as a comma-separated string (e.g., "boots, sandals, sneakers"), which is not ideal. It complicates filtering and searching because the system would need to parse the string to check for specific values, and multiple types might be included in a single product, which conflicts with the business requirement of having one type per product. This would also make it more challenging to apply the required custom messaging per product type.

❌ Option B: A custom attribute type set-of-string containing multiple values.

While a set-of-strings allows multiple values, this is not suitable here because the product is restricted to only one type (boots, sandals, or sneakers). Using a set-of-string would allow customers to select multiple types, which is unnecessary and confusing for this particular scenario. The business requirement specifies that each product should only have one type, and filtering based on multiple types is not required.

❌ Option C: A custom attribute of type enum-of-string (multiselect able value).

A multiselect enum-of-string is inappropriate because it allows selecting multiple values for the product type, which conflicts with the business requirement that each product should belong to only one category (boots, sandals, or sneakers). Since a product can only have one type, a single-select enum is more fitting.

Explanation:

✅ Why these options are correct?

Option D: A service configuration, a service profile configuration, and a service credential configuration.

Explanation:

In Salesforce B2C Commerce, to integrate with external systems (like OMS) using REST services, the correct configurations are:

1. Service Configuration: This defines the type of service being integrated with (in this case, REST services). It allows the B2C Commerce platform to know how to communicate with the OMS.

2. Service Profile Configuration: This associates the specific service configuration to the actual external system (OMS in this case). It maps the connection details and any other configurations specific to the service.

3. Service Credential Configuration: This stores the credentials necessary to authenticate the B2C Commerce platform with the OMS. These credentials can be API keys or other forms of authentication (e.g., OAuth tokens).

The combination of these configurations ensures secure and effective communication between B2C Commerce and the OMS.

❌ Why these options are incorrect?

Option A: A service configuration, a hostname alias configuration, and a user credential configuration.

Explanation:

While service configuration and user credential configuration are required, the hostname alias configuration is not directly relevant to integrating with an external service via REST. The hostname alias configuration typically helps manage different environments or URLs for routing requests, but it is not a key requirement for the integration in this context.

Option B: A service profile configuration, a WAF configuration, and a service credential configuration.

Explanation:

While service profile configuration and service credential configuration are needed, the WAF configuration (Web Application Firewall) is generally not part of the standard integration setup. WAF configurations help with security at the network layer and aren’t directly involved in setting up a REST service integration.

Option C: A service configuration, a service profile configuration, and a user credential configuration.

Explanation:

While service configuration and service profile configuration are needed, user credential configuration is typically used in cases where you’re working with user-based authentication (e.g., basic authentication for REST services). However, for external systems like OMS, service credential configuration is typically used instead of user credentials. This makes this option incorrect.

Explanation:

Why Option B?

✅ Persistent Storage (Custom Object) for Survey Data
Ensures no data loss if the API fails (stores survey responses reliably).
Batch processing via a job improves reliability (retries failed submissions).

✅ Handles Skipped Surveys (Email Fallback)
The custom object tracks which customers skipped the survey, enabling email follow-ups.

✅ Avoids OMS XML Parsing Issues
Since the survey data is stored separately (not embedded in the order XML), it prevents OMS parsing failures.

Why Not Other Options?

❌ A. Session-based storage
Session data is volatile (lost if the user leaves or the session expires).
Not reliable for retries or email follow-ups.

❌ C. Hybrid (Real-time + Job)
Real-time API calls can still fail, requiring retries.
Less efficient than a pure batch/job approach (Option B).

❌ D. Force real-time retries + OMS parser update
Does not guarantee data persistence (if API keeps failing).
Depends on OMS changes (out of the Architect’s control).

Best Practice & Reference:
Use Custom Objects for transient but critical data (e.g., surveys).
Batch jobs (instead of real-time) for resilient third-party integrations.
Salesforce B2C Commerce recommends asynchronous processing for reliability.

Explanation:

Why Option D?

✅ Respects spi.basket.addResolveInSameRequest Quota
By wrapping the operation in a transaction and rolling it back, the system avoids multiple add/remove calls, which trigger quota violations.
The basket remains unchanged after calculation, maintaining the original state.

✅ Maintains Business Requirement (Pre-Checkout Shipping Estimates)
Customers still see real-time shipping costs on the PDP without permanently altering their cart.

✅ Optimized Performance
Single transaction reduces API calls compared to repeated add/remove cycles.

Why Not Other Options?

❌ A. Omit removal & pre-add the product
Forces items into the cart prematurely, hurting UX (customers may not want them yet).
Does not solve quota issues (still requires multiple basket modifications).

❌ B. Delay shipping calculation until checkout
Breaks the business requirement (customers expect upfront shipping estimates).

❌ C. Wrap each step in separate transactions
Still consumes quota (each add/remove counts against spi.basket limits).
Less efficient than a single rolled-back transaction (Option D).

Best Practice & Reference:
Salesforce B2C Commerce quotas limit spi.basket operations per request.
Transactions with rollback are the standard solution for temporary basket changes.

Example:
var transaction = require('dw/system/Transaction');
transaction.begin();
// Add item, calculate shipping
transaction.rollback(); // Restore original basket

Explanation:

A. 15,000 visits/hr, 300,000 page views/hr, 3,750 orders/hr

Visits → 15,000 / 1,000 = 15× (WAY too high)
Page views → 300,000 / 20,000 = 15×
Orders → 3,750 / 250 = 15×

Not correct.
✅ Eliminate.

B. 150,000 visits/hr, 3,000,000 page views/hr, 37,500 orders/hr

Visits → 150,000 / 1,000 = 150×
Page views → 3,000,000 / 20,000 = 150×
Orders → 37,500 / 250 = 150×

Outrageously too high.
✅ Eliminate.

C. 1,500 visits/hr, 30,000 page views/hr, 375 orders/hr

Visits → 1,500 / 1,000 = 1.5×
Page views → 30,000 / 20,000 = 1.5×
Orders → 375 / 250 = 1.5×

Too low. Not the required 4× growth.
✅ Eliminate.

D. 3,000 visits/hr, 60,000 page views/hr, 750 orders/hr

Visits → 3,000 / 1,000 = 3×
Page views → 60,000 / 20,000 = 3×
Orders → 750 / 250 = 3×

D represents only 3× growth.
But we need 4×.
So even D is not fully correct.
✅ Eliminate if we’re strict.

Conclusion

None of the given options matches the correctly calculated 4× load test targets:

✅ 4,000 visits/hr
✅ 80,000 page views/hr
✅ 1,000 orders/hr

Therefore, my previous answer stands:
The correct answer mathematically is none of the above.
On the exam, if forced to choose, you’d pick the closest — which is D — but it still underestimates the true 300% growth target.

So yes — I’m sure. The proper targets are:

✅ 4,000 visits/hr
✅ 80,000 page views/hr
✅ 1,000 orders/hr

None of the listed answers matches those exactly.

Explanation:

Why Option C?

✅ Prevents System Instability

OMS web service calls can fail or hang, leading to thread pool exhaustion if not properly managed.
A circuit breaker (e.g., dw.system.HookMgr) stops cascading failures by:
Blocking requests after a failure threshold.
Timing out slow calls.

✅ Matches the Scenario

The job processes yesterday’s orders in bulk—unreliable OMS responses could stall the job indefinitely.

Why Not Other Options?

❌ A. Post-processing search results
While inefficient, post-filtering isn’t the critical issue here (thread safety is).

❌ B. Transaction size
The snippet doesn’t show large transactions (but even if present, thread exhaustion is the bigger risk).

❌ D. Standard order import
Custom code is necessary to fetch OMS tracking numbers (no native "import" for this).

Best Practice & Reference:
Circuit Breaker Pattern: Essential for external service calls in B2C Commerce.

Example:
var CircuitBreaker = require('dw/system/CircuitBreaker');
var breaker = new CircuitBreaker('OMS_Tracking_Service');
breaker.execute(function() { /* Call OMS */ });

Timeout: Set via dw.system.Site preferences.

Explanation:

Option C: Content Slots & Assets

✅ Fulfills Requirements:

Static image content with text: Content slots allow flexible placement of images, text, and rich media.
Realizable (Responsive): Assets adapt to different screen sizes.
Carousel & Dynamic Categories: Slots can be populated with product carousels or seasonal category recommendations via Business Manager rules.

Option D: Page Designer with Dynamic Layout

✅ Fulfills Requirements:

Drag-and-drop editor simplifies placement of banners, carousels, and recommended categories.
Responsive by default: Page Designer layouts auto-adapt to devices.
Time-based rules: Dynamic layouts can swap content seasonally (e.g., winter vs. summer categories).

Why Not A & B?

❌ A. Content Management Service (CMS):
Overkill for a homepage (typically used for blogs/marketing pages).
Doesn’t natively support product carousels or dynamic category rules.

❌ B. Locales in Business Manager:
Manages language/region settings, not page content or layouts.

Best Practices:
Content Slots: Use for reusable, rule-driven content (e.g., "Summer Sale Banner").
Page Designer: Ideal for structural page changes (e.g., moving the carousel position).

Explanation:

✅ Why these options are correct?

C. Enable the Circuit Breaker.

✅ Correct.
B2C Commerce Service Framework has a circuit breaker feature.

When enabled:
If the service repeatedly fails or times out:
The circuit breaker “opens.”
Subsequent calls fail fast without waiting for timeouts.
This protects page load times from getting delayed waiting for a consistently failing service.
Ideal for load tests or production under high load.
✅ Correct choice.

E. Load the data asynchronously after the page is loaded.

✅ Correct.
Right now the third-party call is happening server-side, increasing page load time.

Moving it to the frontend as client-side JavaScript allows:
Faster initial page rendering.
Non-blocking loading of third-party data.
Even if the service is slow, the main page renders quickly, improving perceived performance for users.
✅ Correct choice.

❌ Why these options are incorrect?

A. Ask the third party to improve the reliability of the service.

While this is a good long-term action:
It’s outside the developer’s direct control.
Doesn’t solve the immediate problem of slow page loads during load testing.
Not a technical mitigation for B2C Commerce.
✅ Eliminate.

B. Decrease the service timeout.

Decreasing the timeout might:
Make timeouts happen faster.
Reduce wait time per request.

But:
It doesn’t completely protect the page from repeated failures.
A shorter timeout still causes a delay on every call until it fails.
Not as effective as a circuit breaker or a sync loading.
✅ Eliminate as the best solution.

D. Remove the service.

Removing the service entirely might not be feasible.
The business likely needs this data for analytics, personalization, or recommendations.
Not an architectural mitigation but an extreme measure.
✅ Eliminate.

Explanation:

The client wants a Page Designer-specific cache period, which SFRA’s base cache.js does not provide. The best practice is to extend, not copy, the base modules.

Why C is correct:

Extend the base Page.js controller instead of replacing it. Use server.prepend to add the custom cache middleware to the Page-Show route without duplicating code.

Example:

'use strict';
var server = require('server');
server.extend(module.superModule);

var cache = require('*/cartridge/scripts/middleware/cache');

server.prepend(
'Show',
cache.cachePageDesigner
);

module.exports = server.exports();

Why D is correct:

Instead of copying the entire cache.js file, extend it and add a new function for Page Designer caching. This approach is safer for upgrades and avoids duplication.

Example:

var base = require('app_storefront_base/cartridge/scripts/middleware/cache');

module.exports = {
...base,
cachePageDesigner: base.custom({
mode: 'server',
expires: 300
})
};


Why A and B are incorrect:

Copying entire controllers or scripts increases technical debt and maintenance costs. It’s better to extend existing modules to stay compatible with future SFRA upgrades.

Explanation:

A. Take the backup of the Order as XML and delete the Order…
Deleting the entire order just to fix note count is too destructive. Orders are legal, accounting, and customer data — removing them breaks record-keeping and reporting. This is not a valid solution.
✅ Eliminate

B. Using BM site import/export, soften the warn to make sure that neither order notes are lost and custom object is processed.
You cannot “soften” quota errors via Business Manager. A QuotaLimitExceededException is a hard platform limit — not just a warning you can silence in settings or an import/export tweak.
✅ Eliminate

C. Take the backup of the custom object and delete the custom object to ensure on the next job run the custom objects are getting processed.
This would delete the custom object before it can be retried, but that’s not helpful because it loses the meaningful order notes data that the OMS wanted to save. The data would be gone and never written to the order.
✅ Eliminate

D. Engage B2C Commerce Support Team to soften the quota limit for ‘object.OrderPO.relation.notes’.
This is valid. Quotas are sometimes adjustable via Salesforce Support. While some quotas are hard-coded, many object relation quotas can be raised if justified. It’s definitely one avenue an Architect should consider if the business has a legitimate case for storing >1000 notes.
✅ Correct

E. Take the backup of the Order as XML and delete the notes from Order to ensure on the next job run the custom objects are getting processed.
This is practical. Export the order for safekeeping, then remove older or unneeded notes to bring the total below the limit. This frees up quota for new notes to be written, allowing the custom objects to be processed. Data can be re-imported if needed.
✅ Correct