Salesforce-CPQ-Administrator Practice Test Questions

A.   Set the Conditional Print Field on the Line Column record.

C.   Create a custom formula Indicating if the Payment Terms are Net 30.

Explanation:

Universal Containers wants to conditionally display the Monthly Price column on the Quote Document — but only when the Payment Terms = Net 30.

To do this in Salesforce CPQ, you must use the Conditional Print logic available in the Quote Template system.

✅ A. Set the Conditional Print Field on the Line Column record

The Line Column record defines how Quote Line data appears in the document.
To make a column show only under certain conditions, you set the Conditional Print Field on the Line Column.
This field points to a boolean field (e.g., Show_Monthly_Price__c), which controls whether the column appears.

✅ C. Create a custom formula indicating if Payment Terms are Net 30

This is the field that A references.
You create a custom formula field (e.g., on the Quote object) that returns TRUE if Payment Terms = 'Net 30'.

The formula might look like:
IF(Payment_Terms__c = "Net 30", TRUE, FALSE)
This field is then used in the Conditional Print Field on the Line Column.

❌ Why the other options are incorrect:

B. Include Monthly Price in the Quote Line Editor Field Set
This only affects the Quote Line Editor UI, not the Quote Document output.

D. Create an additional Line Items section without the Monthly Price field
Not necessary. Using Conditional Print is much more efficient and dynamic than duplicating sections.

A.   

{!quote.Additional_Text__c}

Explanation:

1. Field Location:
The custom field Additional_Text__c exists on the Quote object (SBQQ__Quote__c).

2. HTML Template Syntax Rules:
In Salesforce CPQ HTML Templates, the Quote object is referenced using the quote merge field prefix.

The correct syntax is always:
{!quote.Field_API_Name__c}

3. Why This Works:
{!quote.Additional_Text__c} directly accesses the field from the Quote record.
No relationship notation (__r or __c) is needed because the field is on the Quote itself.

Why Not Other Options?

B: Incorrect prefix (Iquote__r is invalid; quote is the correct merge field name).

C: Unnecessary relationship syntax (SBQQ__Quote__r is used for cross-object fields, not fields on the Quote itself).

D: .Additional_Text__c cannot be accessed via SBQQ__Quote__c (this is the record ID, not the object reference).

D.   On the Quote Term record, check the Locked checkbox.

Explanation:

In Salesforce CPQ, Quote Terms are used to insert standardized legal or financial text into the quote documents. To prevent non-admin users from modifying a specific Quote Term, the best practice is to use the Locked checkbox on the Quote Term record.

✅ When Locked = TRUE:
The Quote Term becomes read-only for non-admin users.
Only users with the Modify All Data permission (typically admins) can edit or delete the term.
This is the intended method for restricting edit access to Quote Terms.

❌ Why the other options are incorrect:

A. Read-Only checkbox:
No such standard checkbox exists on Quote Term records.

B. On the User Profile, make the object Read-Only:
Overly restrictive — this would prevent users from seeing or interacting with any Quote Terms, not just specific ones.

C. Make the Object Read-Only:
Same issue as B — applies broadly to the entire object, not specific records.

B.   100, -20, 40

Explanation:

Universal Containers is using Salesforce CPQ Subscription Products, and the scenario involves amendments to a 36-month Contract.
Let’s break this down chronologically.

🔢 Initial Quote and Contract:

The initial subscription is for:
100 licenses
36-month term
→ So the original subscription quantity = 100

🛠️ Amendment 1 (After Year 1):
The customer wants to reduce to 80 licenses starting in Year 2.
Salesforce CPQ tracks only the change when amending.
New Quote will have a negative delta of –20 (to drop from 100 to 80).
→ So the first amended subscription = –20

🛠️ Amendment 2 (After Year 2):
Customer increases license count from 80 to 120.
Again, CPQ tracks only the delta.
The change is from 80 → 120 = +40
→ So the second amended subscription = +40

D.   A twin field should be created on both the Asset and Subscription objects to bring back to Renewal Quote Lines.

Explanation:

In Salesforce CPQ, Renewal Quote Lines are generated from Subscriptions and Assets, not directly from the original Quote Lines. If you want custom field data from the original Quote Line to be carried into the Renewal Quote Line, the correct and supported method is:

🔄 Create twin custom fields on:

Quote Line
Subscription (or Asset, if applicable)
And again on Quote Line for renewal
These fields must have the same API name on each object. Salesforce CPQ automatically copies the data across the objects during contracting and renewal, as long as the fields are properly matched.

🔁 Data Flow Path:

Original Quote Line → Subscription (via the contracting process)
Subscription → Renewal Quote Line (during renewal quote generation)

❌ Why the other options are incorrect:

A. Custom formula field via SBQQ__Source__c
SBQQ__Source__c is a lookup to the originating Quote Line, but this only exists on Amendment Quotes, not Renewals.

