Free Salesforce AP-223 Practice Exam with Questions & Answers | Set: 2

Scenario:

A payment is posted on the wrong Account

It must be applied to an invoice on a different Account

Payment is already posted

Salesforce Billing rules:

A posted payment cannot be reparented

A payment allocated to an invoice cannot simply be moved

Correct process is:

✔ B — If allocated, create a refund, then create a new payment on the correct accountDetailed steps:

Reverse (refund) the incorrect payment

Create a new payment on the correct account

Allocate that payment to the correct invoice

This ensures:

Proper audit trail

Compliance with financial controls

Correct ledger entries

Why the other options are wrongOption

Why Incorrect

A. Allocate payment to Account B invoice

Not allowed: payment is tied to Account A.

C. Reparent payment to Account B

Posted payments cannot be reparented.

D. Cancel the payment

Cancelling alone does not reverse ledger impact; refund process is required.

Thus B is correct.

Requirement:

Product may be taxable or tax-exempt depending on a custom field (Industry).

In Salesforce Billing:

Tax rules determine whether a product line is taxable or exempt.

Tax rules can be driven by custom logic using:

Custom fields

Flow

Apex

Determination scripts

Therefore:

✔ C. Use automation to set the Tax Rule based on the custom field.Why not the others?Option

Why Incorrect

A. Tax Treatment

Outputs tax result, but the rule determining taxability is the Tax Rule, not Tax Treatment.

B. Billing Rule

Controls invoice schedule, NOT taxability.

D. Revenue Recognition Rule

Controls revenue, not tax.

Thus C is the only valid solution.

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

Universal Containers wants:

ARR__c on Opportunity Line Item (Opportunity Product)

But ARR is currently on SBQQ__QuoteLine__c

They want ARR captured in pipeline reports without adding automation.

Salesforce CPQ Behavior:During Quote → Opportunity sync, CPQ automatically maps fields only if:

The same API name exists on both objects

The field types match

The field-level security is correct

If these conditions are met, CPQ automatically handles field synchronization.

Therefore:

✔ C. Create ARR__c on Opportunity Line Item with matching field configurationThis leverages native CPQ field mapping, requires zero automation, and is the recommended Salesforce approach.

Why the other options are incorrect:Option

Why Incorrect

A. Price Rule to copy value

Price rules do not run on Opportunity Products; rules run only on Quote Line Editor.

B. Flow

Extra overhead and maintenance—unnecessary when CPQ already supports native field sync.

D. Cross-object formula

Opportunity Line Item cannot reference Quote Line fields (different object trees). Salesforce prevents this.

Thus, C is the only correct and efficient solution.

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.

The requirement is:

When configuring a bundle, if the customer has previously purchased a hardware firewall, the Hardware Firewall product option should be hidden during bundle configuration.

This means the Product Rule must evaluate immediately when the bundle configuration UI loads, so that the option is hidden before the user begins configuring.

Salesforce CPQ documentation clarifies the evaluation events for Product Rules:

Evaluation Events in CPQ Product RulesEvaluation Event

When it Fires

Use Case

Load

Fires immediately when the configurator opens

Use this when hiding options or preselecting options based on external or historical data, Assets, Subscriptions, etc.

Load and Edit

Fires on initial load and every time the user makes changes

Use when rules may need re-checking with every MODIFY step.

Save

Only fires when clicking Save

Use when validating configuration before saving (e.g., preventing invalid combinations).

Always

Fires during all events including load, edit, and save

Rarely used; typically only for enforcement rules.

You need the option hidden right when the configurator loads.

The rule uses historical data (previously purchased hardware firewall).That data does not change in real time during the configuration session.

There is no need to re-check during every selection or on save.

Why Load is the correct answer:Therefore, using Load provides:

Optimal performance

Immediate user experience consistency

No unnecessary re-evaluations

Overkill; runs multiple times unnecessarily.

Negative impact on performance in large quotes/bundles.

Why the other options are incorrect:❌ A. Always

Hiding an option at save time is too late.

The user should not see the firewall option at all if they already purchased it.

❌ B. Save

This re-evaluates the product rule every time the user interacts.

Not required because the “past purchase” condition does not change during configuration.

Adds unnecessary processing.

❌ C. Load and Edit

The user story states that sales users should inherit previously negotiated pricing when quoting for existing customers.

In Salesforce CPQ, the object that stores account-specific negotiated prices is:

Contracted Pricing (SBQQ__ContractedPrice__c)

This object overrides standard list prices during quoting based on:

Account

Product

Pricebook

Contract linkage

Therefore, in addition to migrating Accounts, Contracts, and Quotes, the missing legacy pricing data must be loaded into Contracted Pricing.

The consultant discovers:

Multiple triggers

Workflows

Flows

Possibly recursion or conflicting automations… on the Opportunity, which is foundational for CPQ.

Salesforce Revenue Cloud Best Practice:Use one automation type (preferably Flow) to avoid conflicts, recursion, performance issues, and unpredictable ordering.

Too many automation types cause issues with:

CPQ Quote Sync

Opportunity → Quote event handling

Performance and CPU limits

Unpredictable execution order

Therefore:

✔ A — Recommend using a single automation type for best performanceThis aligns with:

Salesforce Well-Architected Framework

Salesforce CPQ implementation guidelines

General platform automation best practices

Why other options are incorrect:Option

Why Not Correct

B

Large Quote Threshold affects calculator performance, not Opportunity automation.

C

Multiple automation types is the problem, not the solution.

D

Accepting the current messy automation is not recommended before CPQ implementation.

Thus A is correct.