Explanation:

When deciding between a content slot and a Page Designer (PD) component to make a section editable in Business Manager, the key factor is:

Page Designer Components Support Localization

Page Designer (PD) Components:

Can be localized for different languages (via locale-specific content assignments).

Example: A banner text can be edited in English, French, etc., directly in Business Manager.

Content Slots:

Typically not natively localizable. Content variations require manual handling (e.g., separate slots or custom logic).

Why Option A is Correct?
If the merchant needs to edit and translate content independently, PD components are the better choice.

Why Not Other Options?

B/D (Content Slots & Campaigns):
Both content slots and PD components can be tied to campaigns.
Localization is the differentiator, not campaign association.

C (PD Components & Campaigns):
Misleading. Campaigns work with both.

Additional Considerations:

Complexity: PD components require structured content types, while slots are simpler for static content.

Flexibility: PD components allow drag-and-drop layouts; slots are fixed to predefined regions.

Explanation:

Why Option A?
Locale-Specific Forms: B2C Commerce uses locale-based folder structures (e.g., forms/en_IN/) to override default forms for specific regions.

File Naming:
The file must be named profile.xml (standard form name for registration).
Placed in forms/en_IN/ to target Indian English (en_IN) users only.

Implementation Steps:
Create the file at:
cartridge/forms/en_IN/profile.xml

Add the new field (e.g., ) in this file.
The form will automatically override the default profile.xml only for en_IN locale.

Why Not Other Options?

B: Incorrect filename (profrfe_en_IN.xml is invalid; must be profile.xml).
C: Incorrect path (profde.in.xml is invalid; locale must use en_IN format).

Reference:
Salesforce B2C Commerce Form Localization

Explanation:

In Salesforce B2C Commerce, custom log files (e.g., customdebug, custominfo, customerror) have a daily size limit of 10 MB per application server. Once this limit is reached:

🔒 Logging is suspended until the next day (00:00 GMT)

This means no further log entries will be written to that file for the remainder of the day, ensuring system performance and storage stability.

🔍 Why Not the Other Options?

B. Suspended for two hours
There is no fixed 2-hour suspension — it's suspended until the next day.

C. File is deleted and recreated
Files are not deleted or recreated automatically — they are retained for 30 days.

D. Log file rolls over and is overwritten
SFCC does not roll over log files. It simply stops logging once the size limit is hit.

📘 Reference
Salesforce Developer Docs confirm:

“Logging is suspended until the next day (00:00 GMT) once the 10 MB limit has been reached.” 👉 Log Files | Monitor and Maintain – Salesforce Developers

Explanation:

To create a cache partition specifically for the home page (ensuring only the home page cache is cleared when edits are made), follow these steps in Business Manager:

Navigate to:
Administration > Sites > Manage Sites > [Your Site] > Cache

Configure the Partition:

Add a new cache partition (e.g., home_page).
Set the path to the home page (e.g., /home).
Assign a clear trigger (e.g., "Clear on content changes").

Why Option A?

Cache partitions are managed under Administration > Sites > Manage Sites > [Site] > Cache.
This allows granular control over which pages/URLs are grouped into partitions.

Why Not Other Options?

B/C: Incorrect paths. Cache partitions are not under Operations.

D: Site Preferences manage global cache settings, not partitions.

Explanation:

In Salesforce B2C Commerce, products are stored in the master catalog, and then assigned to categories in site-specific catalogs. If you want to export only the products that are assigned to categories in the site catalog, you need a way to filter the export based on category assignment.

🔍 Why B is correct:
B. Use the Catalog Export module to export the master catalog, with a category assignment search to export specific products.

The Catalog Export module allows filtering of product exports based on category assignments.

You can target only the products assigned to categories of the site catalog, even though they live in the master catalog.

This method ensures only relevant (assigned) products are exported.

❌ Why the other options are incorrect:

A. Use the Catalog Export module to export the site catalog
🔴 The site catalog only contains categories and their structure, not product data.

C. Use the Site Import & Export module to export both the site catalog and the master catalog in a single archive
🔴 This exports everything, not just the filtered subset. It’s not selective.

D. Use the Site Import & Export module to export the master catalog, filtered by site catalog categories
🔴 The Site Import & Export module doesn’t support filtering based on category assignment like the Catalog Export module does.