Salesforce CPQ-301 Exam Practice Test Instant Access

Question 1

The admin at Universal Containers wants to add some Maintenance and some Support products to the parent bundle. Maintenance and Support products should display in separate sections during configuration, with the Support products displaying above the Maintenance products. How should the admin set up the bundle to meet both requirements?

ACreate two Product Features: Maintenance and Support. The Maintenance Feature will always display first, due to alphabetical ordering.

BCreate two Product Features: Maintenance and Support. The Support Feature should have a lower value in the Number field.

CCreate two Product Options: Maintenance and Support. The Support Option should have a lower value in the Number field.

DCreate two Product Options: Maintenance and Support. The Maintenance Option will always display first, due to alphabetical ordering.

Answer : B

To display Maintenance and Support products in separate sections, the admin must create Product Features, as features define sections in the CPQ configurator. To control the order (Support above Maintenance), the 'Number' field on the Product Feature determines the sequence, with lower values appearing first. Option B correctly specifies two features (Maintenance and Support) and assigns a lower Number to the Support Feature, ensuring it displays above Maintenance. Option A relies on alphabetical ordering, which doesn't guarantee Support above Maintenance (e.g., 'M' precedes 'S'). Options C and D use Product Options, which don't create sections---only features do---and thus fail the separate-sections requirement. Salesforce CPQ documentation confirms feature ordering via the Number field.

Question 2

An admin has created a text field Configuration Attribute for Bundle

AThe admin wants the attribute to start with a dynamic value the moment the configuration page loads. Which steps should the admin take to meet this requirement?
A. Create a Flow to update the Product Option field that is used for the Configuration Attribute value. Set the process to trigger upon new record creation.
B. Create a Price Rule to target the Product Option field that is used for Configuration Attribute to give it a value. Ensure the end user selects Apply Rules in the Configurator.
C. Create a formula text field on the Quote, constructing the formula to return the desired default value. Update the Configuration Attribute Default Field to identify the Quote formula field.
D. Create a text field on the Quote Line object with the same API name as the Configuration Attribute field. Create a Price Rule to target the Quote Line field to give it a value.
Explanation:

To set a dynamic default value for a Configuration Attribute when the configuration page loads, automation must populate the associated Product Option field automatically. Option A uses a Flow to update the Product Option field tied to the Configuration Attribute, triggered upon record creation (e.g., when the Quote Line is initiated), ensuring the value is set dynamically at page load. Option B (Price Rule) requires manual user action ('Apply Rules'), which doesn't meet the 'moment the page loads' requirement. Option C (Quote formula field) isn't directly supported as a default source for Configuration Attributes without additional customization. Option D (Quote Line field with Price Rule) lacks real-time dynamism and alignment with page load timing. Salesforce CPQ documentation highlights Flows as a robust solution for dynamic defaults.
Reference: Salesforce CPQ Documentation - 'Configuration Attributes' and 'Using Flows in CPQ'.

Answer : A

Question 3

At Universal Containers, the Fulfillment team requires that Order Item dates reflect when orders are created, rather than Quote Line start dates, because there can be gaps between anticipated versus actual start dates. At the same time, the Account Management team wants to ensure that all items from one order appear on one contract. What are two ways the CPQ specialist can meet these requirements? (Choose 2 answers)

ASet Contracting Method on the Order to Single Contract.

BSet package Default Order Start Date to Today.

CSet Order Product Date to Today when the record is created using Process Builder.

DSet Quote Contracting Method to By Subscription End Date.

Answer : A, C

For the Fulfillment team's requirement, Order Item dates need to reflect the order creation date rather than Quote Line start dates. Option C achieves this by using Process Builder to set the Order Product Date to 'Today' upon record creation, overriding any inherited Quote Line dates. For the Account Management team's requirement, all items from one order must appear on a single contract. Option A accomplishes this by setting the Contracting Method on the Order to 'Single Contract,' ensuring all order products are grouped under one contract regardless of subscription terms. Option B (Default Order Start Date) is a package-level setting that doesn't directly apply to individual order items. Option D (Quote Contracting Method) affects quote-to-contract mapping but doesn't ensure order-based consolidation. Salesforce CPQ documentation supports these configurations for date and contract control.

Question 4

An admin wants to set up a bundle product so a user can view all available options and selected options by scrolling in a single page. Which updates should the admin make to meet this requirement?

AUpdate Option Layout on the parent Product record to Wizard.

BCreate Features related to the parent Product and assign all Options to one of the created Features.

