Salesforce-CPQ-Administrator Practice Test
Updated On 1-Jan-2026
212 Questions
A user created a Quote containing two Products. The Subscription Pricing field on Product A is blank. Product B has Subscription Pricing set to Percent of Total and both Products share the same Percent of Total Category. When the Contract is renewed, both Products are shown in the renewal Quote, but Product A has a Net Total of zero. Why does Product A have a Net Total of zero?
A. Renewal Model was set to Asset Based at the Account Level.
B. Product A is an Asset that the customer already owns.
C. Include Net-New Products in Maintenance must flagged in CPQ Package settings.
D. The Asset Conversion behavior on the Product must be set to Allow Renewals.
Explanation:
Key Issue:
Product A has Subscription Pricing = blank (non-subscription product), while Product B uses Percent of Total pricing.
Both appear in the renewal Quote, but Product A’s Net Total = 0.
Why Option A is Correct?
Asset-Based Renewal Model (at the Account Level) means:
Only assets tied to subscriptions (like Product B with Percent of Total pricing) are priced in renewals.
Non-subscription products (Product A) are included but not priced (Net Total = 0) because they lack subscription terms 58.
Why Other Options Are Incorrect?
B (Product A is an owned Asset): Irrelevant—ownership doesn’t zero out pricing unless Renewal Model is Asset-Based.
C (Include Net-New Products in Maintenance): This setting controls adding new products to renewals, not pricing behavior.
D (Asset Conversion Behavior): Governs whether a product can renew, not why its price is zero 5.
Reference:
Subscription Pricing Logic: Non-subscription products (blank Subscription Pricing) are excluded from pricing calculations in Asset-Based renewals.
Renewal Models: Asset-Based renewal focuses pricing only on subscription-linked assets
Key Takeaway:
The Renewal Model setting determines which products are actively priced in renewals. Here, Asset-Based renewal explains why Product A (non-subscription) shows $0.
Universal Containers (UC) defines a Warranty Period in a field on its Products and wants to ensure that this Warranty Period is correctly stored on the Asset record. A twin field has been created on the Asset record. UC contracts from the Order. When leveraging the twin field functionality to pass this Information to the Asset record, on which object should the admin create a twin field?
A. Product Option
B. Order Product
C. Opportunity Product
D. Quote Line
Explanation:
Key Requirement:
UC wants to pass the Warranty Period (a field on Product) to the Asset record when contracts are generated from an Order.
Twin fields are used to map data between objects during the Order-to-Asset process.
Why Option B (Order Product) is Correct?
Order Product (OrderItem) is the bridge object between:
Product (source of Warranty Period)
Asset (target where the value needs to be stored)
Twin fields must be created on Order Product to map:
Product.Warranty_Period__c → OrderItem.Warranty_Period__c → Asset.Warranty_Period__c
This ensures the field value flows correctly when the Order is activated and Assets are created.
Why Other Options Are Incorrect?
A (Product Option): Used for bundles/components, not for Order-to-Asset mapping.
C (Opportunity Product): Too early in the process; data isn’t passed to Assets from here.
D (Quote Line): Quote data does not directly impact Asset creation (unless synced to Order).
The admin at Universal Containers has received several reports that unwanted price changes have occurred on Quotes that have already been approved.
Which two configuration changes should the admin make to prevent this issue from happening?
(Choose 2 answers)
A. Remove any edit permissions on pricing ficlds in the ficld level security.
B. Assign a different layout to ensure users cannot access the Quote Line Editor, and hide the related list of Quote Lines.
C. Add a Validation Rule on an approved Quote and Quote Line to prevent any material changes.
D. Create a Product Rule, type Validation, that blocks users from editing Quote or Quote Line fields.
C. Add a Validation Rule on an approved Quote and Quote Line to prevent any material changes.
Explanation:
Issue:
Users are changing data on quotes after they’re approved. This is a big problem because it undermines the integrity of the approval process.
There are two excellent ways to address this in Salesforce CPQ:
✅ A. Remove any edit permissions on pricing fields in the field level security.
Once a quote is approved, price fields should no longer be editable. Removing edit access via Field-Level Security (FLS) ensures users can’t change fields like Sales Price, Net Price, Discount %, List Price. This locks down sensitive pricing data. However, this approach alone might not fully prevent changes in all contexts (e.g. API updates or edits via Quote Line Editor). So we also need:
✅ C. Add a Validation Rule on an approved Quote and Quote Line to prevent any material changes.
Validation Rules are the most robust way to block changes once a quote is approved. Example:
AND(ISPICKVAL(Status__c, "Approved"), ISCHANGED(SomeField__c))
This completely blocks edits to critical fields if the quote’s status is “Approved.” It’s the best-practice safeguard to enforce approval integrity.
Why not the other options?
B. Assign a different layout to ensure users cannot access the Quote Line Editor, and hide the related list of Quote Lines.
This is UI-level protection only. Users might still access fields through reports, APIs, or other screens.
D. Create a Product Rule, type Validation, that blocks users from editing Quote or Quote Line fields.
Product Rules only run in the Quote Line Editor. They do NOT enforce validation when users edit Quote or Quote Line records directly (e.g. in standard record pages). Validation Rules are more comprehensive. Hence, A + C are the correct answers.
When using Advanced Approvals, what must an admin do to grant a user the ability to approve any approval request regardless of who it is assigned to?
A. Grant the user the Modify all Data permission.
B. Assign the user the Advanced Approvals Admin permission set.
C. Add the user to the Delegated Approver field for each Approver.
D. Grant the user a permission set with CRED on the Approval object.
Explanation:
Requirement:
The admin wants a user to approve any request, even those assigned to others (e.g., universal approval rights).
Why Option C is Correct?
The Advanced Approvals Admin permission set grants full approval authority, allowing users to:
> Approve/reject any request, regardless of assignment.
> Bypass standard delegation rules.
This is the native CPQ way to enable cross-functional approvals.
Why Other Options Are Incorrect?
A (Modify All Data):
Grants broad edit access but does not specifically enable approval overrides.
C (Delegated Approver field):
Only works per-assignee (must be set for each approver), not globally.
D (CRED on Approval object):
Allows record edits but does not grant approval permissions.
Universal Containers only sells lid Products as part of a container Product. The admin wants to hide all lid Products from Product Selection. How should the admin set up lid Products?
A. Check the Component checkbox.
B. Set the Product Family value to Accessory.
C. Check the Hidden checkbox.
D. Include lid Products in the description of container Products.
Explanation:
Requirement:
UC sells lid Products only as part of a container Product (not standalone).
The admin wants to hide lids from the Add Products selection page to prevent direct sales.
Why Option C is Correct?
The "Hidden" checkbox on a Product record ensures:
The product does not appear in the Add Products selection screen.
It can still be added via Bundles, Product Rules, or as a component of another product.
This matches the need to sell lids only as part of containers.
Why Other Options Are Incorrect?
A (Component checkbox):
Marks a product as a component in a Bundle, but does not hide it from selection.
B (Product Family = Accessory):
Changing Product Family does not control visibility in the Add Products page.
D (Include in description):
A manual workaround, but does not enforce hiding the product.
| Salesforce-CPQ-Administrator Exam Questions - Home | Previous |
| Page 6 out of 43 Pages |