Explanation:

The Product Console in Salesforce Industries CPQ is a centralized interface for managing all key entities involved in product catalog configuration. It allows administrators and developers to manage:

Products (D)
Create, edit, and organize commercial and technical products, including bundles and child items.

Product Attributes (B)
Define and assign attributes to products for customization, filtering, and pricing logic.

Picklists (A)
Create reusable value sets that can be linked to attributes or context dimensions.

Object Types (C)
Define reusable templates for product classes, including layout, fields, and attribute inheritance.

Together, these entities form the foundation of the Enterprise Product Catalog (EPC) and are all accessible and configurable via the Product Console.

Explanation:

In Salesforce Industries CPQ, the CPQPartition is a designated platform cache used to store product hierarchies, pricing data, rules, and other metadata to improve performance—especially in large catalogs or complex bundles.

The minimum recommended allocation for CPQPartition is 10 MB2.

This ensures that caching features like Refresh Platform Cache, Advanced Rules, and Product Hierarchy Maintenance work correctly.

While you can technically allocate less (even 1 MB per segment), 10 MB is the baseline to support full CPQ functionality.

❌ Why the Other Options Are Incorrect

B. 100 MB and C. 1GB
These are valid for larger orgs, but not the minimum required.

D. 0MB, since you can disable the CPQPartition
CPQPartition is required for caching to function. Disabling it would prevent key features from working properly.

Explanation:

Why Option C is Correct?
In Salesforce Industries CPQ (Vlocity CPQ), product attributes are used to define customizable properties of a product (e.g., color, size, material). Before creating an attribute, you must:

Create an Attribute Category → This acts as a container for related attributes.
Example: A category named "Display Options" could hold attributes like "Screen Size" and "Resolution".
Without a category, attributes cannot be logically grouped or assigned to products.

Why Other Options Are Incorrect?

A. Create the product → Attributes can be created before or after products exist. They are linked later via Attribute Assignments.
B. Create the object type → While object types (e.g., "Device") are used in Vlocity Data Model, they are not required for basic attribute creation.
D. Create the picklist → Picklists define attribute values (e.g., "Red/Blue/Green"), but the attribute itself must exist first.

Explanation:

In Salesforce Industries CPQ, once you create an entity filter, it becomes a reusable component that can be applied to any rule that requires it. This includes:

Pricing Rules
Compatibility Rules
Eligibility and Availability Rules
Advanced Rules
Entity filters are designed to:
Target specific line items or objects based on conditions
Be modular and shareable across multiple rule actions
Improve rule maintainability by centralizing logic

For example, if you create a filter to identify products with a status of "Active" and a minimum quantity of 1, you can reuse that filter in multiple rules—such as one that applies discounts and another that validates configuration.

Explanation:

A rule like "Product X requires Product Y" is an example of a Compatibility rule, not an eligibility rule.

Eligibility rules determine whether a product or promotion is available to a customer (for example, based on context like location, segment, or account status).

Compatibility rules define relationships between products, such as:

Product X requires Product Y.
Product X excludes Product Z.

In this scenario, the rule enforces that if you select Product X, you must also select Product Y — that’s classic compatibility logic.