Free Practice Questions for Salesforce AP-223 Exam

The Salesforce Safe Harbor statement exists to remind customers:

They should only make scoping, planning, design, and purchasing decisions based on current, available functionality, not forward-looking statements or roadmap presentations.

Salesforce does not guarantee:

Release timing

Exact feature delivery

Backward compatibility

User Story“As a pricing manager, bulk discounts must include previously purchased quantities for pricing calculations on the quote to reward loyal customers.”

This refers to historical purchases influencing tiered or volume discounts.

In Salesforce CPQ, the only native feature that supports “include prior purchases when calculating discount tiers” is:

✔ Discount Schedules with Cross Orders enabledThis setting tells CPQ to:

Look at existing subscriptions, assets, orders, and previous quote lines

Aggregate prior quantities

Apply tiered volume discount based on the total owned quantity + new quantity

But for Cross Orders functionality to work…

✔ Historical Subscriptions / Assets must existSo you must migrate historical:

Contracts

Subscriptions

Assets (if asset-based ordering)

Without that data, CPQ cannot aggregate historical quantities.

Correct answer: B and E✔ B — Populate Contracts, Subscriptions, and Assets with historical dataCPQ needs these to calculate previously purchased quantities.

✔ E — Discount Schedules with Cross Orders checkedThis is the actual feature that uses prior purchased amounts to determine discount tiers.

Why the other options are not correct:Option

Why Incorrect

A — Custom Action

Unnecessary. CPQ has native Cross Orders behavior.

C — Summary Variable

Summary variables do not summarize external historical purchases.

D — Migrate Orders & Invoices

Not required for CPQ pricing. Only Subscriptions/Assets matter.

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.

During UAT, any incident related to invoice totals must include information that allows the consultant or tester to reproduce and diagnose the issue quickly.

✔ B — Quote number, Order number, or Invoice numberThese IDs allow the consultant to immediately:

Locate the exact transaction

Review invoice lines, tax, proration, billing rules

Check data mapping and calculation sequence

This is essential for any Revenue Cloud troubleshooting scenario.

✔ D — Steps to replicate the issueWithout reproducible steps, diagnosis is almost impossible.

UAT defect triage requires:

Exact user actions

Fields populated

Sequence of operations (e.g., "Bill Now", "Invoice Run", etc.)

This is a Salesforce UAT best practice.

✔ E — Expected resultsCrucial for determining:

Whether the system is incorrect

Whether requirements were misunderstood

Whether recalculation logic (tax, proration, discounts) was expected to behave differently

Why Other Options Are IncorrectOption

Why Wrong

A — Description of new requirements

UAT incidents are not for new requirements; they are for defects.

C — Expected resolution date

Not part of incident description; it's part of project management, not defect logging.

Final Answer: B, D, E

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.

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

Before a scoping session, the consultant should understand:

A – Sample proposals → reveals quoting format, pricing models, product structure.

B – Product brochures → clarifies offerings, catalog categories, bundles.

D – Approval matrix → shows governance controls required in CPQ.

Incorrect:

C Salesforce release notes are irrelevant to understanding customer requirements.

E Financial statements do not contribute to CPQ/Billing scoping.

Correct answers: A, B, D.