Universal Containers (UC) is a Communications Service Provider using Communications Cloud. UC markets their DSL Internet service with two speed tiers - 5 Mbps and 50 Mbps. Five Mbps uses the ADSL technology, which requires Copper Pair, and 50 Mbps uses the VDSL technology, which requires Bonded Copper Pair.
How should a Consultant model this service end-to-end?
Answer : C
In Communications Cloud, the correct end-to-end modeling pattern is:
Commercial Product DSL Internet
Attributes Speed (5 Mbps, 50 Mbps) and derived Technology (ADSL, VDSL)
Customer Facing Services (CFS): ADSL CFS, VDSL CFS
Resource Facing Services (RFS): Copper Pair, Bonded Copper Pair
Multi-level decomposition: Commercial CFS RFS
This follows the standard Salesforce service modeling approach where CFS represents logical service layers, and RFS represents physical resources required to deliver the service.
A communications company wants to improve their quote-to-order journey experience. The journey has several steps, which include selecting products and services, and integration with the inventory system for device reservation. They want to create a modern, multi-channel experience.
What approach should a Consultant take during planning to ensure optimal development and time to market?
Answer : D
In Salesforce Industries (Vlocity) project methodology, an optimal quote-to-order implementation requires parallel workstreams, especially when designing multi-channel digital experiences that rely on backend APIs such as inventory reservation or device allocation. Public Salesforce implementation practices emphasize that UX design should begin early and only needs high-level API contracts, not full backend development, to progress. This is because modern telecom journeys---product selection, service configuration, device reservation, and inventory validation---depend on microservices exposed through TMF-style APIs or custom integration layers.
Salesforce recommends decomposing work into parallel user stories to accelerate time to market:
UX Design Driven by user flows, wireframes, and component behavior
Device Reservation API Defines the interface and payload shapes
Inventory System Integration Implements backend orchestration
This approach enables the UX team to build using mocked or stubbed APIs, ensuring that design decisions aren't delayed while backend services are still being implemented. This directly aligns with option D, which reflects Salesforce's agile implementation strategy.
Options A and B incorrectly assume UX must wait for full integration design, which slows delivery. Option C suggests sequential workstreams, which Salesforce explicitly discourages due to increased cycle time.
Thus, D is the best match.
Universal Containers is using Communications Cloud for their B2B use cases. They have an integration with a legacy stack that will handle network provisioning and billing. As part of their Order Management process they have to send the customer data to the legacy app, which in turn provisions billing.
What should a Consultant recommend to make this callout easier to configure, easier to maintain, and performant?
Answer : B
In Communications Cloud, integrations performed during Order Management---especially callouts for provisioning, billing, and customer synchronization---should use the Order object as the primary integration payload source. Salesforce's public Order Management design principles specify that customer data required for external provisioning should be modeled directly on the Order when the data is stable, required frequently, and does not belong to technical products.
This approach offers:
Simple configuration (fields on Order object rather than product attributes)
High maintainability, because administrators can adjust mappings without changing product models or decomposition rules
Performance efficiency, as Order-based callouts do not require deep decomposition navigation or attribute inheritance logic
Clear separation of commercial vs. technical data, one of the core EPC principles
Options C and D introduce unnecessary complexity. Customer data does not belong on Technical Products (C) nor should it be modeled as multi-picklist cart attributes (D), as these degrade performance and complicate decomposition. A custom adapter (A) adds code and contradicts Salesforce's declarative-first approach.
A developer has modified the EPC price amount of one mobile device using the Product Designer from Communications Cloud. After the price has been changed, the developer wants to check the previous EPC price amount to track pricing metrics and get some forecast metrics.
How can the developer check the previous price amount on the mobile device?
Answer : B
To track pricing changes, Salesforce recommends enabling Field History Tracking on Price List Entry, which logs:
Old price
New price
User
Time of change
This is the simplest way to review previous pricing.
Why others are wrong:
A requires custom triggers---not recommended.
C EPC Project history tracks metadata changes, not price list values.
D Versioning is for product specifications, not PLE prices.
Which User persona manages day-to-day Retail Execution processes such as creating visits, creating tasks, and assigning visits to Field Representatives?
Answer : C
A Sales Manager is the user persona that manages day-to-day Retail Execution processes such as creating visits, creating tasks, and assigning visits to Field Representatives. A Sales Manager is responsible for planning and overseeing the retail activities of a team of field reps, as well as analyzing and reporting on the performance and compliance of the retail stores in their territory. Verified Reference: [Salesforce Consumer Goods Cloud Implementation Guide], page 18.
United Telecom (UT) has initiated high-speed offerings on Communications Cloud after upgrading its network.
Which out-of-the-box MACD process should UT consider when upgrading existing assets to high-speed offers for interested customers?
Answer : A
In Communications Cloud, modifying an existing commercial service to a higher speed tier (or upgraded variant) is handled through the Change of Plan MACD process. Salesforce defines Change of Plan as the out-of-the-box MACD scenario used when an existing active subscription is upgraded, downgraded, or migrated to a different configuration within the same offer family.
High-speed upgrades typically involve the same commercial product family (e.g., ''Internet'') but with modified attributes such as speed tier, bandwidth profile, SLA level, etc. The Change of Plan MACD:
Reuses the existing asset
Captures the new configuration
Decomposes into new or modified technical actions
Avoids unnecessary disconnect/reconnect cycles
Preserves billing continuity
Minimizes order orchestration overhead
Options B (Disconnect & New Order) and C (Modify Order) are not correct: Disconnect/New Order is used only when replacing an entire product with a materially different offering, not speed upgrades. A Modify Order MACD adjusts non-plan attributes---not plan-tier changes. Option D (Apply Promotion) is irrelevant here.
Thus, Change of Plan is the correct MACD for upgrading customers to high-speed offers.
Which methodology does Salesforce Maps offer to facilitate the addition of geocoordinates for each retail store location by an admin?
Answer : A