The three core principles of scoping a Revenue Cloud (CPQ + Billing) project are:

✔ A — Alignment with customer on CPQ & Billing terminologyCPQ/Billing have specific terms (bundles, subscriptions, MRR, usage, amendments).

Shared vocabulary is essential for project success.

✔ C — Lead with business requirements and processSalesforce methodology stresses understanding:

Selling motions

Billing processes

Amendment/renewal lifecycle… before discussing configuration or technology.

✔ D — Think transformation before customizationRevenue Cloud succeeds when customers improve processes rather than recreating legacy systems.

Why the incorrect options fail:Option

Why Incorrect

B. Add new technology to existing process

Bad practice. Revenue Cloud encourages redesigning outdated processes, not replicating them.

E. Interview customer first before knowledge sharing

Opposite of best practice. Discovery is collaborative; knowledge sharing happens early.

The customer asks for customization because of a legacy system process.

Salesforce methodology says:

First validate whether the requirement is truly necessary in Salesforce or whether the legacy process should be transformed.

Therefore, the first step is:

✔ A — Ask follow-up questions to ensure the legacy process has business justificationYou must determine:

Why the process exists today

Whether it is needed in the new system

Whether CPQ or Billing already support the requirement natively

Whether it introduces unnecessary technical debt

Only after justification should you:

Consider customization

Estimate hours

Add developers or change orders

Thus, A is the correct first step.

Scenario SummaryUniversal Containers sells a bundle “Corporate IT Solutions.”

Inside it is a product option: Hardware Firewall.

Requirement:

If the customer previously purchased that Hardware Firewall (historical purchase),

Then hide the product option inside the bundle during configuration.

This is a Configuration Rule

Using Selection/Filter logic to hide options

The rule must trigger as soon as the bundle loads, because the product option must be hidden before the user interacts with the bundle.

What type of Product Rule?Which Evaluation Event is Correct?Salesforce CPQ Product Rule Evaluation Events:

Event

When it Fires

Typical Use

Load

When the configuration page loads the first time

Hide/show options, preselect options, set initial values

Edit

On any user modification

Rerun rules based on changes

Load and Edit

Both events above

When both initial setup and change handling are required

Save

When the quote line editor is saved

Validation rules that block save

We need the product option to be hidden immediately when configuring the bundle.

It is not dependent on user edits.

It uses historical purchase data (Opportunity Product / Asset / Subscriptions).

In this requirementTherefore, the rule should fire at initial load only, not waiting for user interaction.

Always → not a valid Product Rule Event type in CPQ.

Save → too late; user would see the option before it ' s hidden.

Load and Edit → unnecessary; we do not need edits to trigger this rule.

Edit → would fail because hiding must occur before user interaction.

Why Not the Others?Salesforce CPQ Documentation AlignmentCPQ Product Rules documentation states:

Use Load when you want the rule to evaluate immediately when the configurator opens, typically for hiding, filtering, or preselecting options.

This matches the required behavior perfectly.

When a Revenue Cloud project is escalated, the Project Manager is the role accountable for:

Overall project success

Scope, timeline, budget

Risk management

Issue resolution

Stakeholder coordination

Salesforce implementation methodology is clear:

The Project Manager owns project outcomes.

Thus D is correct.

When dealing with large quotes, Salesforce CPQ may hit platform governor limits (CPU time, SOQL limits, etc.) during save and recalculation.

Salesforce CPQ provides the Large Quote Threshold setting, which instructs CPQ to switch to a more efficient calculation mode once the quote line count exceeds the threshold.

The Salesforce documentation states:

Large Quote Threshold should be set to a number below the volume that triggers governor limits during testing.

It is not set arbitrarily; it must be based on empirical volume testing results.

This avoids synchronous processing of too many quote lines and forces CPQ to optimize its calculation path.

Therefore, option D is the correct implementation.

Your CPQ org is performing poorly because:

30 Process Builders running on Quote & Opportunity

Heavy customization

Excessive automation layers

Salesforce best practice for Revenue Cloud:

Remove technical debt BEFORE designing the CPQ/Billing solution.

Thus:

✔ C — Baseline performance and fix technical debt firstReasons:

CPQ depends heavily on synchronous calculations

Custom automations drastically increase sync time

Process Builder is deprecated; should be migrated to Flow

Poor performance must be cleaned before CPQ design

Why others are wrong:Option

Why Incorrect

A — Upgrade CPQ

Upgrading cannot fix org-level technical debt.

B — Mark issues out-of-scope

Avoiding technical debt leads to project failure.

D — Extend customization

Adding code on top of a broken process worsens performance.

Thus C is correct.

Scenario:

A customer has:

A posted invoice

A new order for the same account

Wants to add items without using invoice batches

The correct approach:

✔ D — Use Bill Now on the new order and consolidate invoicesSteps:

Run Bill Now on the new order → generates a new invoice immediately.

Enable Invoice Consolidation (Billing settings / Account level).

Combine invoice lines from the new invoice into the already posted invoice.

Salesforce Billing supports invoice consolidation even after one invoice is posted.

Why the other options are wrongOption

Why Incorrect

A — Credit then Bill

Unnecessary; original invoice is correct and should remain posted.

B — Bill Now + reparent invoice lines

Reparenting posted invoice lines is NOT supported.

C — Cancel and Rebill

Only used to correct errors, not to add new order items.

Thus D is the correct solution.