Salesforce-B2C-Commerce-Cloud-Developer Practice Test Questions

Explanation:

To pass control from a JavaScript controller to an ISML template and load a product object into the pipeline dictionary under the key product, you need to:

Use the ISML.renderTemplate() method.
Pass the template name as the first argument.

Pass a key-value object as the second argument, where the key is the name used in the ISML template and the value is the actual data (in this case, myProduct).

So this line:
ISML.renderTemplate("helloworld.isml", { product: myProduct });
ensures that inside the ISML template, you can access the product data using ${pdict.product}.

❌ Why the other options are incorrect:

A: "myProduct": "product" passes a string "product" instead of the actual product object.

B: "product": myProduct is syntactically correct, but the quotes around the key are unnecessary in JavaScript unless the key has special characters.

D: "myProduct": product assumes product is defined, but the key myProduct doesn’t match what the ISML template expects.

Explanation:

When a critical web service is frequently unavailable, you need to address either:

Timeout issues (client-side)
Slow or unreliable responses (server-side)
Or network instability

Let’s break down the correct answers and why they’re effective:

✅ C. Increase the web service timeout
If the service is slow but eventually responds, the current timeout setting may be too short.

Increasing the timeout gives the service more time to respond, reducing the number of failed requests due to timeouts.

This is configured in Business Manager under Administration > Operations > Services.

✅ D. Update the external service to have a faster response time
If the external service is consistently slow, optimizing it to respond faster is ideal.

This is a long-term fix that improves both user experience and application reliability.

This could involve database optimizations, load balancing, or API improvements on the external server.

❌ Why the other options are incorrect:

A. Wrap code in try/catch block
This does not prevent service unavailability — it just handles the failure after it occurs.
Good for error handling, but not a solution for reducing failures.

B. Set throwOnError = true
This causes the service framework to throw an error on HTTP error responses (e.g., 500, 404).
Again, this is useful for error detection, but won’t reduce service unavailability — it just makes failures more visible.

Explanation:

Why This Approach?
Salesforce B2C Commerce uses locale-specific folders (en_US, fr_CA, etc.) to override form definitions (like address.xml) for different regions.

By placing the modified address.xml in an en_US subfolder, the U.S. site will automatically use this version while the Canadian site retains the original (in default or fr_CA).

Key Requirements Met:
State Dropdown: Replace Canadian provinces with U.S. state abbreviations in the copied address.xml.
Locale Setting: The en_US folder ensures the form aligns with the U.S. site’s locale.
Field Definition: Edit the copied XML to include the U.S. states list.

Why Other Options Fail:

A & C: Renaming files (e.g., adres_US.xml or address_en_US.xml) won’t work—the system expects files in locale folders, not renamed files in default.

B: A US folder (without en_US) doesn’t follow the locale-naming convention and won’t be auto-detected.

Explanation:

Problem Identification: The current configuration only allows GET requests ("methods": ["get"]), but adding products to a basket requires POST (or PATCH).

Without POST in the methods array, the API will reject write operations.

Why This Fix Works:

Adding "post" to the methods array enables the API to accept requests that modify the basket (e.g., adding items).

Example corrected configuration:
{
"resource_id": "/baskets/**",
"methods": ["get", "post"], // Now supports both read and write
"read_attributes": "(**)",
"write_attributes": "(**)"
}

Why Other Options Are Incorrect:

A: Changing resource_id to "/baskets/*/items" restricts the path but doesn’t solve the missing POST method issue.

B: "(+items)" is invalid syntax for write_attributes (use "(**)" for wildcard permissions).

C: "(items)" only grants read access to the items field but doesn’t enable writes.

Explanation:

The code currently loops through all search results and filters products based on the custom attribute isOnSaleFlag. This is known as post-processing, and it’s inefficient — especially when the product catalog is large.

To improve performance, the developer should move the filtering logic into the search query itself by using isOnSaleFlag as a search refinement. This way, only matching products are returned from the search engine, reducing memory usage and processing time.

This change:
Reduces the number of products iterated over.
Leverages the search index for optimized filtering.
Improves page load time and scalability.

❌ Why the other options fall short:

A. Use a system attribute instead of isOnSaleFlag: Not helpful unless a system attribute already exists for this purpose. The issue is filtering logic, not attribute type.

C. Break into separate loops: Doesn’t reduce the number of iterations — just spreads them out.

D. Use a Collection instead of Iterator: Might simplify syntax, but doesn’t address the root performance issue — filtering too late.

