Industries-CPQ-Developer Practice Test Questions

Explanation:

In Vlocity Cart (Salesforce Industries CPQ Cart), product images are displayed directly next to each product in the Line Item pane of the cart.

This helps customers visually identify the products they have added, improving the user experience.

Analysis of options:

A. Incorrect. The Product List refers to the product selection page, not the cart.
B. Correct. Images appear in the cart’s Line Item pane along with product details.
C. Incorrect. While images need to be set up on the product record, they do not require special templates to display in the cart.
D. Incorrect. Images can appear in the Product Details modal, but in the cart, they specifically show in the Line Item pane.

Explanation:

A Guided Selling OmniScript is designed to walk users through a structured product selection and configuration process. Here’s how each correct option fits:

A. Instantiate the persistent cart This sets up the cart at the beginning of the guided selling flow, allowing selections to persist across steps and enabling final submission later.

B. Allow users to select products from the shared product catalog and add them to the cart This is the core function of guided selling — helping users browse, filter, and choose products from the catalog.

D. Allow users to review applicable promotions Promotions tied to selected products or customer context can be surfaced during the flow, helping users make informed decisions and increasing conversion.

❌ Why not the others?
C. Submit the order and return to the account This is typically handled in a separate OmniScript or post-cart flow, not within the guided selling process itself.

E. Use multiple OmniScripts to get products Guided Selling is usually implemented as a single OmniScript with branching logic and integration procedures — not multiple scripts fetching products independently.

Explanation:

When adding a new commercial product to the catalog in Salesforce Industries (Vlocity), to make it display in the Vlocity Cart’s product list, you must ensure:

A. It must have a price.
Products displayed in the cart need to have a price so that customers can see and buy them.
If a product has no price (and no price list entries), it won't appear in the cart.

C. Run the Product Hierarchy Maintenance job.
This job updates the product hierarchy cache used by the Vlocity Cart UI.
Without this, new or updated products will not show up properly in the cart product list.

F. The Active field must be checked.
Only active products appear in the cart.

The Active flag on the product (Catalog Product or Product2, depending on context) must be set to true.

❌ Why not the others?

B. Run Refresh Pricebook.
This is not necessary for Vlocity Cart. This is standard Salesforce CPQ functionality, not Vlocity CPQ.

D. The default Availability interface must be active.
Not required to simply display a product. Availability interfaces are used when there is availability logic (like checking inventory), but not strictly needed for listing.

E. The Orderable field must be checked.
This is only needed if you want to enforce ordering constraints. A product can still be displayed without it.

G. It must have an Object Type.
Object Type is used internally for distinguishing product types, but it is not a requirement for showing the product in the cart.

Explanation:

A Price List in Salesforce Industries (Vlocity) CPQ is a critical component for defining pricing structures. Here’s what you must know:

✅ Correct Answers:

A. Is always associated with a price book.

Price Lists cannot exist independently—they must be linked to a Salesforce Price Book.
Why? Price Books standardize which products are sellable, while Price Lists define how they’re priced (e.g., regional pricing, discounts).

C. Contains price list entries.

Price Lists store Price List Entries, which specify:
Base prices
Discount tiers
Overrides (e.g., customer-specific pricing).
Why? Without entries, the Price List is just an empty container.

D. Can be a parent price list or child price list.

Supports inheritance: Child Price Lists can override parent prices (e.g., for geographic or contract-specific pricing).
Why? Enables centralized pricing control with localized exceptions.

❌ Why Not the Others?

B. Is used to create pricing variables.
Incorrect. Pricing variables (e.g., formula-based discounts) are defined in Price Rules, not Price Lists.

E. Is the same as a price book.
Incorrect. Price Books (Salesforce standard) define which products are sellable. Price Lists (Vlocity CPQ) define how they’re priced.

Explanation:

Vlocity Rule Builder (now called Industries Rule Builder) is a powerful declarative tool used to define rules that control product eligibility, pricing adjustments, availability, validation, and other dynamic behaviors in Salesforce Industries (Vlocity) CPQ and EPC.

The Rule Builder allows you to visually create rules without coding by configuring:

Entity Filters — conditions that determine when or to whom a rule applies.
Rule Actions — what to do when the conditions are met (for example: show, hide, restrict, adjust, override).

✅ A. Advanced rules using entity filters and rule actions
Correct.
The Rule Builder is specifically designed to create advanced rules by combining entity filters (conditions) with rule actions (outcomes).
Examples include dynamically showing or hiding products, restricting options, or adjusting prices.

❌ Why not the others?

B. Context rules in Vlocity Product Console.
Incorrect.
While context rules exist in the Product Console, they are not directly built using the Rule Builder. Context rules are set up to control visibility of child products or attribute choices in bundles, but they use a different configuration UI.

C. Penalty rules for contracts and promotions.
Incorrect.
Penalty rules for contracts or early termination are configured differently (for example, through pricing procedures and specific contract settings), not with Rule Builder.

