Explanation:

Correct Option: 🟢 B. Action plan templates can have multiple planogram, inventory, and promotion checks
Action plan templates in Salesforce Consumer Goods Cloud allow users to define tasks like planogram checks, inventory checks, and promotion checks. These templates support multiple task types to streamline retail execution processes, ensuring field reps can perform various checks during store visits. This flexibility helps align store activities with business goals, making option B accurate.

Incorrect Options:

🔴 A. Action plan templates can have multiple orders and delivery tasks
Action plan templates focus on tasks like planogram, inventory, and promotion checks, not directly on managing orders or delivery tasks. While orders and deliveries are part of Consumer Goods Cloud, they are handled through other objects like Order or Delivery Task, not action plan templates.

🔴 C. Action plan templates are ready to use after saving
Action plan templates require additional configuration, such as assigning them to retail stores or visits, before they can be used. Simply saving the template does not make it immediately actionable for field reps, as further setup is needed.

🔴 D. Action plan templates are not extensible through Apex
Action plan templates are extensible through Apex, as Consumer Goods Cloud supports customization via Apex for advanced functionality. Developers can extend templates to meet specific business needs, making this statement incorrect.

Summary: 📝
This question tests knowledge of action plan templates in Consumer Goods Cloud, which are used to define tasks for retail store visits. The scenario involves understanding how templates support field activities like checks for planograms, inventory, and promotions, ensuring efficient store execution. Knowing their extensibility and setup requirements is key for certification.

Reference: 📚
Salesforce Help: Action Plan Templates

Explanation:
This question tests knowledge of the purpose and data focus of different pre-built Tableau CRM dashboards in CGC. A Field Sales Manager needs to analyze store-level execution metrics (KPIs like Facing, Share of Shelf, etc.) to identify underperforming locations. The correct dashboard must aggregate and visualize these specific Retail Store KPI trends at the store level.

Correct Option:

A. Store Performance Dashboard:
This dashboard is specifically designed to analyze the performance of individual retail stores. It visualizes key Retail Execution KPIs (e.g., Planogram Compliance, Out-of-Stock) over time, allowing a manager to easily spot trends, compare stores, and identify which ones have a decline in KPIs and thus need attention.

Incorrect Option:

B. Team Performance Dashboard:
This dashboard focuses on the productivity and activity metrics of the field team members or reps (e.g., visits completed, tasks per day). It is used to manage rep performance, not to diagnose store-level KPI problems.

C. Lost Visit Store Performance Dashboard:
This dashboard analyzes the impact of missed store visits (Lost Visits) on sales and KPIs. While it involves store data, its primary lens is understanding the consequence of visit coverage gaps, not providing a general analysis of all stores' KPI trends.

D. Product Performance Dashboard:
This dashboard focuses on the performance of products across stores or regions (e.g., sales velocity, distribution). It is used for brand or category management, not for assessing the execution health of specific retail store locations.

Reference:
The Consumer Goods Cloud Tableau CRM dashboard descriptions identify the Store Performance Dashboard as the tool for managers to monitor and compare store-level execution metrics and compliance over time, directly fulfilling the need to identify stores with declining KPIs.

Explanation:
For a modern, multi-channel project involving both user experience (UX) and back-end integration (API and Inventory System), a parallel development approach is critical for speed. The UX design team and the integration team can work concurrently. The UX team needs the API specifications (endpoints, data structure, expected response times) to be defined so they can design the user interface components (e.g., loading spinners, error messages, fields for device selection) that interact with those APIs, but they don't need the integration implementation to be complete.

✅ Correct Option:

D. Plan for three user stories running in parallel: UX Design, Device Reservation API, and Inventory System Integration. UX only requires the API information to be complete.
Parallelism: Running the three distinct work streams (UX Design, API Definition, and Inventory Integration) simultaneously significantly reduces the overall time-to-market compared to a sequential approach.

Decoupling: The UX team needs the contract (the information) of the Device Reservation API (i.e., the data model and endpoints), not the fully built back-end integration itself. They can design and build the front-end components, often using mock data, based on the API specification.

Efficiency: This is the standard Agile approach for complex projects, ensuring all parts of the solution are developed efficiently and integrated in later sprints.

❌ Incorrect Options:

