✅ Explanation

This scenario clearly describes a field technician performing manual steps and needing to provide information back to the Order Management system (such as identifying installed equipment).

In Salesforce Communications Cloud / Industries OM, the correct pattern is:

✔ Manual Task + OmniScript

Manual Tasks are used when human intervention is required during order orchestration.

OmniScripts provide a guided, step-by-step user experience for technicians to:

- Capture equipment identifiers
- Validate inputs
- Submit data back to Order Management

OmniScripts integrate seamlessly with:

- DataRaptors (for read/write)
- Integration Procedures (if orchestration is needed behind the scenes)

This is the recommended Salesforce pattern for technician-led fulfillment activities.

❌ Why the other options are incorrect

B. Use Integration Procedures
❌ Integration Procedures are for system-to-system orchestration, not for user-driven workflows.
They do not provide a UI for technicians to interact with.

C. Use DataRaptor and introduce manual tasks
❌ DataRaptors are data utilities only (extract, load, transform).
They cannot guide users or replace OmniScripts for step-based workflows.

D. Use callouts to fully automate the flow
❌ The scenario explicitly states that technicians must perform manual steps.
Automation alone cannot capture physical actions like identifying installed equipment.

Reference
Salesforce Industries – Order Management & OmniStudio
Manual Tasks are designed for human interaction
OmniScripts provide guided experiences for technicians and agents
Integration Procedures and DataRaptors support automation but do not replace user interaction

🧠 Exam Tip
If the question mentions:

- Technician
- Manual steps
- User input
- Providing information back to OM

👉 The answer is almost always: Manual Task + OmniScript

Explanation:

Why?
Calculation Matrices are the standard, declarative way to implement attribute-based pricing in Industries CPQ.

By adding the delivery zip code as a header attribute in the matrix, the system can look up the correct tax rate based on location.

This approach ensures:
- Declarative configuration (no custom code).
- High performance because calculation matrices are optimized for CPQ pricing.
- Flexibility to adjust tax rates by zip code without impacting cart performance.

The total price (recurring charge + tax) is then displayed seamlessly in the CPQ cart.

Why Not the Others

B. Configure tax rate in the price plan → Price plans handle recurring/one-time charges but do not dynamically calculate tax based on zip code. Tax logic must be attribute-driven, not static.

C. Custom hook class → Possible, but introduces custom code, higher maintenance, and performance overhead. Not the “least impact” solution.

D. Pricing plan step with Apex class → Similar to C, this requires custom Apex logic. It’s heavier and less performant compared to declarative calculation matrices.

Conclusion
The best solution with minimal performance impact is:
A. Add the delivery zip code customer field as a header in the pricing calculation matrix
This leverages Industries CPQ’s native attribute-based pricing capabilities, avoids custom code, and ensures efficient tax calculation by zip code.

📖 References
Salesforce Industries CPQ – Calculation Matrices
Salesforce Industries CPQ – Attribute-Based Pricing

Explanation:

Why C is Correct:
Harmonizing business processes to align with Communications Cloud's out-of-the-box capabilities reduces dependency on customizations. By simplifying and standardizing operational logic to fit the platform’s native models (e.g., using standard EPC, OM orchestration, CPQ rules), UT can lower maintenance overhead and leverage Salesforce’s upgrade-safe features, directly cutting operational costs.

Why D is Correct:
A key benefit of adopting Communications Cloud is application consolidation. Assessing the architecture to identify and decommission redundant legacy applications eliminates their associated licensing, maintenance, and integration costs. This simplifies the IT landscape and aligns with the goal of reducing total cost of ownership.

Why A is Incorrect:
Replicating legacy customizations in Communications Cloud would perpetuate the same complexity and high maintenance costs, defeating the purpose of adopting a standardized platform. This approach misses the opportunity to simplify and leverage native functionality.

Why B is Incorrect:
Manual handling of complex processes increases operational labor costs, introduces human error, and negates the automation benefits of Communications Cloud. This would raise—not reduce—operational costs and is antithetical to digital transformation.

