Free Salesforce Sales-Admn-202 Practice Exam with Questions & Answers | Set: 4

 Scenario:

A Price Rule utilizes a Lookup Object and Lookup Queries, and multiple records meet the criteria for a single Quote Line.

 Behavior:

When more than one lookup record meets the criteria, Salesforce CPQ does not apply any value to the Target Field. Instead:

The Target Field retains its original value.

An error message is displayed in the Quote Line Editor, notifying the user of the conflict.

 Why Other Options Are Incorrect:

A & D: Salesforce CPQ does not resolve ties by sorting records alphabetically.

C: The system does not apply values based on record creation date.

 Salesforce CPQ Reference:

Lookup Queries behavior and error-handling are outlined in CPQ Price Rules Configuration Guidelines ​.

 Issue Context:

A Contract could not be created from an Order for a new customer.

 Troubleshooting Steps:

A. Confirm Order Product Activation:

Contracts can only be generated for activated Order Products.

C. Check Apex Jobs:

Errors in the contracting process are logged in Apex Jobs. Review these logs for potential issues.

E. Ensure Subscription-Based Order Product:

Contracts require at least one subscription-based Product on the Order.

 Validation:

Verify that all conditions are met and retest the Contract creation process.

 Requirement:

Sales reps need to identify Product Options linked to Quote Lines in the Quote Line Editor.

 Solution:

Enabling Visualize Product Hierarchy organizes Quote Lines based on their position within the bundle, displaying the parent-child relationship.

 Why Other Options Are Incorrect:

A: The Product Option Drawer enables detail viewing but does not organize Quote Lines.

B: Preserve Bundle Structure applies to output documents, not the Line Editor.

D: Keep Bundle Together affects grouping but not hierarchy visualization.

 Salesforce CPQ Reference:

Hierarchy settings are covered in the Quote Line Editor Configuration documentation ​.

 Requirement:

Certain products should only be available as part of a bundle, not sold separately.

 Solution:

Setting the Component checkbox to TRUE on the Product ensures it is only available as a component within a bundle.

 Why Other Options are Incorrect:

A: Removing Price Book Entries restricts pricing but does not limit availability.

B: Configuration Event field is unrelated to this functionality.

D: Product Rules are not required for this basic configuration.

 Salesforce CPQ Reference:

The Component checkbox functionality is documented under Product Configuration in CPQ ​.

 Requirement:

Clients can negotiate a discount for Product A until a specified date before contract activation.

 Relevant Fields on the Contracted Price Record:

Product: Identifies Product A as the subject of the negotiated price.

Expiration Date: Specifies the end of the discount eligibility period.

Discount: Sets the agreed discount percentage for the negotiated price.

 Salesforce CPQ Reference:

Contracted Price Record management is key to implementing client-specific pricing strategies ​.

In Salesforce CPQ, when search filters are configured with predefined values and visible to sales reps, their interaction with the filter is determined by the filter’s configuration and available operators. The behavior described here is tied to Search Filters in the Product Selection screen, which allow users to refine the list of displayed products based on specific criteria.

Search Filter Configuration:

Predefined Filter Value: Here, the filter is set with a value ("Green").

Operator: The operator “starts with” limits the search to product codes beginning with the text "Green."

Sales Rep Interaction with the Filter:

The visibility of the search filter enables sales reps to view and interact with the criteria during product selection.

Specifically, sales reps have the ability to delete the predefined text to ignore the filter and retrieve a broader or unrestricted product list.

Documentation Alignment:According to Salesforce CPQ guidelines (as referenced in the Salesforce CPQ package settings and user behaviors), if filters are not marked as "required," users can remove or modify the filter values dynamically. This is designed to offer flexibility during quoting while maintaining filter defaults for ease of use.

The interaction described above aligns with Salesforce CPQ's behavior regarding visible search filters, emphasizing that sales reps can clear the filter text unless restricted by additional customization.

Use Case Reference:

When a sales rep begins a quote and searches for products, the filter defaults to "Green."

If the rep does not want to limit the product search to codes starting with "Green," they can simply remove the text and refresh the results.

Relevant Salesforce CPQ References:

Search Filters in the Quote Line Editor section of CPQ documentation .

Guidelines for Search Filter Configuration and behaviors when visible filters are not required .

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:

Track individual serial numbers for each unit of Product A sold.

 Solution Details:

Asset Conversion Field determines how assets are created from Quote Lines.

Setting Asset Conversion to One Per Unit creates one Asset record for each unit sold, allowing tracking of individual serial numbers.

 Implementation:

Navigate to the Product Record for Product A.

Set Asset Conversion to One Per Unit.

 Justification:

This setup aligns with Salesforce CPQ's approach for granular tracking of Assets associated with product sales​​.

When amending a contract in Salesforce CPQ, the net pricing of products can sometimes appear incorrect, especially when quantities are adjusted on existing subscriptions. The "Revised Quantity" field on the Subscription record is used during amendments to reflect the updated quantity of a subscription product after the amendment. If this field is set incorrectly or unexpectedly (e.g., manually or via automation), it can override the expected quantity and cause discrepancies in pricing calculations, especially for existing products. This aligns with the scenario where the issue only occurs when quantities are adjusted on existing products. Option B (Price Rule firing On Calculate) could affect pricing but typically wouldn’t target only existing products or cause quantity-specific issues unless explicitly designed to do so. Option C (Price Rule firing Before Calculate) might alter pricing but wouldn’t directly tie to quantity adjustments on amendments. Option D (Discount Schedule with Cross Order unselected) affects pricing tiers but isn’t directly related to amendment quantity adjustments. Per Salesforce CPQ documentation, the "Revised Quantity" field is a key factor in amendment scenarios impacting pricing consistency.

 Issue Context:

Users encounter a warning when searching Campaign records in the Quote Line Editor.

 Root Cause:

For Lookup fields to work correctly in Salesforce CPQ's Quote Line Editor, a Twin Field must exist on the target object (Campaign) with the same API name as the Quote Line lookup field.

 Solution Steps:

Create a custom field on the Campaign Object with the same API name as the lookup field on the Quote Line Object.

Ensure the field types match (e.g., both are Lookup fields or Text fields).

 Validation:

Test the functionality by searching for Campaign records in the Quote Line Editor. The warning message should no longer appear.

 Salesforce CPQ Documentation Reference:

This is a common configuration for CPQ Lookup fields in the Quote Line Editor​​.