A. Knowing the exact data exchanged in integration is an input to the UX design. Detailed design of the integration step is required before UX design can start.
This approach is sequential and slow. UX only requires the API specification (the contract), not the detailed implementation of the Inventory System Integration. Waiting for the full integration design will unnecessarily delay the UX work.

B. UX experience is the most important. Fully design and validate the UX before designing the integration step.
This is inefficient and risky. The integration capabilities and data model are a hard constraint on the UX. Designing the UX in a vacuum without knowing what data the APIs can provide or how long they will take to respond can lead to designs that are technically unfeasible, requiring costly rework later.

C. Plan for three user stories running sequentially: UX Design first, Device Reservation API second, and Inventory System Integration last.
This is a waterfall/sequential approach which sacrifices time-to-market. While logically ordered, it is not the optimal development strategy. The API and Integration work should start alongside the UX work to maximize efficiency.

📖 Reference:
Agile Software Development and Systems Integration Best Practices: Principles of parallel development, API-first design, and defining interface contracts early to enable simultaneous work on front-end (UX/UI) and back-end (integration/API) systems.

Explanation:
A Tier-1 telco with 20M subscribers cannot afford any downtime or order processing interruption during migration. The only viable strategy is a phased, hybrid approach that keeps the legacy system available for any non-migrated accounts while progressively migrating data in the background and supporting on-demand (just-in-time) migration when an order is placed for a yet-unmigrated subscriber.

Correct Option:

D – Migrate data on-demand as orders are raised through the Salesforce interface and implement a bulk migration strategy.
This is the standard and proven Communications Cloud migration pattern for large carriers (sometimes called “stratal migration” or “lazy + bulk migration”). Bulk ETL jobs migrate accounts in waves over months, while an on-demand service (usually via Enterprise Integration Patterns or a fallback middleware) instantly pulls and converts any non-migrated account from legacy into Communications Cloud the moment an order touches it. This guarantees zero order disruption.

Incorrect Option:

A – Disable the production system during off peak hours…
Impossible for a 20M-subscriber telco; even off-peak downtime is unacceptable and would break SLAs.

B – Ensure that both the new and old system are online during peak hours.
Simply keeping both systems online does nothing without an orchestrated on-demand fallback mechanism; orders would fail for non-migrated accounts.

C – Partition the data into logical blocks… allowing for on-demand migration and direct requests of non-migrated data to the legacy system.
This is very close but incomplete. It describes staged migration correctly but misses the critical “on-demand pull when an order is placed” trigger, which is the core of option D.

E – Partition the data into logical blocks… while the staged migration occurs.
This only describes phased bulk migration without the mandatory on-demand fallback for orders touching non-migrated accounts, so orders would still fail or be delayed.

Reference:
Salesforce Communications Cloud Launch Guide → “Large-Scale Data Migration Strategies”

Vlocity/Communications Cloud Best Practices → “Stratal Migration (Bulk + On-Demand)”

Explanation:
In Consumer Goods Cloud, when a Custom Task includes KPIs (defined via Retail Visit KPI Definition records), the actual values entered by the field rep during the visit are stored directly in Retail Visit KPI records. These records are child objects of the Visit and are automatically created when the Custom Task is completed. This allows KPI results to roll up to dashboards, be used in action plans, and support performance tracking at the visit level.

Correct Option:

B. In the Retail Visit KPI record
Retail Visit KPI is the standard object that holds the actual KPI values captured during a visit for both standard and custom tasks.

Each completed Custom Task KPI generates one or more Retail Visit KPI records linked to the specific Visit.

These records power Tableau CRM dashboards, visit scoring, and compliance reporting.

Incorrect Options:

A. In the custom object.
The custom object only defines the task structure; actual KPI results are never stored there.

C. In the Retail Store KPI record
Retail Store KPI records hold aggregated or target values at the store level, not individual visit actuals.

D. In the Visit Record
The Visit record itself does not have fields to store individual KPI actuals; it only has roll-up summary fields (if configured).

Reference:
Salesforce Help: “Custom Tasks and KPIs in Consumer Goods Cloud” → Retail Visit KPI storage

Trailhead: “Define and Measure Retail Visit KPIs” – Data model diagram

CG Cloud Object Reference (API v61.0+): Retail Visit KPI object as child of Visit and container for actual KPI values