CCreate Features related to the parent Product and assign each Feature the Option Selection Method of Dynamic.

DUpdate Option Layout on the parent Product record to Sections.

Answer : D

In Salesforce CPQ, the Option Layout field on the Product record determines how bundle options are presented in the configurator. To allow users to view all available and selected options by scrolling on a single page, the 'Sections' layout is ideal. This layout organizes options into collapsible sections based on Product Features, keeping everything visible on one page without requiring navigation steps like a wizard. Option A (Wizard) presents options step-by-step across multiple pages, which doesn't meet the single-page requirement. Option B (assigning all options to one feature) limits organization and doesn't address the layout requirement. Option C (Dynamic selection method) controls runtime behavior of options but doesn't influence the single-page scrolling display. Salesforce CPQ documentation confirms that the 'Sections' layout supports a scrollable, single-page view.

Question 5

What is the correct order of data import to load Products and Product bundles in CPQ?

AProduct, Product Features, Product Options, Option Constraints, Configuration Attributes

BProduct, Product Action, Product Rules, Error Conditions, Configuration Rules

CProduct Option, Product Feature, Product, Option Constraints, Configuration Attributes

DProduct Features, Product, Product Options, Configuration Attributes, Option Constraints

Answer : A

In Salesforce CPQ, importing data for products and bundles requires a specific order to ensure referential integrity, as certain objects depend on others being present. The correct sequence starts with the Product (the parent record), followed by Product Features (defining sections or categories within the bundle), Product Options (specific selectable items under features), Option Constraints (rules governing option selections), and finally Configuration Attributes (additional settings for dynamic configuration). Option A reflects this hierarchical dependency accurately. Option B includes unrelated objects like Product Action and Error Conditions, which pertain to rules rather than bundle structure. Option C starts with Product Option before Product, which violates dependency rules since options require a parent product. Option D begins with Product Features before Product, which is incorrect as features need a product to associate with. Salesforce CPQ documentation emphasizes this order for successful data imports.

Question 6

When amending a contract, users have reported that the net pricing of some products is incorrect. The admin has done a preliminary investigation and found that the issue only happens on existing products when the quantity is adjusted. What is the likely cause?

AThe Revised Quantity has been set on the Subscription record.

BA Price Rule is firing On Calculate and changing the Effective Quantity.

CA Price Rule is firing Before Calculate and changing the Regular Unit Price.

DThe products have a Discount Schedule and Cross Order is unselected.

Answer : A

When amending a contract in Salesforce CPQ, the net pricing of products can sometimes appear incorrect, especially when quantities are adjusted on existing subscriptions. The 'Revised Quantity' field on the Subscription record is used during amendments to reflect the updated quantity of a subscription product after the amendment. If this field is set incorrectly or unexpectedly (e.g., manually or via automation), it can override the expected quantity and cause discrepancies in pricing calculations, especially for existing products. This aligns with the scenario where the issue only occurs when quantities are adjusted on existing products. Option B (Price Rule firing On Calculate) could affect pricing but typically wouldn't target only existing products or cause quantity-specific issues unless explicitly designed to do so. Option C (Price Rule firing Before Calculate) might alter pricing but wouldn't directly tie to quantity adjustments on amendments. Option D (Discount Schedule with Cross Order unselected) affects pricing tiers but isn't directly related to amendment quantity adjustments. Per Salesforce CPQ documentation, the 'Revised Quantity' field is a key factor in amendment scenarios impacting pricing consistency.

Question 7

Universal Containers (UC) sells to partners in multiple regions. Each region has a unique price multiplier that should be applied to the pricebook price of the product.

A custom object has been created to maintain the regional multipliers for each region. Any discounts should be applied after the regional multiplier has been applied. An admin needs to create a Lookup Price Rule.

Which field should the admin configure the price action to update?

AThe special price

BThe partner price

CThe customer price

DThe list price

Answer : C

Scenario:

Apply a regional multiplier to the pricebook price and subsequently apply discounts.

Solution:

The Customer Price field stores the post-regional multiplier price, enabling further discounting.

Why Other Options Are Incorrect:

A: Special Price is used for manual overrides, not automated calculations.

B: Partner Price is unrelated to the customer's pricing structure.

D: List Price remains constant and does not reflect discounts or multipliers.

Salesforce CPQ Reference:

Price Rules and field updates are detailed in CPQ Pricing Logic Guidelines .

Salesforce CPQ-301 Configure and Administer a Salesforce CPQ Solution Exam Practice Test