SALES-ADMN-202 Practice Questions

​Requirement:

Amend an active contract and adjust prices for subscriptions and assets based on new discounts.

​Solution:

Use the Amend Contract process.

Adjust prices for subscriptions or assets directly by modifying the Net Price or Price field.

Use the Refresh Prices button to apply changes to the amended contract.

​Why Other Options are Incorrect:

A: Cloning Quote Lines is unnecessary and inefficient for contract amendments.

B: Changing the contract status to Draft is not supported in standard CPQ.

D: Creating a new Price Book is not required for this use case.

​Salesforce CPQ Reference:

The Amendments Process is extensively documented in CPQ Subscription Management ​.

​Scenario:

Original subscription: $600 Net Unit Price × Quantity 10 × 24 months = $14,400.

Refund: Ten months into the contract, 14 months remain unused.

​Calculation:

Refund amount = ($600 × 10 × 14) ÷ 24 = -$3,500.

Amended subscription refund (Quantity = 0): 14 months refund prorated = -$2,500.

​Why Other Options Are Incorrect:

A, C, D: The refund calculations either overstate or understate the prorated refund based on the

subscription term and remaining months.

​Salesforce CPQ Reference:

Prorated refunds and subscription amendments are explained in CPQ Subscription Pricing

Documentation ​.

Requirement:

Separate products into different Line Item tables by Product Family when rendering a document.

Solution:

The Group Field functionality within a single Template Section can group Line Items by Product

Family dynamically, avoiding the need for multiple Template Sections.

Why Other Options Are Incorrect:

B & D: Creating multiple Template Sections for each Product Family introduces redundancy and is

less efficient.

C: LineSortField sorts products but does not create separate tables.

Salesforce CPQ Reference:

Group Field functionality is explained in the Quote Templates and Template Sections guidelines ​.

​Requirement Overview:

Assign generated Approval requests to the user's direct manager.

​Solution:

Salesforce CPQ's Advanced Approvals package includes the setting Next Automated Approver

Determined By, which allows Approvals to be routed automatically to the user's manager.

​Steps to Configure:

Navigate to the Approval Process.

Set Next Automated Approver Determined By to Manager.

Save and test the Approval process to ensure it correctly assigns to the manager.

​Requirement:

Set Product A’s price back to its List Price ($300) for a business unit account while ignoring parent

account contracted pricing.

​Solution Steps:

Option B: Create a new contracted price record for Product A at $300 for the business unit account.

Option D: Mark the Ignore Parent Contracted Prices checkbox as TRUE on the business unit account

to override inherited contracted pricing.

​Why Other Options Are Incorrect:

A: This would affect all contracted prices under the parent account, which is not the desired behavior.

C: Creating a new contracted price with Ignore Parent Contracted Prices set to TRUE is redundant;

the account-level setting (D) achieves this.

​Salesforce CPQ Reference:

Contracted Pricing functionality, including parent-child account handling, is outlined in CPQ Pricing

Guidelines ​.

​Requirement:

Deploy Price Rules with Lookup Queries that reference a new Rental Rates object.

​Best Practices for Deployment Order:

Step 1: Rental Rates: Deploy the object and data it

first to ensure lookup data is available.

Step 2: Price Rules: Deploy Price Rules to establish the logic governing pricing calculations.

Step 3: Price Conditions: These evaluate criteria for the rules to execute.

Step 4: Lookup Queries: Queries must reference both the object and conditions, so deploy them after

both.

Step 5: Price Actions: Set last to ensure that the actions triggered by the rules execute correctly.

​Why Other Options Are Incorrect:

A, B, D: Deploying Lookup Queries or Price Actions before Rental Rates or Price Rules may cause

execution errors due to missing references.

​Salesforce CPQ Reference:

Best practices for deploying CPQ Price Rules and Lookup Queries are detailed in Salesforce

documentation ​.

​Issue Context:

The custom field is not being updated by the Price Rule even after enabling triggers in the CPQ

Package Settings.

​Root Cause:

After creating new fields or updates, the Post Install Script must be executed to register custom fields

in the Calculator Referenced Fields list.

​Solution Steps:

Navigate to Setup > Installed Packages > Salesforce CPQ.

Locate the Post Install Scripts section and click Run.

Test the Price Rule again to verify that the custom field is updated correctly.

​Salesforce CPQ Documentation Reference:

Custom fields must be registered with the calculator for the Price Rule engine to interact with them

properly​​.

​Requirement:

A unique license number needs to be stored on the Asset record for each unit of a downloadable

product sold.

​Solution:

Setting the Asset Conversion field to One per Unit ensures that an individual Asset record is created

for each unit of the product. This allows each Asset to store a unique license number.

​Why Other Options Are Incorrect:

A & B: Null or custom values do not enforce one Asset per unit, making it impossible to assign unique

license numbers.

D: One per Quote Line creates only one Asset for the entire Quote Line, which is not suitable for unit-

level licensing.

​Salesforce CPQ Reference:

The behavior of Asset Conversion is detailed in CPQ Asset Configuration documentation ​.

​Requirement:

Ensure that quotes are recalculated with current information prior to approval without reopening the

Quote Line Editor.

​Solution:

Option A: Adding or modifying a field in the Calculating Fields Field Set automatically triggers

recalculation for quotes.

Option C: Including the Calculate button on the quote layout provides users with a manual option to

trigger recalculation before approval.

​Why Other Options Are Incorrect:

B and D: These require additional customization (e.g., creating a custom Lightning button or Flow)

and are not standard CPQ features.

​Salesforce CPQ Reference:

The Calculating Fields Field Set and Calculate Button functionalities are well-documented as standard

CPQ tools ​.

​Real-Time Calculation:

The Calculate Immediately field in CPQ ensures that pricing calculations occur automatically when

changes are made in the Quote Line Editor without requiring manual saving.

​Field Behavior:

Enabling this field configures CPQ to detect changes to the Partner Discount or other relevant fields

and trigger real-time recalculations.

​Salesforce CPQ Reference:

Configuration settings for real-time pricing calculations are documented in the Pricing and

Calculation Package Settings .