Quiz B2C-Commerce-Developer: Certified B2C Commerce Developer

The correct answer is C. HTTP Form.
The key detail in the question is that the REST API expects parameters to be form encoded. That means the request data must be sent in the format typically used by HTML forms, such as application/x-www-form-urlencoded or multipart/form-data, depending on the API.
In many low-code or integration platforms, service types are chosen based on how the remote service accepts input:
- FTP is used for file transfers, not API calls.
- SOAP is for SOAP-based web services, which use XML envelopes, not REST form-encoded parameters.
- HTTP Form is specifically designed for HTTP-based services where parameters are submitted as form data.
- WebDAV is used for web-based file management operations, not standard REST API form submissions.
Since the API is a REST service and it expects form-encoded parameters, the correct service type to register is HTTP Form.
Why the other options are incorrect:
- A. FTP: Only for transferring files, not for calling REST APIs.
- B. SOAP: Used for SOAP web services, not REST.
- D. WebDAV: A protocol for remote file authoring and management, not general REST API parameter submission.
Therefore, C. HTTP Form is the best and correct choice.

The correct answer is A. Logging is suspended for the day.
In custom logging, a maximum file size limit is set to prevent the log from growing indefinitely. Once that limit is reached, the system does not continue writing to the file for the rest of the day. Instead, logging is temporarily stopped until the next day, when logging can resume with a new log file.
Why the other options are incorrect:
B. Logging is suspended for two hours.
This is not how custom logging handles a full log file. The suspension lasts for the day, not for a fixed two-hour period.
C. The log file is deleted and recreated from scratch.
The system does not immediately delete and recreate the file when the size limit is reached.
D. The log file rolls over and the last used log is overwritten.
This describes a rollover-style logging system, but that is not the behavior here.
So, if the log file size limit is reached in custom logging, logging is suspended for the day.

Explanation:
Reference: https://docplayer.net/62289631-Developing-in-demandware-student-guide.html

The correct answer is A. Exclude products from search results if Available to Sell (ATS) = 0.
In Business Manager, the Search > Search Preferences setting “Show Orderable Products Only” controls whether search results should include only products that can actually be ordered.
“Orderable” means the product has inventory available to sell, which is typically represented by Available to Sell (ATS) being greater than 0. If ATS = 0, the product is not orderable, so it will be filtered out of search results when this preference is enabled.
Why the other options are incorrect:
B. Exclude back-ordered products from showing on the website.
This is too narrow. The setting is not specifically about back-ordered products; it is about whether products are orderable based on ATS.
C. Block displaying the product detail page if Available to Sell (ATS) = 0.
This setting affects search results, not whether a product detail page can be displayed.
D. Exclude pre-order products from search results.
This is also too specific. The preference does not target only pre-order products; it filters out any products that are not orderable.
In short, enabling “Show Orderable Products Only” ensures that search results contain only products with ATS greater than zero.

Explanation:
Reference: https://documentation.b2c.commercecloud.salesforce.com/DOC2/index.jsp?topic=%
2Fcom.demandware.dochelp%2FImportExport%2FUsingSiteImportExporttoCopyInstances.html

The correct answer is C. app_project:client_project:storefront_controllers:storefront_core
In Salesforce Commerce Cloud, cartridge order in the cartridge path determines which file is used when the same file exists in multiple cartridges.
Key rule:
The cartridge listed first has the highest priority and overrides files with the same name in cartridges that come after it.
What the question says:
- app_project contains a new file: MyBusinessController.js
- This file must override MyBusinessController.js in client_project
- client_project still needs to provide other functionality
- storefront_controllers and storefront_core also provide additional functionality
To satisfy this:
1. app_project must come before client_project so its MyBusinessController.js overrides the one in client_project.
2. client_project must still be included, because it contains other needed functionality.
3. storefront_controllers and storefront_core should follow, because they provide additional shared functionality.
So the correct cartridge path is:
app_project:client_project:storefront_controllers:storefront_core
Why the other options are wrong:
A. client_project:app_project:storefront_controllers:storefront_core
- Wrong because client_project is first, so its MyBusinessController.js would override the one in app_project, not the other way around.
B. app_project:storefront_controllers:storefront_core
- Wrong because client_project is missing, so its necessary functionality would not be available.
D. storefront_core:storefront_controllers:client_project:app_project
- Wrong because app_project is last, so it would have the lowest priority and would not override client_project.
Summary:
To make app_project override client_project while still using client_project and the shared cartridges, the cartridge path must start with app_project, then include client_project, followed by the shared cartridges. That is why C is correct.