B. Renewal Quote Line values are automatically mapped
Only standard fields are mapped automatically.
Custom fields require twin-field setup.

C. Price Rule to copy values
Overkill and less reliable than using twin fields.
Also not automatic — requires rule maintenance.

A.   Configuration Attributes.

Explanation:

Configuration Attributes in Salesforce CPQ allow you to capture user input during bundle configuration — such as dropdowns, picklists, or text fields — without creating a separate SKU for every possible combination.

In this scenario:
Universal Containers needs sales reps to specify:
Location (4 regions)
Color (10 options)
Size (4 options)
But without creating 160 different SKUs (4 × 10 × 4).

✅ Why Configuration Attributes is the correct tool:

They allow sales reps to choose values (like color, size, location) while configuring a product.
These values are stored on the Quote Line and can influence pricing or product rules.
No need to manage hundreds of SKUs.
They are ideal for product variants where the core product is the same, but options vary.

❌ Why the other options are incorrect:

B. Product Options
Used to add other products to a bundle — not for user input like color/size.

C. Product Features
Used to group Product Options, not to gather configuration input.

D. Option Constraints
Used to create logic between Product Options (e.g., "if this, then hide that"), not for data entry or selection fields.

C.   The Quote Line date

Explanation:

In Salesforce CPQ, when a Quote Line has a custom Start Date or End Date (i.e., different from the Quote’s start/end), the Quote Line dates take precedence when calculating the prorate multiplier for subscription products.

✅ CPQ uses:
Quote Line Start Date → Quote Line End Date
Instead of the quote-level start and end dates, if they are present.

This behavior ensures that subscription pricing is accurately prorated based on the specific service period for that line item.

🔁 Proration logic:
If the Quote Line has custom Start/End Dates, CPQ uses those for proration.
If not, it defaults to the Quote’s Start/End Dates.

❌ Why the other options are incorrect:

A. The earliest date
CPQ doesn’t choose based on “earliest” — it uses the Quote Line dates when specified.

B. The Quote date
The Quote’s date is only used when Quote Line dates are blank.

D. The latest date
Not applicable — CPQ doesn’t select dates based on which is latest.

B.   The Target Field maintains its original value and an error message appears in the Quote Line Editor.

Explanation:

When using Lookup Price Rules in Salesforce CPQ, if multiple lookup records match the criteria specified in the Lookup Queries, CPQ will:

Select the first record sorted alphabetically by the Name field (ascending A → Z), and apply that record’s field value to the Target Field on the Quote Line.

This behavior is default and cannot be controlled directly without additional custom logic or filters to ensure only one record matches.

❌ Why the other options are incorrect:

A. Second record sorted alphabetically
Incorrect — CPQ applies the first alphabetically, not the second.

B. Error message appears
CPQ does not throw an error in this scenario. It simply picks the first match.

C. Most recently created record
Creation order is not considered — only alphabetical order by Name is used.

B.   The renewal Quote start date will be the Contract end date plus one day.

Explanation:

When a Contract is activated in Salesforce CPQ, and Renewal Pricing Method is set to List, the behavior for renewal quote generation is as follows:

✅ Key facts:

Renewal Pricing Method = List:
Means CPQ will use current List Prices for subscription products on the renewal Quote.
No discounts or pricing from the original Quote are carried over.

Renewal Quote Start Date:
Will be set to the day after the Contract’s End Date.
This ensures the renewed subscription period picks up seamlessly where the last one ended.

❌ Why the other options are incorrect:

A. Additional discounts from the original Quote will automatically populate
❌ Not true when Renewal Pricing Method = List — it resets pricing.

C. Optional products from the original Quote will pull into the renewal
❌ Optional products are not carried over into renewals by default.
Only active subscription lines become part of the renewal.

D. All Quote Line items will be pulled through from the original Quote
❌ Incorrect. Only subscription products on the contracted Quote generate renewal lines.
Non-subscription products are excluded from renewal Quotes.

B.   Subscription Term unit: Month
Subscription Prorate Precision: Month

Explanation:

1. Business Requirement:
Sell products with monthly subscription terms.
Round up additional days to the nearest month for proration (e.g., 1.5 months → 2 months).

2. Solution:
Subscription Term Unit = Month:
Sets the base term to months.

Subscription Prorate Precision = Month:
Forces proration to whole months only, rounding up partial months.

3. Example:
If a subscription runs for 45 days (1.5 months):
Prorated Term: 2 months (rounded up).

Why Not Other Options?

❌ A: Prorate Precision: Day calculates exact daily rates (does not round up).
❌ C: Month + Daily allows partial-month proration (contradicts the rounding requirement).
❌ D: Term Unit: Day bases pricing on days, not months.

Key Settings:

Navigate to:
Setup → CPQ Settings → Subscription Terms

Configure:
Default Subscription Term Unit: Month
Subscription Prorate Precision: Month