In a Salesforce CPQ scoping session, the first documentation created is the Business Process Map, because:

It defines the customer’s selling, quoting, approval, pricing, contracting, renewal, and ordering processes.

It ensures all stakeholders are aligned on “how the business works now” before CPQ design begins.

Only after processes are mapped can product structure, order management, and quote document needs be designed.

Salesforce Revenue Cloud methodology always starts with:

Business Process Documentation → Requirements → Solution Design

Thus C is correct.

Salesforce user story best practices include:

A – Know the business process the story supports

B – Identify the actor/persona (Sales Rep, Billing Ops, Pricing Manager, etc.)

E – Identify acceptance criteria (must-have conditions for the story to be complete)

Incorrect options:

C Designing the solution before the business process is finalized violates Salesforce implementation methodology.

D Writing test scripts is UAT preparation, not part of writing user stories.

When Salesforce CPQ attempts to amend a contract, it relies on a very specific set of fields on:

Contract

Subscription

Asset (for asset-based models)

Quote Line (for amendment and renewal linkage)

If mandatory amendment fields are missing, CPQ ' s amendment engine will throw errors — most commonly:

“Attempt to de-reference a null object”

This happens because CPQ expects certain relationships and data points that do not exist in legacy-migrated records unless populated correctly.

✔ Why C is the correct answerWhen migrating historical Contracts and Subscriptions, CPQ requires certain fields to be populated, such as:

Account

StartDate

EndDate

Contract Number

Pricebook2Id

Contracted = TRUE

ContractId

Product2Id

Quantity

StartDate

EndDate

ListPrice

SalesPrice

SubscriptionType

Status = Active

TermStartDate

TermEndDate

Most importantly:

OriginalContractedListPrice

OriginalContractedSalesPrice

OriginalQuantity

OrderProductId (for order-based renewals)

AssetId (required depending on renewal model)

Contract Required FieldsSubscription Required FieldsIf any of these fields are missing or incorrectly mapped, the amendment engine fails.

CPQ amendment logic does not require a source quote line for legacy migrations, nor does it block amendments on migrated data if all required fields are present.

Thus C is the only answer consistent with CPQ documented behavior.

❌ Why the other answers are wrongA. Migrated contracts and subscriptions cannot be amended using Salesforce CPQIncorrect.

Salesforce CPQ fully supports amendment of migrated contracts/subscriptions as long as the required data is populated.

B. Amendment requires asset-based renewal methodIncorrect.

Legacy migrations can use either:

Contract-Based Renewal, or

Asset-Based Renewal

There is no requirement to switch to asset-based renewal.

D. Legacy data missing lookup to source quote lineIncorrect.

A lookup to the original Quote Line (SBQQ__QuoteLine__c) is not required for amendments.

It is only needed to support:

Contracted pricing logic reuse

Certain renewal pricing behaviors

Some reporting use cases

Missing this field does not block amendments and does not cause this error.

The requirement:

" Bulk discounts include previously purchased quantities for pricing calculations. "

This refers to cross-order discounting, where historical quantities affect pricing on the new quote.

To support this:

✔ B – Contracts, Subscriptions and Assets should be populated with historical dataCPQ reads existing Subscriptions/Assets to determine previously purchased quantities.

Historical install base must be migrated for correct discounting.

✔ E – Discount schedules with Cross Orders checkedSalesforce CPQ includes an OOTB feature:

Discount Schedule → Cross Orders = TRUEThis allows the quantity tiers to consider historical purchases.

Incorrect options:

A Custom Action unnecessary unless data is external (not indicated here).

C Summary variables cannot aggregate off-contract historical quantities.

D Migrating invoices is not required for quantity-based pricing.

Thus, the validated answers are B and E.

A partner leading a Revenue Cloud Scoping session requires:

✔ A — Strong communication skillsEssential for facilitating workshops, documenting requirements, and aligning stakeholders.

✔ B — Effective at planning, monitoring, reviewingScoping is structured, requires:

Agenda control

Risk identification

Note capture

Validation cycles

✔ E — Understanding design pitfalls & mitigationCritical in CPQ + Billing, where poor scoping leads to:

Wrong pricing model

Incorrect renewal logic

Billing edge cases

Data migration problems

A good partner surfaces these risks early.

Why the wrong answers are incorrect:Option

Why Incorrect

C — Knowledge of competitor products

Not relevant to scoping Salesforce Revenue Cloud.

D — Experience with quota-carrying sales roles

Helpful but not foundational to scoping complex CPQ + Billing architecture.

Final answer for Q49 = A, B, E

For multi-level discount approvals in CPQ:

A – Identify backup approvers: Required because Salesforce Approval Processes must account for out-of-office or unavailable approvers.

D – Define discount thresholds for sales reps: Mandatory so the system knows when to trigger approvals.

E – Document approval levels: Ensures clear governance and reduces ambiguity.

Incorrect options:

B printing approval matrices is not a Salesforce implementation requirement.

C contradicts the purpose of approval controls.

Thus the correct answers are A, D, E.

The CPQ Quote Calculator is hosted by Salesforce in specific service regions.

Performance is optimized when the service region matches the Salesforce org location.

Since the German operation is hosted in the EU Salesforce instance, the performance-optimized setting is:

✔ Europe regionThis keeps latency minimal and significantly improves quote calculation speed.

When Price Rules are insufficient for complex pricing logic, Salesforce CPQ documentation directs consultants to the Quote Calculator Plugin (QCP) as the next escalation point.

QCP enables custom JavaScript logic executed inside the CPQ Quote Calculator, allowing manipulation of:

List price

Net price

Quantity

Custom logic loops

Conditional calculations beyond standard rule capabilities

Flows or Apex should not manipulate pricing during calculation because they run outside the CPQ calculator, causing inconsistent pricing results.

Hence the correct next step is QCP.

When users log in to Salesforce CPQ for the first time, the Post-Install Script must run.

This script:

Initializes CPQ user settings

Creates required calculation metadata

Ensures Quote + Quote Line permissions and defaults work

Enables Primary Quote logic

If an automation tries to set a new Quote as Primary, but the user has not run the CPQ post-install script, CPQ raises errors because internal references and fields are not yet initialized for that user.

This is a documented CPQ requirement.

Thus, A is correct, and all other options point to permission issues that do NOT cause this specific failure pattern.

The CPQ Quote Calculator runs in a designated Service Region. Performance increases significantly when:

The service region is geographically close to the Salesforce org.

Since the org is hosted in the EU:

✔ D — Europeis the correct service region, which reduces latency and speeds calculation.

Why the others are wrong:Option

Why Incorrect

A — No performance impact

100% incorrect; region affects latency heavily.

B — North America

Far from EU, adds latency.

C — Japan

Even slower.

E — Australia

Worst possible latency option.

Thus D is correct.