Pass the Salesforce Revenue Cloud Consultant AP-223 Questions and answers with CertsForce

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.

SKU rationalization reduces catalog complexity and improves CPQ performance by merging duplicate or similar products.

✔ A — Same product names with different attribute valuesUse Product Options, Attributes, or Configuration Attributes instead of separate SKUs.

✔ C — Same product names with different bulk discount levelsUse Discount Schedules instead of duplicating products.

✔ E — Same product names commonly found in the same bundleUse one product with options/rules, rather than multiple redundant SKUs.

Why others are incorrect:Option

Why Wrong

B — Same products with different serial numbers

Serial numbers belong on Assets, not separate products.

D — Same names with different terms

Use Subscription Term or Term picklist, not separate SKUs.

Thus A, C, E is correct.

The question:

Which feature is needed to split Order Products into different Invoice Runs?

In Salesforce Billing, the feature that controls how order products are separated into different invoice runs is Invoice Group.

✔ Why Invoice Group is the correct answerThe Invoice Group field on:

Order Product

Order

Invoice

is used to:

Separate order products into different invoices within the same invoice run, or

Ensure specific order products are invoiced in different invoice runs entirely.

The Billing Engine evaluates Invoice Group when generating invoices:

Order Products with different Invoice Group values → will be generated on different invoices or different invoice runs, depending on the configuration.

This is the official Salesforce Billing mechanism for splitting invoice generation.

The three customer teams that must be involved in Revenue Cloud scoping are:

✔ A — Information (Product / Pricing owners)They define product catalog rules, pricing models, and offerings.

✔ B — Technology (IT/Architecture)Ensures integration, data migration, security, and platform alignment.

✔ C — Sales OperationsOwns quoting flows, approvals, discounting, sales motions, and user experience.

These teams define core CPQ processes.

Why others aren't required at scoping:Team

Why Not Required

D — Accounting/Finance

Essential for Billing scoping, but not required for CPQ-only scoping unless Billing is in scope.

E — Customer Service

Usually relevant for Service Cloud and CALM, not initial CPQ scoping.

F — Human Resources

Irrelevant to CPQ and Billing.

Thus A, B, C is correct.

Salesforce CPQ Renewals use two fields:

Used for pipeline forecasting

Should be checked as soon as the contract activates

Indicates revenue is expected at renewal

Indicates the renewal quote has actually been generated

Should be checked close to the contract end date

1. Renewal Forecasted2. Renewal QuotedThis is standard Salesforce CPQ renewal process guidance.

Correct logic:Forecast early, quote late.

Thus:

✔ D — “Renewal Forecasted should be checked early; Renewal Quoted should be checked near Contract End Date.”

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

Error:

“Attempt to de-reference a null object” while amending migrated contracts/subscriptions.

This is the classic CPQ issue when legacy contract/subscription data is missing required fields.

Subscription Start / End Dates

Quantity

Price fields

Billing Frequency

Term

Amendment-related fields (AmendmentStartDate, etc.)

Subscription Product

Related Order Product

Related Asset (if asset-based)

During amendment, CPQ expects:Missing or incorrectly populated fields cause CPQ code to attempt to reference null values → null pointer exception.

Thus:

✔ C. Required fields are missing or incorrectly populated

Why the other options are incorrect:Option

Why Incorrect

A. Migrated contracts cannot be amended

False. Salesforce explicitly supports amendments on migrated data if fields are populated correctly.

B. Asset-based renewal required

Not required—CPQ supports quote-based and asset-based renewal models.

D. Missing lookup to source Quote Line

Not required for legacy subscriptions; CPQ amendments work without source quote lines.

Thus C is the only valid root cause.

Setting Legal Entity on:

Order Product

Order Product Consumption Schedule

Must be scalable, bulk-safe, and future-proof.

The most performant and Salesforce-recommended approach is:

No additional DML required

Runs before insert and update

Bulk-safe

Better performance than Workflow or Process Builder

No need to use QCP, which only affects Quotes—not Orders or Schedules

✔ Before-Save Flow (Record-Triggered Flow)Thus D is correct.

A governance structure is essential in every Revenue Cloud implementation.

It ensures:

✔ C — Clarity on roles & responsibilitiesAvoids confusion, ensures accountability.

✔ D — A communication plan between implementation team & customerCritical for issue management, design reviews, sprint planning.

✔ E — Alignment on assigned workEnsures no duplication, no missed tasks, and smooth execution.

Why A and B are incorrect:Option

Reason

A

Governance does not mean the team works independently.

B

Governance does not assign extra work to the customer.

Thus C, D, E is correct.