Salesforce AP-223 Exam Questions in PDF and Online

QUESTION: 1

You are implementing the Design Document for a large Enterprise Revenue Cloud project having multiple lookup price rules supporting a complex pricing requirement in the Build phase. During construction the customer discovers additional logic and external data stores that need to be incorporated in order to achieve the correct pricing in a particular set of use cases. You estimate the lookup price rules will need to be modified, additional rules will need to be created and API development will be needed. As an Implementation consultant what is the appropriate course of action that should take in this predicament?

Communication to the customer ongoing adjustment can be made as long as we're in the build phase.
Implement the lookup price rules immediately then review with the solution Architect.
Communicate these changes to the project manager who will evaluate the impact to scope, timeline and budget them determine the next course of action
Consult with the solution Architect first who will expedite the updates to the design documents, then implement the changes immediately.
Gather more details, if it requires a low level of effort then implement immediately before starting the next sprint. Otherwise Complete on the subsequent sprint.

Answer(s): C

Explanation:

For a large Enterprise Revenue Cloud (Salesforce CPQ + Billing) implementation, the key themes in all Salesforce delivery guidance and project best practices are:

Governance and change control

Design-first, then build

Raising scope-impacting changes through the Project Manager

Architect accountability for solution integrity, PM accountability for scope/timeline/budget

Let's walk through why C is correct and why the other options conflict with typical Salesforce CPQ/Billing implementation best practices.

1. Context of the ScenarioYou are in the Build phase and:

You already have a design with:

Multiple Lookup Price Rules implementing complex pricing.

New information emerges:

Additional pricing logic

External data stores that must be incorporated

Need to modify existing lookup rules

Need to create additional rules

Need API development (integration work)

This is not a cosmetic tweak; it is:

Scope-impacting (new integration/API work, new logic)

Design-impacting (pricing architecture changes)

Potentially timeline and budget impacting

Therefore, this triggers formal change control.

2.
Why Option C is CorrectC. Communicate these changes to the project manager who will evaluate the impact to scope, timeline and budget then determine the next course of action

This aligns with standard Salesforce implementation and project governance principles:

Any change that affects scope, complexity, or integration must be raised to the Project Manager (PM)

Project Manager is responsible for:

Scope management

Timeline & milestones

Budget & resourcing

Managing change requests and stakeholder approvals

The PM will:

Evaluate impact with:

Solution Architect (for technical/design impact)

Tech leads / Dev leads (for effort estimation)

Decide:

Whether a Change Request (CR) is needed

How to re-prioritize sprints, adjust backlog

Whether additional budget / time is required

How to communicate to customer stakeholders

This preserves:

Design integrity (Architect still evaluated the solution)

Project discipline (PM governs scope/timeline/budget)

Traceability and documentation (updated design docs, backlog, CRs)

This is exactly how a large enterprise Revenue Cloud (CPQ + Billing) program is expected to run.

3.
Why the Other Options Are Not AppropriateA. "Adjust as long as we're in build phase"A.

Communication to the customer ongoing adjustment can be made as long as we're in the build phase.

Problems:

Implies uncontrolled scope creep:

"As long as we're in build, we can just keep adjusting."

No mention of:

Impact to scope, timeline, budget

Formal change control

Involvement of PM or Architect

In a complex CPQ/Billing implementation, this would:

Break governance

Risk missed deadlines and budget overruns

Create misaligned expectations with the customer

So A contradicts standard methodology and enterprise delivery practices.

B . "Implement then review with the Solution Architect"B. Implement the lookup price rules immediately then review with the solution Architect.

Problems:

Sequence is wrong:

You never build first and ask the Architect later on large-scale pricing and integration changes.

This can cause:

Misalignment with overall pricing architecture

Conflicts with other CPQ/Billing components (e.g., Amendments, Renewals, Billing logic)

Rework if the Architect has a different approach

Still no mention of PM or scope/timeline/budget impact.

This violates both design governance and project governance.

D . "Architect then immediate implementation (no PM)"D. Consult with the solution Architect first who will expedite the updates to the design documents, then implement the changes immediately.

This is closer, but still incomplete:

Good:

You involve the Solution Architect.

You talk about updating design documents.

But:

No involvement of the Project Manager.

No consideration of:

Impact to scope

Impact to timeline

Impact to budget

For "large Enterprise Revenue Cloud" projects, Architect PM:

Architect owns technical solution integrity

PM owns project plan, change control, stakeholder approvals