D. Entity filters and rule actions.
Incorrect (partially correct, but incomplete).
This option only lists the components (entity filters and actions) but does not mention advanced rules, which is the purpose of Rule Builder.

Explanation:

Salesforce Industries CPQ product models are often aligned with the TM Forum Shared Information/Data (SID) model, which is a standardized framework used across the communications industry to define and structure product, service, and resource entities.

Here’s why:

TMForumSID provides a common vocabulary and structure for modeling commercial and technical products, making it easier to integrate with other systems and maintain consistency across catalogs.

It supports specification-based modeling, where reusable templates (specs) define product characteristics, relationships, and behaviors.

This alignment ensures that product entities in the Enterprise Product Catalog (EPC) conform to industry best practices and are interoperable with other TM Forum-compliant systems.

❌ Why the Other Options Are Incorrect

A. ANSI 7200
Not relevant to product modeling in Salesforce Industries CPQ. ANSI standards are more focused on general telecommunications and electrical specifications.

C. TMForum eTOM
eTOM is a process framework, not a data model. It defines business processes, not product structures.

D. IEEE Telecommunications Template
IEEE standards are technical and protocol-focused, not used for catalog or product modeling in CPQ.

Explanation:

When implementing attribute-based pricing in the Default Pricing Plan, your custom pricing step must be placed before Sequence 10, which is the Initialize Pricing Context step. This ensures that attribute-based logic is evaluated early in the pricing flow, allowing subsequent steps (like loading price list entries and applying adjustments) to use the calculated values.

Here’s why this matters:

Attribute-based pricing often relies on custom matrices and calculation procedures that determine price based on product characteristics.

Placing the step before Sequence 10 ensures that the pricing context is influenced by these attribute values before any standard pricing logic kicks in.

If placed later, the attribute-based logic might be skipped or overridden by other pricing steps.

🔧 Implementation Notes

When configuring the step:

Use the Apex class CustomPricingPlanStepImpl
Method name is typically GetMatrixPrice
Set the sequence number to less than 10 (e.g., 5 or 9)
Activate the step and define parameters like ProcedureName and MatrixName

Explanation:

When working with Multi-Service Point Groups (MSPGs) in Salesforce Industries CPQ (Vlocity), a Master Quote is used to consolidate multiple service point quotes into a single commercial proposal.

Before a Master Quote can be submitted, the user must ensure:

✅ A. Apply to Group

Correct.
When working with a Multi-Service Point Group, the individual service point line items and configurations must be applied to the group.
This ensures that the configuration and selections are consolidated into the Master Quote for correct pricing and submission.

✅ D. Price and Validate

Correct.
After configuration and before submission, you must price and validate the quote to ensure:

The quote complies with business and pricing rules.
All errors or configuration conflicts are resolved.
Final prices are calculated and stored.

This step is required before any quote submission (including Master Quotes) to confirm it is commercially valid.

❌ Why not the others?

B. Configure line items
Incorrect.
You configure line items as part of the quote-building process, but this is not a final required step immediately before submission. The final "must do" steps are applying to group and price/validate.

C. Add to Cart
Incorrect.
"Add to Cart" is done when you initially select and configure products, but before creating or finalizing the Master Quote. It is not required immediately before quote submission.

Explanation:

When Felix creates a new product attribute in Salesforce Industries CPQ, it won’t automatically appear in the Object Type assignment list until the system updates its internal JSON cache. That’s where the EPCProductAttribJSONBatchJob comes in:

This batch job regenerates the JSON metadata used by the Product Designer and Object Type framework.
It ensures that newly created attributes are visible and assignable to object types.
Without running this job, the UI may not reflect recent changes—even if the attribute was saved correctly.

❌ Why the Other Options Are Incorrect

A. Set the Applicable Objects to Product2 Object
This is necessary for attribute behavior, but it doesn’t trigger the metadata refresh needed for visibility in the Object Type list.

B. Refresh the CPQPartition platform cache
This clears cached data for pricing and configuration, but not the attribute metadata used in Object Types.

C. Run the ProductAttributesBatchProcessor from the CMT Administration page
This job is used for syncing attribute definitions across partitions, not for updating the Object Type assignment list.

Explanation:

A pricing element defines how a product or service is priced. The two core components are:

✅ Correct Answers:

C. The charge (amount)

Why? The charge is the actual monetary value (e.g., $100 or 10% discount).
This is the primary attribute of any pricing element.

D. Whether the charge is a cost or price

Why? Pricing elements distinguish between:
Price: Amount charged to the customer (e.g., $100/month).
Cost: Internal expense (e.g., $70 to fulfill the service).

❌ Why Not the Others?

A. The price category
Incorrect. Categories (e.g., "Hardware" or "Subscription") group products but aren’t part of the pricing element definition.

B. The currency code
Incorrect. While currency is important for multi-currency orgs, it’s a system-level setting, not part of the pricing element itself.