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

Block pricing in Salesforce CPQ is used when a fixed price applies to a quantity range, as in this tiered pricing scenario (e.g., $1,800 for 6-10 licenses). Option A sets the Pricing Method to "Block" on the Product, enabling this model. Option E involves creating Block Pricing records for each tier (e.g., 1-5 = $1,000), defining the fixed prices. Option B (Non Discountable = True) ensures no further discounts apply, meeting the requirement. Option C (Fixed Price) applies a single price regardless of quantity, not tiered pricing. Option D (Slab Discount Schedule) is for percentage-based discounts, not fixed block prices. Salesforce CPQ documentation validates this setup for block pricing.

ï‚· Requirement:

Ensure that custom field data from original Quote Lines flows into Renewal Quote Lines.

ï‚· Solution:

Use twin fields on the Asset and Subscription objects to store and transfer data. Twin fields are automatically mapped during renewal processes, ensuring data flows seamlessly.

ï‚· Why Other Options Are Incorrect:

A: A formula field cannot persist data on Renewal Quotes.

B: Automatic mapping does not apply to custom fields without twin fields.

C: A Price Rule is unnecessary when twin fields handle this data flow.

ï‚· Salesforce CPQ Reference:

Twin fields and their functionality are described in CPQ Subscription Management ​.

Understanding the Requirement:

Universal Containers wants a bundle with pre-selected Product Options.

Sales reps should mostly leave the default configuration as-is but need the flexibility to make changes when required.

Salesforce CPQ Feature Overview:

Configuration Type:

Determines whether sales reps can modify the configuration of a bundle product.

Setting it to Allowed permits the flexibility to configure without mandating it.

Configuration Event:

Defines when the bundle configurator is accessible.

Setting it to Edit prevents the configurator from opening automatically but allows sales reps to access it by clicking the "Reconfigure" link.

Configuration Steps:

Navigate to the Bundle Product record in Salesforce CPQ.

Set the Configuration Type field to Allowed. This ensures the configurator is optional and not enforced.

Set the Configuration Event field to Edit. This enables the configurator to be accessible only upon user action.

Key Behaviors:

With these settings, sales reps can use the default configuration but still make changes if needed by accessing the configurator manually.

The "Reconfigure" link in the quote line becomes available for editing.

Testing and Validation:

Add the bundle to a Quote.

Verify that the configurator does not open automatically.

Check that the "Reconfigure" link is accessible on the Quote Line for editing options.

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 ​.

ï‚· Scenario:

A subscription product does not appear in the Product Selection screen during search.

ï‚· Possible Causes:

A: The Active checkbox must be TRUE for the product to appear.

D: The product requires a Pricebook Entry in the corresponding Quote’s Pricebook.

E: If the Component checkbox is TRUE, the product is treated as a bundle component, not standalone, and will not appear in search results.

ï‚· Why Other Options Are Incorrect:

B: Cost records are unrelated to product visibility.

C: The Optional checkbox determines bundling behavior, not search visibility.

ï‚· Salesforce CPQ Reference:

Product visibility settings are detailed in CPQ Product Selection Configuration ​.

ï‚· Requirement Overview:

Universal Containers wants to restrict sales reps to accessing only region-specific Products while allowing managers to access all Products.

ï‚· Solution:

C. Price Books per Region: Create a separate Price Book for each region, associating only the relevant Products. Share each Price Book with the respective sales reps.

D. Product Rules: Use Product Rules to hide Products from sales reps outside their assigned regions.

ï‚· Steps to Configure:

Price Book Setup:

Navigate to Price Books.

Create a Price Book for each region and associate the specific Products.

Use Sharing Rules to share the Price Books with the appropriate sales reps.

Product Rule Setup:

Create a Product Rule with a Condition to hide Products based on the user’s region.

ï‚· Validation:

Test by logging in as a sales rep and verifying that they can only see Products for their assigned region.

ï‚· Requirement Overview:

A user must have the ability to approve any approval request, regardless of who the request is assigned to.

ï‚· Solution:

Granting the Modify All Data permission provides administrative privileges across all Salesforce objects, including the ability to approve any approval request in Advanced Approvals.

ï‚· Steps to Configure:

Navigate to the user’s Profile or Permission Set.

Add the Modify All Data permission.

Save and test the user’s ability to approve any request.

ï‚· Validation:

Confirm the user can approve approval requests without assignment restrictions.

ï‚· Requirement:

Ensure approval requests are routed to a substitute manager during the original manager's absence.

ï‚· Solution:

The Delegated Approver lookup field on the Approver record allows the admin to specify a temporary approver.

Setting the Delegation End field ensures the delegation automatically ends upon the original manager’s return.

ï‚· Why Other Options Are Incorrect:

A: Using the Next Approver field for temporary delegation is not the intended functionality.

B: Creating an Approval Rule with start and end dates is overly complex and unnecessary.

D: Replacing the original Approver record risks permanent changes and is not recommended for temporary delegation.

ï‚· Salesforce CPQ Reference:

Delegated Approval Settings are documented under Advanced Approvals Configuration Guidelines ​.