Salesforce Certified CPQ Administrator 온라인 연습
최종 업데이트 시간: 2026년02월14일
당신은 온라인 연습 문제를 통해 Salesforce Sales-Admn-202 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Sales-Admn-202 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 212개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
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 .
정답:
Explanation:
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 .
정답:
Explanation:
Comprehensive Detailed Step-by-Step Explanation with all Salesforce CPQ Reference
To split orders based on product family when creating orders from quotes in Salesforce CPQ, the
following steps must be followed:
Enable the Allow Multiple Orders Setting
Navigate to Setup > Installed Packages and locate Salesforce CPQ.
Click Configure, then go to the Orders tab in the CPQ package settings.
Check the Allow Multiple Orders option. This allows multiple orders to be created from a single quote.
This setting ensures that products can be grouped and split into separate orders based on specific criteria like Product Family.
Set the Order By Field to Product Family
From the object management settings for Quotes, edit the Order By field.
Add "Product Family" as a picklist value if it is not already available.
On the Quote, select Product Family in the Order By field.
Save your changes. When creating an order, Salesforce CPQ will group quote lines into separate
orders based on the Product Family.
Process for Creating Orders
On the quote, select the Ordered checkbox.
Salesforce CPQ will automatically split the quote into multiple orders, grouping quote lines by the
Product Family value.
Notes and Considerations
If some quote lines do not have a value for the field used in the Order By, they will be grouped into one order.
This functionality is available in Salesforce CPQ editions starting from Summer ’16.
By following these steps, administrators can ensure that similar products are automatically separated into different orders based on their product family.
정답:
Explanation:
Requirement Overview:
Display the sum of a custom field in the standard Line Editor table without replacing the subtotal or
total fields.
Solution Details:
The Summary Fields field set on the Quote Line object controls which fields appear as totals in the Line Editor.
Steps to Configure:
Navigate to Setup > Object Manager > Quote Line.
Locate the Summary Fields Field Set.
Add the custom field to the field set.
Validation:
Open the Quote Line Editor and confirm that the sum of the custom field appears in the standard table, alongside other totals.
정답:
Explanation:
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.
정답: B
Explanation:
Requirement Overview:
Configure tiered pricing for Product A specific to a customer for all future Quotes.
Solution Details:
Use a Discount Schedule with tiered pricing.
Assign the Discount Schedule to a Contracted Price record tied to the customer's Account.
Steps to Configure:
Create the Discount Schedule with the desired tiers.
Navigate to the customer’s Account.
Create a Contracted Price record:
Reference Product A.
Assign the Discount Schedule.
Validation:
Generate a Quote for the customer and confirm the tiered pricing is applied correctly.
정답:
Explanation:
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.
정답:
Explanation:
Requirement Overview:
Limit the Product Options displayed in a bundle based on the service level selected by the user via a
Configuration Attribute.
Solution Details:
Selection Price Rule: Use a Selection Price Rule to dynamically show or hide Product Options based on the selected value of the Configuration Attribute.
Apply Immediately: Ensures that changes based on the service level selection occur in real-time
during configuration.
Steps to Configure:
Create the Selection Price Rule:
Define the Price Rule with a Condition targeting the Configuration Attribute value.
Use a Price Action to show or hide Product Options.
Set Apply Immediately:
Navigate to the Configuration Attribute.
Set Apply Immediately to TRUE.
Validation:
Test the bundle configuration by changing the service level and verifying the Product Options displayed dynamically update.
정답:
Explanation:
Requirement:
Sell a non-renewable support SKU in 1-month increments, with the ability to cancel before the
agreed end date.
Solution:
SubscriptionType = One-Time: Ensures the product is treated as a one-time charge, not renewable.
SubscriptionTerm = Number of Months: Allows the quote to define the length of the support
agreement.
Why Other Options Are Incorrect:
A and C: These configurations do not align with the requirement to sell support in defined monthly increments.
D: Marking the product as Renewable contradicts the requirement that the product is non-renewable.
Salesforce CPQ
Reference: SubscriptionType and SubscriptionTerm fields are detailed in the Subscription Products configuration guide .
정답:
Explanation:
Requirement:
Streamline the Quote Line Editor by enabling automatic calculations after each change.
Solution:
Enabling the Calculate Immediately setting in Managed Package Settings ensures calculations are triggered automatically whenever changes are made in the Quote Line Editor. Why Other Options Are Incorrect:
A: The Legacy Calculator setting is outdated and not related to automatic calculations.
B: Quick Calculate is a manual process that does not meet the requirement for automatic recalculation.
Salesforce CPQ
Reference: The Calculate Immediately Setting is described in the CPQ Managed Package Settings documentation
.
정답:
Explanation:
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.
Reference: Salesforce CPQ documentation highlights the effectiveness of Product Selection Rules for handling dynamic product configurations and resolving conflicts.
정답:
Explanation:
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 .
정답:
Explanation:
Comprehensive Detailed Step-by-Step Explanation with all Salesforce CPQ Reference Understanding the Issue:
The error message, “Product cannot be refunded. The quantity of Line # cannot decrease without a corresponding update,” occurs because the default behavior prevents a decrease in asset quantities unless explicitly allowed.
Asset Conversion for Product A is set to "One per Unit," requiring each unit to be treated as a separate asset.
Key Salesforce CPQ Setting:
Asset Amendment Behavior:
This field on the Product determines how CPQ handles amendments for asset-based products. Setting it to "Allow Refund" enables sales reps to reduce the quantity of assets during amendment quotes without generating errors.
Configuration Steps:
Navigate to the Product Record for Product A in Salesforce CPQ.
Locate the Asset Amendment Behavior field.
Change its value to Allow Refund.
Save the changes.
Impact of the Change:
Sales reps can now amend the quantity of Product A on amendment quotes.
The system will process the reduction in quantity without triggering an error, as the refund behavior
is explicitly enabled.
Verification:
Create an amendment quote for a contract involving Product A.
Adjust the quantity of Product A and confirm that the amendment processes successfully without
errors.
Reference: This approach is in line with Salesforce CPQ guidelines on managing amendments for asset-based products.
정답:
Explanation:
Understanding the Requirement:
Universal Containers wants sales reps to associate Campaign records with Quote Lines using a lookup field in the Quote Line Editor.
The requirement includes avoiding warning messages when searching for Campaign records.
Salesforce CPQ Lookup Field Behavior:
When a lookup field is added to the Quote Line Editor, Salesforce CPQ searches for records in the target object (e.g., Campaign).
To avoid warnings, the target object (Campaign) must have a specific field set named CPQ_Lookup, which defines the fields displayed in the search results. Steps to Implement the Solution:
Step 1: Navigate to the Campaign object in Salesforce Setup.
Step 2: Go to the "Field Sets" related list and click "New."
Step 3: Name the field set CPQ_Lookup (case-sensitive).
Step 4: Add the fields you want to display in the lookup search results (e.g., Campaign Name, Start Date, Owner).
Step 5: Save the field set.
Integration with the Quote Line Editor:
The system will now use the fields defined in the CPQ_Lookup field set when sales reps perform a search for Campaign records.
This ensures the lookup field operates without errors or warnings in the Quote Line Editor.
Key Considerations:
Ensure that all required fields for identifying Campaign records are included in the CPQ_Lookup field set.
Test the lookup functionality in the Quote Line Editor to confirm smooth operation.
Validation:
Add a Campaign lookup field to a Quote Line in the Quote Line Editor and test the search
functionality. Verify that the fields defined in the CPQ_Lookup field set appear in the search results
without warnings.
Reference: Salesforce CPQ documentation on setting up lookup fields and field sets emphasizes creating a CPQ_Lookup field set to avoid warnings
정답:
Explanation:
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.