Salesforce Sales-Admn-202 - Salesforce Certified CPQ Administrator

ï‚· Requirement Overview:

Admin needs to generate one Asset record for each unit of the Product upon contracting.

ï‚· Solution Details:

The Asset Conversion field determines how Salesforce CPQ creates Asset records from Quote Lines.

Setting Asset Conversion to One per Unit ensures that for each quantity of the Product, a corresponding Asset is created.

ï‚· Steps to Configure:

Navigate to the Product record.

Locate the Asset Conversion picklist and select One per Unit.

Save and test the configuration by creating a Quote, contracting it, and verifying the Asset creation.

ï‚· Requirement Overview:

Restrict sales reps to only selecting subscription Products when using the Add Subscriptions Custom Action.

ï‚· Solution Details:

The Search Filter for the Add Subscriptions action should include only subscription Products.

Setting the Filter Value to Hidden ensures that only Products matching the filter criteria are displayed.

ï‚· Steps to Configure:

Navigate to the Search Filter related to the Add Subscriptions action.

Set the Filter Value to True.

Mark the Hidden checkbox to restrict visibility to subscription Products.

ï‚· Validation:

Test the Custom Action to confirm that only subscription Products are visible.

Tiered pricing in Salesforce CPQ applies a cumulative price where each tier has a marginal rate (e.g., $9 per unit above 100). This matches the scenario: $1,000 for 0-100 units, then $9/unit for 101-500, $8/unit for 501-1,000, and $7/unit above 1,000, building on the prior tier’s total (e.g., $4,600 at 500). Option B (Tiered) supports this incremental pricing model. Option A (Block) uses fixed prices per range, not cumulative rates. Option C (Segmented) isn’t a standard CPQ pricing method. Option D (List) applies a flat unit price, ignoring tiers. Salesforce CPQ documentation defines Tiered pricing for this use case.

ï‚· Requirement Overview:

Ensure the Standard Warranty (a Percent of Total product) generates an Order Product when a partial Order is created.

ï‚· Solution:

When generating a partial Order, selecting a Shipping Container product triggers the automatic creation of a Standard Warranty Order Product, as the warranty is based on the container’s Net Price.

ï‚· Steps to Test:

Add a Shipping Container Quote Line and the Standard Warranty Quote Line to a Quote.

Create a partial Order, selecting the Shipping Container.

Verify that the Standard Warranty Order Product is generated.

ï‚· Issue:

Contract creation fails when the Contracted checkbox is checked on an Opportunity.

ï‚· Possible Causes:

A: If the Subscription Conversion Behavior is set to None, the product is not converted into a Subscription, preventing the Contract from being created.

B: The Opportunity requires a Primary Quote to generate a Contract, as the Contract details are derived from the Quote.

ï‚· Why Other Options Are Incorrect:

C: If the Subscription Pricing field is blank, the product is treated as non-subscription but does not prevent Contract creation.

D: Products with Subscription Pricing = One-time are not converted to Subscriptions, but they do not block Contract creation.

ï‚· Salesforce CPQ Reference:

Contract creation requirements and behaviors are documented under CPQ Subscription Management Guidelines ​.

ï‚· 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:

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

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

ï‚· Requirement Overview:

Universal Containers wants to update the Quantity of a specific Product in the Quote Line Editor via a Price Rule.

The Price Rule should target only this specific Product.

ï‚· Key Mechanism:

Use a Price Condition on the Price Rule to evaluate a Quote Line field that uniquely identifies the Product (e.g., Product Code or Product Name).

ï‚· Steps to Configure:

Navigate to the Price Rule.

Add a Price Condition:

Field: Select a field from the Quote Line that identifies the Product.

Operator: Equals.

Value: Enter the unique value (e.g., Product Code or Name).

Configure the Price Action to update the Quantity field.

ï‚· Validation:

Test the rule by adding the specific Product to a Quote and confirming that the rule updates its Quantity as expected.

In Salesforce CPQ, amendments adjust subscription quantities incrementally. The original sale (Quote Line and Subscription) is 100. The first amendment reduces to 80, a decrease of 20, so the Quote Line is 80 (absolute), and the Subscription delta is -20 (reflecting the change). The second amendment increases to 120, an increase of 40 from 80, so the Quote Line is 120, and the Subscription delta is 40. Subscription quantities in amendments show the net change (-20, 40) rather than absolute values (80, 120), aligning with CPQ’s amendment mechanics. Option B correctly reflects this: Quote Lines (100, 80, 120) show user-facing totals, while Subscriptions (100, -20, 40) show deltas. Salesforce CPQ documentation explains this behavior in amendment scenarios.