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

ï‚· Requirement Overview:

Control the visibility of fields in the Quote Line Editor.

ï‚· Solution:

The Edit Lines Field Set Name special field on the Quote object references the field set used to control which Quote Line fields are visible in the editor.

ï‚· Steps to Configure:

Navigate to the Field Set on the Quote Line object.

Add or remove fields from the field set referenced in the Edit Lines Field Set Name field.

ï‚· Validation:

Test the Quote Line Editor to ensure only the configured fields are visible.

To manage a subset of eco-friendly products for opportunities flagged as eco-friendly while allowing flexibility to include all bundles, follow these steps:

Step 1: Create a Filter Product Rule

Filter Product Rules help define dynamic filtering of products displayed during the quoting process.

Navigate to Product Rules

Go to Salesforce Setup → Product Rules and click New.

Set the Type to Filter and define a clear Name such as "Eco-Friendly Product Filter."

Configure the Filter Logic

Define the conditions to identify eco-friendly and bundle products.

Use the Conditions related list to target the relevant product fields (e.g., a custom checkbox for eco-friendly products and a type field for bundles).

Example condition:

Field = Eco-Friendly Checkbox

Operator = Equals

Value = True

Step 2: Set up the Product Action

Product Actions define what the rule does when triggered.

Add a Product Action

In the Product Rule, go to the Product Actions related list and click New.

Set the Type to Optional Filter. This allows the system to apply the filter by default but enables users to remove the filter and see all bundles.

Link to Add Products Button

Make sure this action links to the Add Products custom action.

Step 3: Ensure Opportunity Integration

The Opportunity flagged as eco-friendly must drive this behavior.

Custom Field Dependency

Ensure the Opportunity has a field (e.g., Eco-Friendly Checkbox) that can be referenced in the Filter Product Rule or through a related custom formula on the Quote.

Dynamic Behavior

When the Opportunity is flagged, the filter is applied dynamically, displaying only eco-friendly and bundle products in the Add Products dialog.

Step 4: Test and Validate

Test the behavior by flagging different Opportunities as eco-friendly and verifying the Add Products functionality:

Eco-Friendly flag → Default to eco-friendly products and bundles.

No flag → All products, including non-eco-friendly bundles, are shown.

Additional Considerations:

Search Filter IntegrationThe Search Filter can complement this approach by providing additional options for users to refine their selections further​​.

User TrainingTrain sales reps on how to toggle the filter manually if needed.

This setup allows Universal Containers to meet its business objectives while maintaining flexibility for its sales team​.

ï‚· Issue:

Prices are hidden on the Configure Products page due to restricted field visibility.

ï‚· Solution:

Adjust the Field-Level Security settings for the Unit Price field on the Product Option object to ensure visibility.

ï‚· Why Other Options Are Incorrect:

B: The Option Configuration Field Set affects configuration but does not control visibility.

C & D: Default Pricing Table and Price Editable settings do not impact visibility on the Configure Products page.

ï‚· Salesforce CPQ Reference:

Managing field visibility is outlined in CPQ Field-Level Security documentation ​.

ï‚· 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 references 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 ​.

ï‚· Requirement Overview:

Calculate the pricing steps for a subscription product with a 24-month term.

ï‚· Calculation Details:

Regular Unit Price:

Default Subscription Term = 12 months.

Adjusted for 24 months: $120 × 24 / 12 = $216.00.

Customer Unit Price:

Apply 10% Volume Discount: $216.00 × (1 − 0.10) = $194.40.

Apply 20% Additional Discount: $194.40 × (1 − 0.20) = $172.80.

Net Unit Price:

Apply 5% Partner Discount: $172.80 × (1 − 0.05) = $164.16.

ï‚· Validation:

Verify each step in the Salesforce CPQ price waterfall to ensure accuracy.

ï‚· Requirement Overview:

Maintenance Feature: At least one Product Option must be selected.

Support Feature: At least one and no more than two Product Options must be selected.

ï‚· Key Configurations:

Min Options = 1: Ensures users select at least one option.

Max Options = 2: Ensures users cannot select more than two options.

ï‚· Steps to Configure:

Navigate to the Feature Record for Maintenance and set Min Options = 1.

Navigate to the Feature Record for Support and set Min Options = 1 and Max Options = 2.

ï‚· Validation:

Test the bundle in the Quote Line Editor and verify the selection behavior for both Features.

ï‚· Requirement:

Different profiles need to see distinct sets of fields in the Quote Line Editor.

ï‚· Solution:

Create two field sets on the Quote Line object, one for each profile.

Use a text formula field named EditLinesFieldSetName on the Quote object to dynamically return the appropriate field set name based on the user’s profile.

ï‚· Why Other Options Are Incorrect:

A & B: Field sets must be created on the Quote Line object, not the Quote object.

D: This duplicates C but introduces a typo or incorrect description in the explanation.

ï‚· Salesforce CPQ Reference:

Field set configurations for the Quote Line Editor are detailed in CPQ Field Configuration Documentation ​.

ï‚· Requirement Overview:

Reference specific Error Condition records in the Advanced Condition field of a Product Rule.

ï‚· Solution:

Use the Index field value from the Error Condition record in the Advanced Condition formula.

ï‚· Example:

If the Index field value is 1 for a specific Error Condition, reference it as 1 in the Advanced Condition (e.g., 1 AND 2).