So D ignores formal change management which is critical at enterprise scale.

E . "If low effort, just do it; else next sprint"E. Gather more details, if it requires a low level of effort then implement immediately before starting the next sprint. Otherwise complete on the subsequent sprint.

Problems:

Consultant is unilaterally deciding based on "low effort":

No PM.

No formal scope/time/budget impact evaluation.

This might be okay for minor cosmetic or non-functional changes in a small project, but:

Here we have:

Complex pricing

Multiple lookup price rules

External data store integrations

API development

This is never "just low effort".

For a large enterprise Revenue Cloud implementation:

This bypasses governance, change control, and approvals.

So E promotes ad hoc scope changes, which is against standard practice.

4. How This Ties Back to Salesforce CPQ & Billing Best PracticesIn Salesforce CPQ and Billing implementations, especially when dealing with complex pricing logic and external integrations:

Complex Pricing (Lookup Price Rules):

Changes can affect:

Quote calculation performance

Sequential dependencies with Price Rules, Discount Schedules, QCP, Billing logic

May cause downstream issues in:

Orders, Invoices, Revenue Schedules, Amendments, Renewals

External Data Stores & API Development:

Introduces:

New integration patterns

Error handling, retries, timeouts

Security and governance requirements

Impacts:

Technical design

Test strategy (SIT, UAT, performance testing)

Possibly non-functional requirements

Because of that, Salesforce project documentation and implementation guidance emphasize:

Raising such changes via Project Manager

Having the Solution Architect assess and update:

Solution design

Integration architecture

Managing it formally as a change request if it affects:

Scope

Timeline

Budget

This is exactly what Option C describes at the right level of responsibility.

Reveal Solution Next Question

QUESTION: 2

Universal Containers has recently implemented and released CPQ to users in their production environment. After an extensive testing Cycle in a sandboxed environment. One of the automations implemented was to set every new quote created as "primary" at the time of creation in order to save clicks. Users immediately began to report errors when trying to create quotes in the production environment for the first time.
What could have caused this issue?

The User did not execute post-installation scripts upon their first login to CPQ.
The User did not have the proper access to the Opportunity Product object.
The User did not have the proper access to the Quote Line object.
The User did not have the proper access to the Quote Object.

Answer(s): A

Explanation:

When a Salesforce CPQ user logs into production for the first time, CPQ requires running the Post- Install Script. This script:

Creates default settings

Ensures CPQ-managed fields are initialized

Grants required permissions

Creates default Primary Quote logic metadata

Updates field values such as IsPrimary, quote calculation settings, etc.

Why the issue happenedThe customer implemented automation that automatically sets a new quote as Primary at creation.

If a user has not executed the CPQ Post-Install Script on their first login, then Salesforce CPQ has not yet initialized several objects and fields that are required for the Primary Quote creation process.

Therefore, the "first time users tried to create quotes" they encountered errors, because:

Their user-specific CPQ installation metadata was not initialized

CPQ could not run its internal logic that depends on Primary Quote setup

Salesforce's installation documentation explicitly states:

Each CPQ user must run the Post-Install Script after first login, or they may encounter errors when creating quotes, setting a quote primary, or performing calculations.

Thus the correct answer is A, and it is consistent with CPQ installation best practices.

Reveal Solution Next Question

QUESTION: 3

Universal Containers sell a product bundle named "Corporate IT Solutions". One of the product options inside this bundle is named Hardware Firewall Universal Containers has a requirement where if the customer has purchased a hardware firewall in the past, the hardware firewall product option should be hidden while configuring the bundle.

The CPQ admin has created a product rule to handle this requirement.
What should the evaluation event of the product rule be set to?

Always
Save
Load and Edit
Load.

Answer(s): D

Explanation:

Scenario SummaryUniversal Containers sells a bundle "Corporate IT Solutions."

Inside it is a product option: Hardware Firewall.

Requirement:

If the customer previously purchased that Hardware Firewall (historical purchase),

Then hide the product option inside the bundle during configuration.

This is a Configuration Rule

Using Selection/Filter logic to hide options

The rule must trigger as soon as the bundle loads, because the product option must be hidden before the user interacts with the bundle.

What type of Product Rule?Which Evaluation Event is Correct?Salesforce CPQ Product Rule Evaluation Events:

Event

When it Fires

Typical Use

Load

When the configuration page loads the first time

Hide/show options, preselect options, set initial values

Edit

On any user modification

