Explanation:

A. A new customer export Job must be created to export customers.

🚫 Not necessarily.
The new site will use the existing CRM system.
Unless there’s a specific business rule to isolate customer data, customers across sites can often be exported through shared or existing jobs.
Usually, customer exports can be site-agnostic, or the existing job can handle multiple sites.
✅ Eliminate.

B. A new product Import Job must be created to manage products.

✅ Correct.
The new site’s ERP has its own product data.
Products from the new ERP need to be imported into B2C Commerce.
This requires a new import job, because:
The data source differs.
Mapping, data structure, and file format might differ from the current brand’s import process.
So a new product import job is needed.

C. A new inventory Import Job must be created to manage inventory.

✅ Correct.
The new brand has its own ERP → meaning its own inventory data source.
Inventory import jobs are tied to data feeds.
Since this ERP is separate, a new inventory import job must be created for this site.

D. A new order export job must be created to export orders.

🚫 Not required.
Orders will flow into the existing OMS.
It’s usually possible to reuse the same order export job across sites:
The job can export orders from multiple sites, as long as site-specific logic is handled in the job’s processing.
You might add configuration to the existing job, but you don’t necessarily need a brand-new export job just because there’s a new site.
✅ Eliminate.

Explanation:

Create a job and define three steps: one custom step to download the files from SFTP, and two standard steps to import the promotion and coupons.

Why?

Step 1: Custom SFTP Download
B2C Commerce does not natively support SFTP in standard job steps.
A custom script (ExecuteScriptModule) is required to securely fetch files from the SFTP location.

Steps 2 & 3: Standard Imports

Use built-in import modules for promotions and coupons (ImportPromotions, ImportCoupons).
No need for custom scripts here—standard steps are optimized for these tasks.

Why Not the Others?

A → Incorrect. Only one custom step (SFTP download) is needed; the rest should use standard imports.

B → Incorrect. Promotions/coupons should use standard import steps, not custom scripts.

D → Incorrect. Overuse of custom steps is inefficient when standard modules exist.

Key Best Practices:
✅ Minimize custom code (use standard imports where possible).
✅ SFTP requires a custom script (no OOTB support).

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:

✅ 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:

A. Four Service Configurations. Four Service Profiles, One Service Credential.

Service Configurations: ✅ required because log prefix differs.
Service Profiles: Technically not necessary to have four if the settings are identical. One profile would be enough.
Service Credential: ✅ only one needed.

→ Slightly redundant. Four service profiles is not minimal if all share the same timeout and settings. One profile suffices.
→ So A is not the minimal set of configuration. It works, but it’s not minimal.

B. Four Service Configurations. Four Service Profiles, Four Service Credentials.

Four credentials? ❌ No, question says all services share credentials.
→ Overkill.
✅ Incorrect.

C. Four Service Configurations. One Service Profile, One Service Credential.

Service Configurations: ✅ required because log prefix differs.
Service Profile: ✅ one shared, since timeouts and settings are identical.
Service Credential: ✅ one shared.

→ This is correct. It’s the minimal setup to:
Achieve different log prefixes.
Reuse settings and credentials.
✅ THIS IS THE BEST ANSWER.

D. One Service Configuration, Four Service Profiles, One Service Credential.

Only one Service Configuration means only one log prefix.
→ That fails the requirement for separate log files.
✅ Incorrect.

✅ Correct Answer:
✅ C. Four Service Configurations. One Service Profile, One Service Credential.
That’s the minimal configuration. You only need one profile if the timeout and settings are identical. You do, however, need four service configurations because each has a separate log prefix.