Free Practice Questions for Salesforce Sales-Admn-202 Exam

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

 Requirement:

Maintenance and Support products must display in separate sections during configuration.

Support products should appear above Maintenance products.

 Solution:

Product Features are used to organize Product Options into sections.

The Number field on Product Features determines the order in which the sections appear.

Support should have a lower Number value to appear above Maintenance.

 Salesforce CPQ Reference:

The Product Features Configuration Guidelines explain how to use features and their ordering mechanisms ​.

 Requirement:Populate a Configuration Attribute with a dynamic value when the configurator page loads.

 Solution Mechanics:

Process Builder can be used to dynamically set values on records based on predefined logic.

By targeting the Product Option field, which maps to the Configuration Attribute, Process Builder ensures that the value is set upon record creation.

 Steps to Implement:

Create a new Process Builder.

Trigger on the creation of the Quote Line record (or related record based on Configuration Attribute setup).

Define criteria to determine the dynamic value.

Use the Update Records action to populate the Product Option field with the default value.

 Advantages of Process Builder:

Allows for dynamic and conditional logic.

Automates the default value population without user intervention.

 Testing and Validation:

Create a test bundle with the Configuration Attribute.

Load the configurator and verify that the attribute is pre-populated.

 Scenario Breakdown:

The original subscription starts with 100 licenses.

After the first year, the count decreases to 80 licenses.

After the second year, the count increases to 120 licenses.

 Quantity Adjustments:

Original Subscription: The initial agreement is for 100 licenses over 36 months.

First Amendment: Reduces the quantity to 80 licenses for the remaining term after the first year.

Second Amendment: Increases the quantity to 120 licenses after the second year.

 Validation:

Salesforce CPQ keeps track of subscription adjustments through the Contract object.

Amendments reflect updated quantities while preserving the history of original and amended subscriptions.

Requirement:

Localize Quote Terms into three selectable languages for the quote PDF output.

Solution Steps:

Step A: Create a picklist field (e.g., Output Language) on the Quote object with language codes (e.g., EN, FR, DE) as values.

Step B: Create Localization records for each Quote Term in all three languages, ensuring the Quote PDF reflects the selected language.

Why Other Options Are Incorrect:

C: "Allow Output in Different Languages" is not an actual managed package setting.

D: Setting the Language field alone does not dynamically manage multiple languages for PDF generation.

Salesforce CPQ Reference:

Localization of Quote Terms is covered in CPQ Multi-Language Configuration Guidelines ​.

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

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

 Requirement Overview:

Prevent non-admin users from editing a specific Quote Term.

 Key Configuration:

The Locked checkbox on a Quote Term record ensures that the term is non-editable for all users except admins.

 Steps to Implement:

Navigate to the Quote Term record.

Check the Locked checkbox.

Save and test by logging in as a non-admin user to confirm editing is disabled.

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