Free Salesforce Sales-Admn-202 Practice Exam with Questions & Answers

 Requirement:

Migrate existing contracts to a new Product version upon renewal.

 Solution:

Update the Renewal Product field to specify the new version of the Product.

Enable the Renewal Forecast checkbox on the Contract to ensure renewal Quotes reference the new Product version.

 Why Other Options Are Incorrect:

B: Changing the Product Lookup on the Subscription directly bypasses standard renewal processes.

C: Selection Product Rules enforce configurations during quoting but are not suitable for renewals.

D: Price Rules do not modify Product references during renewal Quotes.

 Salesforce CPQ Reference:

Renewal product management is outlined in the CPQ Subscription and Renewal Guidelines ​.

 Requirement:

Restrict the products visible during the configuration of a dynamic bundle.

 Solution:

Use a Default Filter in a Product Rule. This ensures only the specified set of products is displayed in the configurator for the dynamic bundle.

 Why Other Options Are Incorrect:

A: Optional filter is not a valid Product Action.

B: The Show action determines visibility but does not enforce restrictions on selections dynamically.

D: Enable action is used to activate a previously disabled product but does not filter selections.

 Salesforce CPQ Reference:

Dynamic bundles and filtering actions are detailed in CPQ Product Rule Configuration Guidelines ​.

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

 Requirement Overview:

Ensure that the Contract Name field is visible to users when initiating an Amendment.

 Key Configuration:

The Active Contract Lookup Field Set on the Contract object determines which fields appear when selecting a Contract for an Amendment.

 Steps to Configure:

Navigate to the Field Set named Active Contract Lookup on the Contract Object.

Add the custom Contract Name field to the Field Set.

 Validation:

Test the Amendment process to confirm that the Contract Name field is visible.

 Issue:

Sales reps experience excessive horizontal scrolling to access the Clone and Delete actions in the Quote Line Editor.

 Solution:

Quote Line Editor Drawers provide a compact and user-friendly way to access actions without excessive scrolling.

 Steps to Configure:

Navigate to Setup > Custom Actions.

Configure the Clone and Delete actions to appear in the Quote Line Editor drawers.

 Validation:

Open the Quote Line Editor and confirm that the actions are accessible without horizontal scrolling.

 Requirement:

Group products in collapsible sections based on Product Family in the Add Products page.

 Solution:

Set the Product Results Group Field Name in Additional Settings to Product Family. This groups products by their Product Family in the Add Products page.

 Why Other Options Are Incorrect:

A: Solution Groups apply to Quote Lines, not the Add Products page.

B: Adding fields to the Search Results Field Set does not enable grouping functionality.

C: The Product Search Plugin is unrelated to grouping.

 Salesforce CPQ Reference:

Configuring product grouping is detailed in CPQ Product Search and Results Configuration ​.

 Issue:

The validation error message appears immediately after a user sets a specific value in the Configuration Attribute, even before saving.

 Solution:

Setting Apply Immediately to False ensures that changes in Configuration Attributes do not trigger immediate validations. Instead, validations occur only upon clicking Save.

 Why Other Options Are Incorrect:

A: Evaluation Action does not exist as a field for Product Rule Error Conditions.

C: Changing the Apply Immediately field for Product Options does not affect the Configuration Attribute's behavior.

D: Setting Evaluation Event to Save applies to the rule's scope but does not address Configuration Attribute settings.

 Salesforce CPQ Reference:

Configuration Attribute Settings are explained in CPQ Configuration Attribute documentation ​.

Requirement:

Prevent users from reconfiguring a bundle after its initial configuration.

Solution:

Set Configuration Type to Allowed to permit configuration during initial setup.

Set Configuration Event to Add to allow configuration only when the product is added, blocking reconfiguration later.

Why Other Options Are Incorrect:

A: Disabled blocks all configuration, including initial setup.

B: Configuration Event = Always allows continuous reconfiguration.

D: Reconfigure Line Custom Action is unrelated to this requirement.

Salesforce CPQ Reference:

Configuration Type and Event settings are documented in Bundle Configuration ​.

 Requirement Overview:

Adjust the List Price dynamically based on the geographic area using a custom Price Multiplier stored in a custom object.

 Solution Details:

Custom List Unit Price Field: Store the adjusted List Price for the specific geographic area.

Lookup Price Rule: Retrieve the multiplier from the custom object and calculate the adjusted List Price.

 Steps to Configure:

Create a Custom Field (e.g., Custom List Unit Price) on the Quote Line.

Create a Lookup Price Rule to:

Retrieve the Price Multiplier from the custom object.

Calculate and populate the custom List Unit Price field.

 Validation:

Generate a Quote and confirm the List Price reflects the appropriate multiplier for the geographic area.

 Issue Context:

Lookup Price Rules rely on the SBQQ__LookupObject__c field to reference the target object (e.g., Rental Rates).

If this API name is inaccurate or incorrectly input, the rule will fail to retrieve the desired value.

 Review Steps:

Go to the Price Rule record.

Check the SBQQ__LookupObject__c field. Confirm the API Name of the Rental Rates object is accurate.

Example: Ensure the API name matches exactly (e.g., Rental_Rates__c).

 Additional Checks:

Verify the Lookup Queries. Ensure the filter conditions correctly target a valid record on the referenced object.

 Salesforce Documentation Reference:This behavior follows Salesforce CPQ's guidelines on Lookup Price Rules configuration​​.