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

Document generation performance in CPQ depends heavily on template content size, not price rules or QLE performance.

✔ C — Use compressed image formatsLarge JPG/PNG images dramatically slow down:

Template rendering

PDF generation

Email attachment creation

Compressing images is a documented best practice.

✔ E — Reduce the number of line columns in the quote documentEach additional column:

Adds more data retrieval

Increases merge time

Slows PDF rendering

This is one of the primary causes of slow Quote Document generation in CPQ.

Why the other answers are incorrectOption

Why Wrong

A & B — Product rules / constraints

They affect quote calculation, not document generation.

D — Fields in QLE

QLE configuration does not affect document generation speed.

Thus C and E are correct.

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.

ARR__c exists on Quote Line (SBQQ__QuoteLine__c) and must appear on:

Opportunity Line Item for pipeline reporting

Salesforce CPQ automatically syncs Quote → Opportunity Line Item when:

The field exists on both objects

The Field API Name and Field Type match

This requires zero automation, no flow, no price rules.

The three customer teams that must be involved in Revenue Cloud scoping are:

✔ A — Information (Product / Pricing owners)They define product catalog rules, pricing models, and offerings.

✔ B — Technology (IT/Architecture)Ensures integration, data migration, security, and platform alignment.

✔ C — Sales OperationsOwns quoting flows, approvals, discounting, sales motions, and user experience.

These teams define core CPQ processes.

Why others aren't required at scoping:Team

Why Not Required

D — Accounting/Finance

Essential for Billing scoping, but not required for CPQ-only scoping unless Billing is in scope.

E — Customer Service

Usually relevant for Service Cloud and CALM, not initial CPQ scoping.

F — Human Resources

Irrelevant to CPQ and Billing.

Thus A, B, C is correct.

These three patterns negatively impact Revenue Cloud scalability and performance:

✔ A — Multiple automation types on a single objectTriggers + Workflows + Flows create:

CPU limit issues

Debug complexity

Recursion

Unpredictable execution order

This is a major anti-pattern.

✔ B — External API calls during pricing sequenceQCP or Price Rules must never call external APIs because:

They block calculator execution

Cause timeouts

Dramatically slow down quote save time

This is a severe performance issue.

✔ C — Extensive custom fields on Quote LineEvery Quote Line field:

Increases calculation payload size

Increases JSON transmitted to the calculator

Slows down Quote Calculation

Impacts large quotes significantly

Why D and E are not performance design flawsOption

Why Not a Design Problem

D — Quotes with 200 lines

CPQ supports scaling to far more than 200 lines with proper configuration.

E — Invoices with 200 lines

Billing handles this volume normally. Performance issues arise at thousands of lines.