ABC Telecom uses Communications Cloud while its distributors use their own CRM system. ABC Telecom wants to share product catalog information, including technical descriptions of products from ABC Telecom's Communications Cloud. Distributors can then use this information to set up their own CRM product catalog.
What should a Consultant suggest as a starting point for this integration?
In Communications Cloud, the single source of truth for commercial and technical products is the Enterprise Product Catalog (EPC). For external systems---like distributors' CRMs---to consume product specifications, offerings, attributes, technical details, and bundled components, Salesforce provides EPC REST APIs.
These APIs expose:
Product Offerings
Product Specifications
Commercial & technical attributes
Prices (optional depending on configuration)
Relationships and hierarchies
They are designed explicitly for external catalog synchronization, making them the ideal starting point for distributors to pull up-to-date product definitions.
Why others are incorrect:
A (Product2 APIs): Product2 is not used for Communications Cloud catalog; EPC uses Vlocity EPC objects.
B (TMF620): Salesforce EPC is not natively TMF620 compliant. TMF620 requires a mediation layer; using EPC APIs directly is the recommended starting point.
D (getCartProducts): CPQ APIs require a cart context and do not expose full catalog specs.
ABC Telecom wants to enable Experience Cloud for their partners. They want Communications Cloud to communicate with external systems during an order capture journey for their partners. Users should go through a guided journey and connect with an external system seamlessly.
Which two features must a Consultant use to meet their needs?
For partner-facing guided journeys in Experience Cloud that must communicate with external systems during order capture, Salesforce recommends using OmniScripts and Integration Procedures together.
OmniScripts (A) provide the guided user journey---highly configurable, step-by-step flows where partners can configure products, enter customer data, and trigger backend processes. OmniScripts are the front-end orchestration layers for Communications Cloud CPQ and order capture in portals.
Integration Procedures (C) are the server-side execution engine that handle:
Calling external systems
Orchestrating multiple APIs
Handling transformations
Reducing client-server chattiness
They are specifically optimized for Experience Cloud, where minimizing round trips and improving performance is critical.
DataRaptors (B) handle simple CRUD and transformations but are not well suited for multi-step external integrations. FlexCards (D) are for display/UI components, not guided journeys or external API orchestration.
Universal Containers wants to include product A every time they sell bundle B. Users can opt out this product if they want but cannot take a quantity of more than 1 per bundle.
How should a Consultant configure the product in the system?
The requirement is:
Product A should be included by default (default=1)
User can remove it (Min=0)
They cannot increase quantity beyond 1 (Max=1)
This exactly aligns with cardinality settings:
Min = 0 (optional)
Max = 1 (only one allowed)
Default = 1 (pre-included)
Auto Add (A) does not allow opt-out. Recommend Rule (C) only suggests the product --- does not auto-include.
For an Enterprise Sales Management quoting journey for fixed-line products for an enterprise customer, United Telecom needs to have a feasibility check for the requested product for desired locations.
Which of the following features can meet the requirement?
Enterprise Sales Management (ESM) for B2B telecom includes Location-Based Feasibility (LBF), which checks whether a product (e.g., fiber, Ethernet access, MPLS, DIA) is technically feasible at a given customer location or site. This is a standard requirement in enterprise fixed-line quoting.
LBF provides:
Real-time or batch feasibility lookup
Integration with GIS, network inventory, or legacy feasibility engines
Support for multi-site enterprise quoting
Feasibility responses (yes/no/conditional)
Auto-blocking non-feasible service requests
Location-Based Serviceability (A) is used in B2C broadband/mass-market sales, not complex enterprise quoting. Product Availability (C) and Eligibility Rules (D) control catalog eligibility, pricing, or contract conditions, not technical feasibility.
A consultant for Northern Trail Outfitters (NTO) retail stores would like to configure inventory checks related to product, that are stocked in the frozen food aisle. What should the consultant do first to ensure the field rep knows that the product is located in the frozen food aisle?
To ensure the field rep knows that the product is located in the frozen food aisle when performing an inventory check, the consultant should create an In-Store Location called Frozen Food Aisle'. An In-Store Location is an object that represents a specific area within a retail store, such as an aisle, a shelf, or a cooler. By creating an In-Store Location for the frozen food aisle, the consultant can associate it with the products that are stocked in that area and display it on the inventory check task. This way, the field rep can easily locate and verify the products in the frozen food aisle. Verified Reference: [Salesforce Consumer Goods Cloud Implementation Guide], page 20.
Fletcher
1 day agoIsabelle
9 days agoLina
16 days agoPamella
23 days agoIvette
1 month agoJenise
1 month agoJuliann
2 months agoEdison
2 months agoTerrilyn
2 months agoAlisha
2 months agoSalome
3 months agoJovita
3 months agoGayla
3 months agoPortia
3 months agoMarcelle
4 months agoNan
4 months agoRikki
4 months agoAndrew
4 months agoEnola
5 months agoAshleigh
5 months agoKaycee
5 months agoDolores
5 months agoAja
6 months agoAn
6 months agoLauna
6 months agoRobt
6 months agoHolley
6 months agoDerick
7 months agoSimona
7 months agoSylvia
7 months agoLorean
9 months agoWenona
9 months agoKrissy
9 months agoOra
10 months agoGianna
10 months agoDelila
11 months agoCornell
11 months agoCharlie
12 months agoLennie
1 year agoPaul
1 year agoGussie
1 year agoFrancisca
1 year agoCandra
1 year agoValda
1 year agoKris
1 year agoLawanda
1 year agoFlorencia
1 year agoLorrie
1 year agoWalton
1 year agoYolando
1 year agoLetha
1 year agoBulah
1 year agoGerman
1 year agoDenny
1 year agoLashawnda
1 year agoHelene
1 year agoSherita
1 year agoNorah
1 year agoValentine
1 year agoRossana
1 year agoSabra
1 year agoLaila
1 year agoLouvenia
1 year agoLettie
2 years agoMaryanne
2 years agoJoye
2 years agoDona
2 years agoJennifer
2 years agoLucy
2 years agoShawna
2 years agoJesus
2 years agoPaola
2 years agoEric
2 years agoAnabel
2 years agoViola
2 years agoRaul
2 years agoIndia
2 years ago