Free Practice Questions for Salesforce Sales-Admn-202 Exam

 Requirement:

Allow users to choose options and define quantities during bundle configuration.

 Configuration Types:

None (A): Users can freely choose options and set quantities.

Allowed (C): Users can choose options and optionally set quantities.

Required (E): Users must configure the options and define quantities.

 Why Other Options Are Incorrect:

B: Configurable is not a valid value for the Configuration Type field.

D: Disabled prevents any configuration, which contradicts the requirement.

 Salesforce CPQ Reference:

Configuration Types are documented under Bundle Configuration Guidelines ​.

 Scenario Breakdown:

Product A has a base list price of $100.

A quantity of 15 is entered on the quote.

Gold Hardware Maintenance Discount applies because contracted pricing is enabled.

Discount for the quantity range (11–20) is 15% (as shown in the table).

 Net Price Calculation:

List Price = $100

Discount = 15%

Quantity = 15

Net Total Price = $100 × 15 × (1 - 0.15) = $1,275.

 Justification for Selected Discount:According to Salesforce CPQ guidelines, when contracted pricing applies, it takes precedence over other Discount Schedules. The Gold Discount Schedule is therefore applied.

 Testing and Validation:Test the configuration using a sample quote to ensure the correct schedule is applied and the net total price matches the expected value.

 Requirement:

The processor is priced differently when sold as a standalone product versus as part of a laptop bundle.

 Solution:

Marking the processor as Bundled ensures the discounted price applies only when it is part of the laptop bundle.

 Mechanism:

When the Bundled checkbox is TRUE, Salesforce CPQ applies the discounted pricing for bundle components based on the defined Price Book Entry.

 Salesforce CPQ Reference:

Bundled pricing behavior is described in the Product Option and Bundle Configuration Guidelines ​.

 Considerations for Authorizing Calculation Service:

The Calculation Service must be authorized by a user who has sufficient privileges and stable permissions.

 Solution Steps:

Option B: Use a non-human admin user (e.g., an integration user) to authorize the Calculation Service. This ensures consistent access and avoids disruptions due to personnel changes.

Option C: Place the user at the top of the Role Hierarchy to ensure full visibility and access across relevant objects.

 Salesforce CPQ Reference:

Proper user configuration for the Calculation Service is outlined in the CPQ Authorization Guidelines ​.

Understanding the Requirement:

Within a bundle, Products A and B must be mutually exclusive, allowing the user to select either but not both.

If both products are selected, the system should automatically remove Product B and retain Product A.

Optimal Salesforce CPQ Solution:

Product Selection Rule:

This rule dynamically evaluates conditions and executes actions, such as adding or removing products.

It is suitable for automating the removal of conflicting products based on user selections.

Summary Variables:

Used to check if both products are selected during configuration.

Implementation Steps:

Step 1: Create a Product Rule:

Navigate to Product Rules in Salesforce CPQ.

Create a new rule with the following settings:

Type: Selection

Evaluation Event: Always

Scope: Product

Step 2: Define Error Conditions:

Add two Error Conditions to evaluate if both Product A and Product B are selected:

Error Condition 1: Check if Product A is selected using a Summary Variable.

Error Condition 2: Check if Product B is selected using a Summary Variable.

Step 3: Configure Product Action:

Add a Product Action to Remove Product B if both Error Conditions are true.

Ensure the rule prioritizes retaining Product A over Product B.

Rationale for Option A:

Option A is the most direct and efficient approach, leveraging Product Selection Rules to automatically enforce the requirement.

Options C and D use alert or validation rules, which display messages and rely on user intervention, failing the requirement of automatic resolution.

Option B introduces conflicting rules with differing evaluation orders, which can lead to complex and unpredictable behavior.

Validation and Testing:

Add the bundle to a Quote and configure it to select both Product A and Product B.

Verify that Product B is automatically removed, and Product A is retained.

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

 Requirement:

Apply a 10% discount to Product A on the Quote Line if the customer has previously purchased Product A (stored as an Asset).

 Solution:

Summary Variable:

Sum the Quantity field on Asset records for Product A.

Price Condition:

Verify that the Summary Variable is greater than 0 to confirm the customer has purchased Product A.

 Why Other Options are Incorrect:

B: Quote Lines do not track prior purchases; Assets do.

C, D: These do not align with the requirement to verify prior purchases via Assets.

 Salesforce CPQ Reference:

Summary Variables and their use in Price Rules are documented under CPQ Discounting Guidelines ​.

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

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

 Requirement Overview:

A nonrenewable subscription Product priced annually.

 Key Field Configurations:

Subscription Term = 12: Specifies an annual subscription.

Subscription Type = One-Time: Indicates that the Product is nonrenewable.

Subscription Pricing = Fixed Price: Defines a flat annual price.

 Steps to Configure:

Navigate to the Product record.

Update the fields as specified above.

Save and test by adding the Product to a Quote.

 Validation:

Confirm the subscription term and pricing are applied correctly and the product does not renew automatically.