Rerun rules based on changes

Load and Edit

Both events above

When both initial setup and change handling are required

Save

When the quote line editor is saved

Validation rules that block save

We need the product option to be hidden immediately when configuring the bundle.

It is not dependent on user edits.

It uses historical purchase data (Opportunity Product / Asset / Subscriptions).

In this requirementTherefore, the rule should fire at initial load only, not waiting for user interaction.

Always not a valid Product Rule Event type in CPQ.

Save too late; user would see the option before it's hidden.

Load and Edit unnecessary; we do not need edits to trigger this rule.

Edit would fail because hiding must occur before user interaction.

Why Not the Others?Salesforce CPQ Documentation AlignmentCPQ Product Rules documentation states:

Use Load when you want the rule to evaluate immediately when the configurator opens, typically for hiding, filtering, or preselecting options.

This matches the required behavior perfectly.

Reveal Solution Next Question

QUESTION: 4

Should Bundles be a scoping topic of discussion as part of a CPQ project?

Yes, bundle configuration is a necessary part of CPQ and it should always be implemented.
Yes, bundle Configuration should be introduced and it's up to the customer to decide whether they need it or not.
No, if the customer is not using bundle configuration currently, they won't need it in the future.
No, it is safe to assume that the customer doesn't need bundle configuration unless it's brought up specifically.

Answer(s): B

Explanation:

In every Salesforce CPQ implementation, Product Bundles are one of the core configuration capabilities that must be discussed during scoping and discovery--even if the customer does not initially think they need them.

Why the correct answer is BB. Yes, bundle configuration should be introduced and it's up to the customer to decide whether they need it or not.

This aligns fully with Salesforce CPQ implementation best practices, discovery methodology, and the guidance in CPQ documentation and study resources.

Why bundles must be discussed in scopingSalesforce CPQ Bundles are used to solve many common quoting problems:

Grouping products together

Managing optional/required components

Handling feature selections

Automating inclusion, exclusion, or quantity logic

Supporting configuration rules

Ensuring sales reps configure solutions correctly

Improving quote accuracy

Providing guided selling experiences

Because bundles fundamentally shape:

Product catalog architecture

Pricing structure

Rules design

Quote line generation

Amendment/Renewal behavior

Order + Billing outputs

...they must be addressed early during discovery and scoping to avoid major redesign later.

Salesforce implementation playbooks emphasize:

Introduce all CPQ capabilities during discovery.

Allow the customer to confirm whether a capability meets their use cases.

Document decisions in the solution design before build.

Therefore, bundles should always be a topic of discussion, but the customer chooses whether they need them based on business requirements.

Why the other options are incorrectA. "Bundle configuration is necessary and should always be implemented."Incorrect because:

Not all customers need bundles.

Some catalogs are simple, flat, or priced per unit with no component logic.

Salesforce CPQ documentation does not state bundles are mandatory.

C . "If they don't use bundles now, they won't need them later."Incorrect because:

Customers often evolve pricing and product strategies.

Many legacy quoting tools do not support bundles, so current-state future-state.

CPQ discovery must capture future-state needs.

D . "Assume no bundle configuration unless customer brings it up."Incorrect because:

Customers often don't know what CPQ bundles can do.

CPQ consultants are responsible for educating customers on capabilities.

Failing to introduce bundles leads to:

Incorrect product catalog design

Broken pricing logic

Large rework later in the project

This contradicts CPQ best-practice discovery methodology.

Reveal Solution Next Question

QUESTION: 5

How does Hold Billing work?

It Prevents invoice document generation and stops email notifications from going out to the customer.
The Hold Billing field is set to "yes" until the order is activated. Upon order activation the field will be automatically set to "no".
It suspends invoicing for that order product until the field is set to "no". Invoices lines will be created to account for the time when hold billing was set to "yes"
It suspends invoicing for that order product until the field is set to "no". Invoices lines will be created only for invoices after hold billing was set to "yes".

Answer(s): C

Explanation:

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.

Reveal Solution Next Question

QUESTION: 6

How can a Revenue Cloud Consultant create a new payment Method for a credit card that will be saved for future Payments?

Enter the credit card details into a new payment Method record Click the Tokenize button
From the Payment credit cards related list, click the new credit card button.
Enter the credit card details into a new payment method record. salesforce users should use platform encryption for PCI Compliance.
From the Account, Payment Method related list, then click the new Payment Method Credit Card button.

Answer(s): D