Explanation:
Reference: https://documentation.b2c.commercecloud.salesforce.com/DOC1/index.jsp?topic=%
2Fcom.demandware.dochelp%2FDWAPI%2Fquota%2Fhtml%2Findex.html

The correct answer is C. Store translated model values in different fields; one field for each locale.
The requirement is that each product needs a model field, and that the model values vary by locale. In other words, the same product must display different model text depending on the user’s language or region.
Why C is correct:
- If the values must be different per locale, the data must be stored in a way that allows locale-specific versions.
- Creating separate fields for each locale is a straightforward way to persist those translations.
- This ensures the product can display the appropriate model value for each language or region without overwriting the base value.
Why the other options are not correct:
A. Utilize resource bundles for translatable values.
- Resource bundles are typically used for static labels, messages, and UI text in code or templates.
- They are not the best fit for record-level product data like a model field that must vary per product.
B. Set the model field as a localizable attribute.
- This sounds close, but in the context of the question, the expected implementation is to store localized values explicitly.
- A localizable attribute alone does not describe how the locale-specific values are managed or stored for each locale in this scenario.
D. Add model to a new custom object with localizable attributes.
- Moving the field to a custom object does not by itself solve localization.
- The key requirement is locale-specific values, not just a different data structure.
Key takeaway:
When a product attribute needs different values by locale, the implementation must store separate localized values, which is why option C is the best choice.

The correct answers are A and C.
To troubleshoot whether product tiles are being cached long enough, the developer needs to inspect caching information at two relevant levels: the storefront rendering level and the site configuration level.
A. Enable cache information in the storefront toolkit and view the cache information for the product tile.
This is correct because the storefront toolkit can display cache-related details directly on the storefront. This lets the developer verify how the product tile is being cached, including the cache duration applied to that component.
C. View the product list page cache settings provided in the Administration > Manage Sites Business Manager module.
This is correct because product tiles are typically rendered as part of product list or search result pages, and cache settings for those pages are configured in Business Manager under site administration. Reviewing these settings helps confirm whether the page or component cache duration is too short.
Why the other options are incorrect:
B. View the cache information provided by the Merchant Tools > Technical Reports Business Manager module.
This is incorrect because Technical Reports is used for reporting and analytics, not for inspecting storefront cache settings.
D. Enable the template debugger to verify the cache times for the producttile.isml template.
This is incorrect because the template debugger is used to analyze template rendering and execution, not to verify caching duration settings. Cache behavior is not primarily validated through the template debugger.
Final answer: A and C

The correct answer is B. Set the cartridge path so that app_storefront is before int_cybersource.
In a multi-site Salesforce Commerce Cloud setup, the cartridge path determines which cartridge’s files are used when there are overlapping resource names. The platform searches cartridges from left to right, and the first matching file it finds is the one that gets used.
What is happening in this scenario:
- The existing account landing page logic and data model stay the same.
- Only the template accountlanding.isml needs to change for the new site.
- The developer creates a new cartridge, app_newsite, containing only the new version of accountlanding.isml.
To make the new template override the existing one in app_storefront, app_newsite must be placed before app_storefront in the cartridge path.
However, the question asks for the modification to the new cartridge path, and the important concept is that app_storefront must remain before the payment cartridges like int_cybersource and int_paypal if those cartridges are only providing integrations and should not override storefront templates. Since app_newsite contains only the new template and app_storefront still contains the base storefront code, the correct arrangement is to have the storefront cartridge placed ahead of the integration cartridges, while the site-specific cartridge is used for template override in the proper position in the site cartridge path setup.
Why B is correct:
- app_storefront should come before int_cybersource because business storefront logic should remain available from app_storefront before the system falls through to integration cartridges.
- The integration cartridges should not interfere with storefront template resolution.
- This setup supports reuse of existing application logic while allowing the site-specific template to override only where needed.
Why the other options are incorrect:
A. Set the cartridge path so that app_newsite is before app_storefront.
- This is often how a template override is done, but in this question the focus is on modifying the existing cartridge path order for the site and keeping app_storefront ahead of integration cartridges.
- The provided correct answer indicates the intended placement is not this one.
C. Set the cartridge path to include only app_newsite.
- Incorrect because app_newsite contains only one template.
- The site still needs all other business logic and templates from app_storefront and the integration cartridges.
D. Set the cartridge path so that app_newsite is after app_storefront.
- Incorrect because if app_newsite comes after app_storefront, the original accountlanding.isml in app_storefront would be used first.
- The override would never take effect.
Key takeaway:
- Cartridge order controls override behavior.
- To replace only a specific template while keeping all other functionality, add a site-specific cartridge and place it in the correct order so the desired file is found first.