Reference:
Salesforce Communications Cloud Value Realization and Implementation Best Practices emphasize business process harmonization and legacy system retirement as primary strategies to reduce complexity, minimize customizations, and achieve lower operational costs.

Explanation:

✅ A. Keep the number of attributes on the product low, avoid big picklists and direct assignments

Why this is correct
In Communications Cloud CPQ, every attribute, picklist value, and direct assignment increases:

- Cart evaluation time
- Rule execution complexity
- Payload size passed to Order Management

Large picklists and excessive attributes significantly degrade cart performance, especially in large enterprise B2B carts with many line items.

Salesforce best practices recommend:

- Keeping attributes lean and purpose-driven
- Avoiding large static picklists when possible
- Using attributes only when truly required for pricing, eligibility, or decomposition

This directly improves cart load time, rule evaluation, and order submission performance.

✅ C. Avoid deep product hierarchy and large numbers of add-ons; limit advanced rules (Auto-Add / Auto-Remove)

Why this is correct
Deep hierarchies and complex dependency rules (Auto-Add / Auto-Remove):

- Increase rule execution complexity
- Trigger recursive evaluations during cart operations
- Significantly slow down large enterprise carts

Salesforce recommends:

- Keeping hierarchies shallow
- Reducing dependency rules
- Avoiding excessive auto-add/remove logic when possible

This is especially critical in high-volume B2B scenarios, where carts can contain hundreds of items.

❌ Why the other options are incorrect

B. Use picklist attributes instead of products
This leads to:

- Loss of product-level lifecycle management
- Reduced pricing and eligibility flexibility
- Difficult maintenance and governance

Picklists should not replace product modeling.

D. Model everything flat and control cardinality using AutoAdd/AutoRemove
This is the worst-performing option:

- Creates excessive rule evaluation
- Makes carts hard to maintain
- Increases processing time exponentially

Flat models with heavy rule logic are a known performance anti-pattern.

✅ Final Answer:
A and C

Explanation:

Why A is Correct
Correct – Phased, region-prioritized chunked migration aligns with varying readiness and massive scale
With 75 million assets, a big-bang migration is extremely risky (performance issues, data quality problems, operational disruption, governor limits). Salesforce and industry best practices for large-scale telco migrations to Communications Cloud / Customer 360 strongly recommend phased/chunked migration.
Partitioning by geographical region allows respecting different operational differences and readiness timelines (e.g., migrate Region A first when ready, Region B later).
Partitioning by account type (consumer vs. business) further reduces batch sizes, enables targeted validation, and accommodates differing data models/complexity.
Prioritizing based on regional timelines ensures business continuity and aligns migration with local operational readiness, avoiding forced synchronization across all regions.
This approach:
- Minimizes risk
- Enables parallel testing/validation per chunk
- Supports incremental Customer 360 value realization
- Scales technically (e.g., via bulk API, staged loads)

Why the Other Options Are Incorrect

B – Do not migrate legacy assets and leverage external objects within Salesforce to access them
Incorrect
External Objects provide read access to legacy data but do not enable full Customer 360 capabilities (e.g., asset-based ordering, MACD, Industries OM orchestration, unified service/quoting). Real-time access adds latency, limits write-back, and prevents decommissioning legacy systems—defeating long-term transformation goals.
C – Coordinate migration readiness across regions and execute migration all at once to ensure consistency
Incorrect
A single big-bang migration for 75M assets is impractical and high-risk (downtime, errors, resource contention). Forcing all regions to align timelines ignores stated "different readiness timelines" and operational differences.
D – Migrate assets in chunks... and then prioritize high value business accounts
Incorrect
While chunking is good, prioritizing only "high value business accounts" ignores the bulk of consumer assets (likely the majority in a large telco) and does not address regional readiness differences. It risks incomplete Customer 360 views and uneven regional rollouts.

References
Salesforce Communications Cloud migration guides/Accredited Professional exam materials: Emphasize phased migration by region/account segment for large asset volumes
Telco transformation case studies (e.g., large carriers): Phased regional rollouts common due to operational and regulatory differences