Explanation:

Correct Option: B. 📋 As name/value pairs on the Attribute2 object
Product attributes in Salesforce CPQ are not stored on the Product2 object itself. Instead, they are managed through a separate, customizable object called Attribute (API name: Attribute__c). This object stores attributes as name/value pairs linked to a specific product, allowing for a flexible and dynamic structure without requiring schema changes for each new attribute.

Incorrect Option: A. 🗃️ in JSON format in a field on the Product2 object
Salesforce CPQ does not use a single JSON field on the Product2 object to store attributes. While JSON is a common method for storing structured data, CPQ's architecture is built around the separate Attribute object to facilitate complex relationships, validation, and rules within the product configuration process.

Incorrect Option: C. 📝 In individual fields on the product record
Creating individual fields on the Product2 object for every possible attribute is not scalable and is antithetical to CPQ's design. This approach would require constant schema modifications and lacks the flexibility needed for dynamic product configuration, which is why the dedicated Attribute object is used.

Incorrect Option: D. 💾 As a binary attachment
Attributes are not stored as binary file attachments. They are active, queryable data records that must be easily accessible for validation rules, pricing calculations, and configuration logic. Storing them as an attachment would make them unusable for these core CPQ processes.

Summary:
The Salesforce CPQ data model uses a separate, customizable object (Attribute__c) to store product attributes as name/value pairs. This design provides the flexibility to define an unlimited number of attributes for a product without modifying the core Product2 object's schema, enabling dynamic product configuration.

Explanation:

In Salesforce Industries CPQ (formerly Vlocity), the Line Item Configuration window in the Cart allows the user to modify details specific to each product in the cart. Among the configurable fields are:

✅ A. Service account
Refers to the account that will receive the service associated with this product.
Used in B2B and B2C flows to link the product to the correct customer account or sub-account.

✅ B. Billing account
Refers to the account responsible for billing the charges associated with this product.
Especially critical in multi-account or enterprise scenarios where the service and billing accounts are different.

These two fields are commonly editable in the line item configuration because:
They control who owns the product and who pays for it.
Users may need to select different accounts for different products in the same order.

Why not the others?

C. Prices
❌ Not directly editable in the line item configuration window.
Prices are controlled via:
Pricing logic
Promotions
Manual overrides (done outside the configuration window, e.g. via the Price Details window or specific override fields).

D. Applied promotion
❌ Promotions are typically added or removed at the cart level, not directly adjusted in the line item configuration window.
The window might show that a promotion has been applied, but it’s not where you modify the promotion itself.

✅ Example
In the Line Item Configuration window for “iPhone X,” you might see:
Service Account: [Dropdown or lookup]
Billing Account: [Dropdown or lookup]
...
Other attribute fields

But not:
Editable fields for prices
Editable applied promotions

Explanation:

The requirement is to set prices based on configurable service attributes such as Bandwidth (1 GB versus 10 GB) and Network type (Internet versus External). This scenario directly matches the definition of Attribute-Based Pricing, where pricing is determined by the selected product attributes.

D. Correct (Attribute-Based Pricing)
To meet this requirement, the developer would configure an Attribute Pricing Matrix, or a Range Attribute Matrix for the numeric Bandwidth attribute. Each row in the matrix defines pricing outputs for a specific combination of attribute values, for example:

Row 1: Bandwidth = 1 GB, Network = Internet → Monthly Price = $10, One-Time Price = $5
Row 2: Bandwidth = 10 GB, Network = External → Monthly Price = $20, One-Time Price = $0

This approach ensures the correct price is automatically applied based on the customer’s configuration choices.

Why the other options are incorrect

A. Usage Pricing
Usage Pricing is intended for consumption-based charging, such as a cost per unit of usage over time (for example, $0.10 per GB consumed). In this case, pricing is fixed based on selected service tiers rather than variable usage, so Usage Pricing is not appropriate.

B. Context rules for pricing adjustments
Context Rules are used to enforce product relationships such as Requires, Recommends, or Excludes. They do not define base pricing based on attribute selections. Pricing adjustments typically apply discounts or surcharges on top of an already determined base price.

C. Cost and Margin Pricing
Cost and Margin Pricing focuses on internal cost structures and profitability calculations. It is not a customer-facing pricing mechanism driven by configurable product attributes, making it unsuitable for this scenario.

Key Indicator
When the price of a product depends directly on configuration choices or attribute values, Attribute-Based Pricing is the standard and correct solution.

Reference
Salesforce Industries CPQ documentation on Attribute-Based Pricing describes this method as setting prices based on product characteristics or attributes, which aligns exactly with the scenario described.

Explanation:

In Salesforce Industries CPQ, context dimensions are variables used in rule conditions to evaluate eligibility, pricing, and visibility. When creating a context dimension, you must assign a data type that determines how values are interpreted and compared during rule evaluation. The supported data types include:

Text (A)

Used for freeform string values.
Replaces the deprecated String data type.
Ideal for values like account status, region, or product type.

DateTime (C)

Enables rules to evaluate temporal conditions (e.g., order date, activation date).
Useful for time-sensitive promotions or contract logic.

Boolean (D)

Supports true/false logic.
Commonly used for flags like “IsNewCustomer” or “HasContract.”

❌ Why the Other Options Are Incorrect

B. String
Deprecated in favor of Text. Using String may cause rule evaluation issues.

E. Integer and F. Numeric
Not valid data types for context dimensions. Numeric comparisons are handled through pricing variables or calculation matrices, not context dimensions.

Explanation:
Entity Filters are reusable, independent objects in Salesforce Industries CPQ and are not tied to a single Advanced Rule.

B is Correct (False):
An Entity Filter defines a set of conditions (e.g., Product Family = 'Mobile' AND Market = 'US'). This filter can be saved as a standalone, named filter and then referenced by multiple different Advanced Rules (such as Pricing Rules, Discount Rules, or actions within Promotion Rules). This reusability is a key design feature for maintainability and consistency.

Why A is Incorrect:
If Entity Filters were tied to a single rule, administrators would have to recreate the same logical conditions repeatedly across different rules, leading to redundancy, inconsistency, and a maintenance burden.

How it Works:
An administrator creates an Entity Filter (e.g., "US Mobile Phones").

They can then apply that same filter to:
- A Pricing Rule to adjust prices for US mobile phones.
- A Discount Rule to apply a special discount to US mobile phones.
- An Action within a Promotion Rule that adds a free accessory to US mobile phones.

Reference:
Salesforce Industries CPQ Documentation: "Use Entity Filters." The documentation explains that Entity Filters are "reusable filters" that you can "apply to multiple rules," clearly indicating they are standalone components not limited to a single rule.