Free Practice Questions for Salesforce AP-223 Exam

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.

Amendments in Salesforce Billing must maintain clean financial continuity. Any financial artifact still in an incomplete or unsettled state breaks future invoicing, because Billing cannot prorate, advance, or reconcile future periods correctly.

✔ B — Subscription linked to Order Product with unpaid invoice linesUnpaid invoice lines cause:

Billing to treat the subscription as financially “not settled”

Block future billing for that subscription

Incorrect Next Billing Dates

This is a documented reason for missed or incorrect invoice generation.

✔ C — Subscription linked to Order Product with draft invoice linesDraft invoice lines mean the invoice is not posted, so:

Revenue and billing are not finalized

Billing engine cannot determine the next billing boundary

Amendments generate incorrect billing periods

This absolutely causes incorrect future invoicing.

✔ D — Subscription linked to an unallocated paymentUnallocated payments interfere with:

Aging

Balance-based billing logic

Proper allocation of future charges

Billing expects charges and payments to be reconciled.

Why A and E are not correct:Option

Reason

A — Not contracting the amendment order

You must contract an amendment order, but failure to do so stops renewal/amendment flow, not future invoicing behavior.

E — Contracting from amended opportunity

This is the correct and expected process, not a problem.

Thus B, C, D are correct.

User Story:

“Sales users should be able to create new quotes with rate cards and account-specific discounts that honor originally negotiated pricing.”

This means the system must pre-store customer-specific negotiated prices.

In Revenue Cloud, the object used for this is:

✔ Contracted PricingContracted Pricing stores:

Account-specific price overrides

Custom discounting

Negotiated flat rates

Validity windows

When a new quote is created, Salesforce CPQ automatically applies Contracted Pricing to the relevant products.

Why the other options are incorrect:Option

Why Incorrect

B — Subscription

Tracks ongoing services, not negotiated pricing.

C — Order Product

Not used for quoting or negotiated rates.

D — Entitlements

Applies to support or warranty, not pricing.

The Salesforce CPQ calculation sequence includes:

Internal Initialization

QCP: onInitialization()

CPQ: Calculate Formulas (pre-calculation)

Price Rule Evaluation: Before Calculate

QCP: onCalculate()

Price Waterfall (Pricing Engine)

QCP: AfterCalculate()

Option D matches this exact order:

internal initialization → on Initialization → calculate formulas → Before Calculate → calculate quantities → On Calculate → Price Waterfall → After Calculate

To correctly load and rate Usage in Salesforce Billing, a Usage Record must contain the minimum required fields that allow the Billing Engine to:

Identify which subscription/order product the usage belongs to

Determine the billing period

Retrieve the correct rating method (per unit, tiered, etc.)

Apply account-level and billing-level context

Roll up usage into a Usage Summary for invoicing

Salesforce Billing documentation specifies that the following fields are required for rating:

Required Fields for Usage RatingField

Why it is required

Order Product (SBQQB__OrderProduct__c)

Links usage to the billable product and its pricing model

Start Date/Time

Used to determine billing period & usage summary matching

(End Date/Time)

Optional, depending on rating model

Quantity

Required for rating calculation

Unit of Measure

Required to match usage with the product's usage rate

Usage Summary Lookup (optional but required for import batching)

Groups usage records for processing

Account

Required for Billing Context

Option B is the only choice that correctly includes:

Order Product (mandatory for rating)

Start Date/Time

Quantity

Unit of Measure

Usage Summary Lookup

Account

This matches Salesforce Billing’s usage rating prerequisites.

✔ Why other options are incorrect:A – Missing Order Product IDUsage cannot be rated without knowing which subscription/order product it belongs to.

So A is invalid.

“Matching ID” and “Matching Attribute” are not standard required fields for usage rating.

Overly broad and mixes irrelevant fields.

C – Includes fields that Salesforce does not require

D – Only includes UOM + QuantityInsufficient. Missing the essential contextual fields (Order Product, Date/Time, Account).

✔ Final Confirmed AnswerB. lookup start date time, order product ID, unit of measure, quantity, usage summary lookup, account

Salesforce Billing’s Hold Billing field on Order Product works exactly as follows:

When Hold Billing = Yes, Salesforce Billing does not generate invoice lines for that Order Product.

Once the user sets Hold Billing back to No, Billing:

Calculates the missed invoice periods

Creates catch-up invoice lines so billing is not lost

Correct Behavior (per Documentation)This means:

✔ Invoicing is suspended

✔ Catch-up invoice lines are created for the entire period Hold Billing was active

Thus, C is the correct and documented behavior.

Why the other answers are incorrectOption

Description

Why Incorrect

A

Prevents invoice document generation and emails

Misleading: the function specifically stops invoice line creation for the order product; it does not manage email notifications.

B

Hold Billing auto-resets on activation

False. Hold Billing is a manual field and does not auto-clear.

D

Only invoices after Hold Billing is set to No are created

Incorrect—Billing creates catch-up invoices for missed time.

Thus, C is completely aligned with Salesforce Billing behavior.

A Revenue Cloud project often requires enhanced document capabilities beyond native Salesforce CPQ or Billing.

✔ A — Contract RedliningRequires document collaboration, versioning, and clause-level redline—not native in CPQ.

AppExchange apps like Conga, Nintex, DocuSign CLM support this.

✔ B — WatermarksNot supported natively by CPQ Quote Templates or Billing invoice templates.

Requires 3rd-party document generation.

✔ D — Electronic SignatureSalesforce does not provide native eSignature.

Common tools: DocuSign, Adobe Sign.

Why the wrong answers are incorrect:Option

Why Incorrect

C — Invoice Generation

Salesforce Billing does generate invoices natively.

E — Attachments

Salesforce Files/Attachments are natively supported; no AppExchange needed.