Sales-Admn-202 Exam Dumps - Salesforce Certified CPQ Administrator

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.

ï‚· Requirement:

Allow users to generate output documents in Microsoft Word format.

ï‚· Solution:

The Allow Output Format Change checkbox in User Settings enables users to select alternative formats like Microsoft Word during document generation.

ï‚· Why Other Options Are Incorrect:

A: The checkbox is user-specific, not template-specific.

C: Creating a second template is unnecessary when users can dynamically change the format.

D: Template Sections do not control output formats.

ï‚· Salesforce CPQ Reference:

Configuring user settings for document generation is detailed in CPQ Quote Templates Documentation ​.

When a user performs a contract renewal and finds that the Price Book on the Renewal Opportunity or Quote is incorrect, the issue often arises due to the absence of a Price Book reference on the original Contract. To address this, the Renewal Pricebook ID field on the Contract must be populated. This field ensures the correct Price Book is carried over during the renewal process.

Step 1: Understand the Renewal Pricebook ID Field

Field Location: The SBQQ__RenewalPricebookId__c field is on the Contract object.

Purpose: It specifies which Price Book Salesforce CPQ should use for renewal quotes and opportunities created from the contract.

Without this field populated, Salesforce CPQ defaults to another Price Book, which can lead to inaccuracieste the Renewal Pricebook ID**

Access the Contract Record:

Navigate to the relevant Contract record in Salesforce.

Edit the Contract:

Populate the Renewal Pricebook ID field with the 18-digit Salesforce ID of the desired Price Book.

This ID corresponds to the Price Book you want Salesforce CPQ to apply during renewals.

Save the Changes:

Ensure the field is correctly updated and the changes are saved .

Step 3: **

Attempt the renewal process again by clicking Renew on the Contract.

Confirm that the Renewal Opportunity and associated Quote now reference the correct Price Book.

Step 4: Consider Automation for Future Accuracy

Automate Field Population:Use Process Builder or a Flow to automatically populate the Renewal Pricebook ID field based on the contract's associated Account or Opportunity. This reduces manual errors and ensures consistency.

Data Validation:Enforce validation rules to prevent contracts from being saved without a valid Renewal Pricebook ID .

By ensuring the Renewal Pricebook ID is coesolve the issue of incorrect Price Books during renewals and prevent similar occurrences in the future.

ï‚· Requirement:

Ensure the Warranty Period from the Product is correctly transferred to the Asset record.

ï‚· Solution:

Create a twin field on the Quote Line because:

The Quote Line stores product-specific information during quoting.

When the Quote is contracted, the twin field ensures the value is passed to the Order Product and then to the Asset record.

ï‚· Why Other Options Are Incorrect:

A: The Product Option is used within bundles and does not directly transfer to the Asset.

B: The Order Product receives data from the Quote Line, so the twin field must originate there.

C: The Opportunity Product is not involved in the CPQ twin field data flow.

ï‚· Salesforce CPQ Reference:

Twin fields and their data flow from Quote Line to Asset are detailed in CPQ Field Mapping Documentation ​.

ï‚· Requirement Overview:

Universal Containers wants to use split Orders to manage fulfillment by separating items based on their shipping schedules.

ï‚· Key Considerations:

Component-type Options: When splitting Orders, component-type Options are treated independently and can be split into different Orders.

Bundle Structure: Splitting Orders does not maintain the bundle structure, meaning the parent-child relationships of the bundle are not preserved in the split Orders.

ï‚· Steps to Configure:

Ensure that the Order by Quote Line Group field or a custom grouping field is used to facilitate splitting the Orders based on shipment schedules.

ï‚· Validation:

Test the split Order functionality by creating a Quote with a hardware bundle and ensuring that the bundle and components can be split appropriately.

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.

ï‚· Requirement:

Universal Containers wants to control whether the Additional Discount column appears on the Quote Template.

ï‚· Solution:

By creating a custom checkbox field (Show_Discount__c), administrators can dynamically control the visibility of the Additional Discount column.

This checkbox is referenced in the Conditional Print Field of the Quote Template Line Column settings for the Additional Discount column.

ï‚· Mechanism:

When the Show_Discount__c checkbox is TRUE, the column appears.

When FALSE, it does not display.

ï‚· Salesforce CPQ Reference:

Conditional Print Field functionality in Quote Templates allows for dynamic content visibility based on field values ​.

ï‚· Requirement Overview:

Product A must always be included in the bundle.

Product B should be included by default but can be removed by the user.

ï‚· Key Configurations:

Required = FALSE: This ensures that Product B is not mandatory and can be removed by the user.

Selected = TRUE: This includes Product B by default when the bundle is added to the Quote.

ï‚· Steps to Configure:

Navigate to the Product Option record for Product B.

Set Required to FALSE.

Set Selected to TRUE.

Save and test the behavior by adding the bundle to a Quote.

ï‚· Validation:

Product B should be pre-selected in the Quote Line Editor but can be deselected by the user.

This setup ensures flexibility for Product B while ensuring Product A remains mandatory​​.