Free Sales-Admn-202 sample questions

Correct answer: Scope: Calculator; Event: On Calculate

The 'Calculator' scope targets the Quote Line Editor calculation sequence. The 'On Calculate' event ensures the rule runs during the calculation cycle (after initialization and before save). Using 'Configurator' scope would target the product bundle configuration screen, which is incorrect for Quote Line updates that depend on Account data.

Correct answer: The Product 'Region__c' field is a restricted picklist, which prevents Twin Field mapping.

In Salesforce CPQ Twin Fields logic, if the source picklist (on Product) is a Restricted Picklist, the values often fail to map to the target (Quote Line) if the metadata validation is strict or if the system cannot verify the value integrity during the copy process. Disabling 'Restricted' on the picklist definition usually resolves this specific twin field limitation.

Correct answer: Error Conditions referencing Summary Variables failed because Summary Variables were not migrated first.

Product Rules often contain Error Conditions or Actions that reference Summary Variables. If the Summary Variable records (SBQQ__SummaryVariable__c) are not migrated before the Product Rules (SBQQ__ProductRule__c) and their child Error Conditions, the lookup relationships will fail, causing the insert to error out.

Correct answer: Create a 'Localization' record for each product with the French content.

Salesforce CPQ uses its own Localization object (SBQQ__Localization__c) to translate data records like Product Name and Description for the CPQ UI. While Translation Workbench handles metadata (labels, picklists), CPQ-specific data records require Localization entries to render correctly in the Quote Line Editor.

Correct answer: Lookup Query

Lookup Queries allow Price Rules (and Product Rules) to query data from objects that are not directly related to the Quote. By defining a Lookup Query (SBQQ__LookupQuery__c) record that matches criteria (e.g., Region, Product Family) against the custom object, the rule can retrieve the 'Margin_Rate__c' value.

Correct answer: The user should be a non-human integration user to prevent token expiration issues.

It is a best practice to use a dedicated non-human admin user (integration user) for authorizing the CPQ Calculation Service. If a human user authorizes it and then leaves the company or changes their password, the token becomes invalid, causing calculation failures for all users.