Explanation:

To save a new credit card Payment Method for future payments, the correct Salesforce Billing process is:

Correct documented methodFrom the Account Page:

Go to the Payment Methods related list

Click New Payment Method Credit Card

Enter card details

Card is tokenized (via Payment Gateway)

Saved for future payments

This is exactly what option D describes.

Why the other answers are incorrectOption

Why Incorrect

A . Tokenize button

Outdated UI/legacy workflow; new UI and gateways tokenize automatically.

B . Payment credit cards related list

Not the standard Billing object structure; Salesforce Billing uses Payment Method object, not "Payment Credit Card".

C . Enter card details + encryption

PCI does not allow storing full credit card numbers in Salesforce even with Platform Encryption --

credit cards must be tokenized via gateway, not stored directly.

Therefore:

The only correct Salesforce Billing approach is D.

Reveal Solution Next Question

QUESTION: 7

A Revenue Cloud customer has posted an invoice and now wants to add on more items from another order associated to that account. Without using invoice batches, how can this be accomplished?

Credit the invoice, add the new order and run an invoice scheduler to pick all the orders up.
use bill now on the new order and reparent the new invoice lines to the existing invoice C . Cancel and Rebill the invoice, add the new Order and run an invoice scheduler to pick all the order up.
Use bill now on the new Order and consolidate the invoices.

Answer(s): C

Reveal Solution Next Question

QUESTION: 8

What are three risks when using too many cross object formula fields in a Revenue Cloud Project?

Formula field data is not always available during CPQ quote calculation
Formula fields have unlimited access to object many relationships away which makes it vulnerable to data changes.
They are computationally Expensive.
They can easily exceed limits if not carefully designed and tested
Formula Fields are editable, after the calculation completes the sales user or process automation can overwrite its value

Answer(s): A,C,D

Explanation:

In Salesforce CPQ + Billing (Revenue Cloud), heavy use of cross-object formula fields can create serious performance, calculation, and reliability issues. Salesforce product documentation and CPQ study guides highlight several risks related to:

Quote calculation engine performance

SOQL query depth

Runtime evaluation limits

Data availability timing during synchronous calculations

Below is the breakdown of the options:

A . Formula field data is not always available during CPQ quote calculationCorrect.

Salesforce CPQ reads values at calculation time, but cross-object formula fields may:

Not resolve in time if they depend on parent records updated within the same transaction

Return stale values because formula evaluation is not recalculated in real time mid-calculation

Fail during QCP or price rule evaluation due to record access/state issues

This is a known risk documented in CPQ technical architecture guidance.
B . Formula fields have unlimited access to object many relationships away which makes it vulnerable to data changes.Incorrect.

Formula fields do NOT have unlimited access. They are limited to 10 relationship levels.

While data changes on parent objects can affect formula results, this is not a primary risk emphasized in Revenue Cloud implementation guidance.

Therefore, not one of the three correct risks.
C . They are computationally expensive.Correct.

Formula fields--especially cross-object ones--are recalculated at runtime every time:

The referenced record is queried

CPQ calculator reads them during price rule evaluation

Billing processes (Invoice Run, Usage Rating, etc.) reference them

This can significantly slow down:

Quote calculations

Order/Invoice generation

Any multi-object SOQL-heavy logic

This is a well-known performance risk.
D . They can easily exceed limits if not carefully designed and testedCorrect.

Cross-object formulas contribute to:

SOQL query depth limits

CPU time limits

Formula size complexity

Relationship depth limits

In CPQ/Billing, where Quote and Quote Line processing already push platform limits, too many formula fields can cause:

Calculation failures

Invoice/Order creation errors

Apex limit exceptions

Salesforce documentation warns against heavy formula usage for precisely these scalability concerns.
E . Formula fields are editable, after calculation a user/process can overwrite the valueIncorrect.

Formula fields are never editable by users or automation.

Their values are dynamically calculated from their formula expressions.

Therefore, this option is not a valid risk.

Reveal Solution Next Question

Salesforce CPQ and Billing Consultant Accredited Professional AP-223 Exam Questions in PDF

Free Salesforce AP-223 Dumps Questions (page: 1)

QUESTION: 1

Explanation:

QUESTION: 2

Explanation:

QUESTION: 3

Explanation:

QUESTION: 4

Explanation:

QUESTION: 5

Explanation:

QUESTION: 6

Explanation:

QUESTION: 7

QUESTION: 8

Explanation: