Salesforce Updated AP-223 Exam Questions and Answers by aras

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.

Salesforce upgrades Preview sandboxes before production. To ensure testing is done on the next release before go-live:

✔ A — Review status.salesforce.com for release and sandbox cutoff datesThis tells you:

When sandboxes will upgrade

Deadlines for refreshing to get onto Preview

Release milestones

✔ C — Determine whether your sandbox is on a preview or non-preview instanceThis determines your next action:

Preview instance → sandbox upgrades early

Non-preview → sandbox upgrades after production

This is essential to test the implementation before production is upgraded.

Why B and D are incorrectOption

Why Incorrect

B — “All sandboxes upgrade at the same time”

False: preview vs non-preview sandboxes upgrade at different times.

D — “Submit a ticket to support to upgrade sandbox”

Salesforce does not move or upgrade sandboxes via support case. Release timing follows the published schedule only.

Final Answer: A, C

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.

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.