Explanation:

In Salesforce B2C Commerce (SFCC), resource bundles follow a fallback mechanism based on locale specificity:

When using:
${Resource.msg('weight.unit', 'account')}
...and visiting the storefront with the locale en_CA (English - Canada), the system will attempt to load the property in the following order:

🔍 Locale Resolution Order for en_CA:
account_en_CA.properties ✅ (not available)
account_en.properties ✅ (exists → used)
account.properties (default/fallback)

So in this case:
The system finds account_en.properties

It uses the entry:
weight.unit=stones

✅ Therefore, the output will be:
Your parcel weighs 10 stones.

❌ Why the other options are incorrect:

B. "pounds" → Would only occur if en_US locale was active (account_en_US.properties)

C. "undefined" → Would happen only if weight.unit was missing in all property files

D. "kilos" → From account.properties, used only if account_en.properties didn’t exist

Explanation:

A. Enable Debug Log Level

By default, debug logs may not be written to disk unless explicitly enabled.

Steps to Fix:
Business Manager > Administration > Operations > Log Settings > Custom Log Settings
→ Ensure "debug" is checked under "Log Levels to File".

C. Add the "login" Category to Log Filters
Log categories (e.g., "login") must be whitelisted in Custom Log Filters to appear in logs.

Steps to Fix:
Business Manager > Administration > Operations > Log Settings > Custom Log Filters
→ Add "login" to the list of categories.

Why Other Options Are Incorrect:

B (Archive old logs): While log rotation is important, it doesn’t affect whether new logs are written.
D (Global Preferences): Log levels are managed in Log Settings, not Global Preferences.

Explanation:

In Salesforce B2C Commerce SFRA (Storefront Reference Architecture), controller modules are structured using the server object from dw/system/Server. After defining routes and middleware, you need to export the controller so it can be used by other parts of the application — including Page Designer components.

The correct way to expose the controller logic is:
module.exports = server.exports();

This ensures that all defined routes and middleware are properly registered and accessible to the framework. Without this line, the controller won’t be recognized by the application, and Page Designer won’t be able to invoke it for rendering components.

❌ Why the other options don’t work:

A. Base.render = render;: This is not a valid export pattern and doesn’t expose the controller.

B. Module.exports.render = render;: Only exports a single function, not the full controller logic.

C. Module.exports = render;: Again, exports just one function — not suitable for SFRA controllers.

Explanation:

To properly process the new rewards pass ID form submission on the shopping cart page, the developer must complete two essential setup steps:

Add an node to the form definition XML This defines the form action and links it to the controller logic. The formid="addRewardPass" attribute ensures the form submission is routed correctly.

Update the Form.handleAction() call in Cart.js Add a new key addRewardPass to the object passed to Form.handleAction(), with a corresponding function to process the form data.

These steps ensure that the form submission is recognized and handled by the controller logic, allowing the rewards pass ID to be processed correctly.

❌ Why the other options don’t work:

B. node: Not valid in the Forms Framework — actions must be defined using .

C. addtl-form-action attribute in ISML: Used for multi-action forms, but not required or sufficient here.

D. No controller change: Without updating Form.handleAction(), the form submission won’t be processed at all.

Explanation:

In Salesforce B2C Commerce (SFCC), the Search Dictionaries Dashboard allows merchants and developers to refine how customer search terms are interpreted and matched.

To show only “car accessories” and exclude other accessories (like “technology accessories” or “household accessories”), the best strategy is to treat "car accessories" as a distinct phrase — not just a combination of two words.

✅ Why Option D is Correct:
A Common Phrase Dictionary entry allows you to define multi-word phrases that should be matched together, not split apart.

Setting the Search Mode to “Exact Match” ensures that only search results that match the full phrase "car accessories" will be shown.

This prevents unrelated matches where only “accessories” or “car” appear independently — which is what often causes household or technology accessories to show up.

❌ Why Other Options Are Incorrect:

A. Synonym Dictionary with car accessories, household, technology
➤ This would associate all these terms as equivalent, making the situation worse — you'd include the very terms you're trying to exclude.

B. Common Phrase Dictionary with car accessories, NOT household, NOT technology
➤ The Search Dictionaries Dashboard does not support boolean logic like NOT in phrases. So this entry would be invalid.

C. Synonym Dictionary with car accessories, household, technology using First Word
➤ Again, this would tell the system to treat all three phrases as interchangeable, which is the opposite of the goal.