Choosing the right Power Platform component

PL-600 · Perform solution envisioning and requirement analysis · Updated

The exam gives a business story and asks for one component. You win these by knowing what each component is for and by defaulting to the simplest option that meets the requirement.

The core components

NeedComponent
Data-first internal app with complex relationshipsModel-driven app on Dataverse
Pixel-level, task-focused app, often mobileCanvas app
Site or portal for external usersPower Pages (formerly Power Apps portals)
Conversational bot or agentCopilot Studio (formerly Power Virtual Agents)
Automation triggered by events or schedulesPower Automate cloud flow
Automating legacy desktop UIPower Automate desktop flow (RPA)
Guided stages of a processBusiness process flow
Reports and dashboardsPower BI

Dynamics 365 apps versus building

Before building, check whether a Dynamics 365 app already covers the domain: Sales for pipelines, Customer Service for cases and Omnichannel, Field Service for work orders and scheduling, Marketing for journeys. Use AppSource for industry and partner solutions. Building from scratch is the last choice when the requirement is standard.

Connecting to existing systems

If the requirement is to show ERP data inside an app without migrating it, choose a connector or a virtual table. Virtual tables show external data as Dataverse tables without copying it. A connector inside a canvas app or flow reads the data on demand. Do not recommend a migration when the scenario says to avoid one.

Automation choices

  • Cloud flow: API-based, runs in the cloud, best default.
  • Desktop flow: when there is no API and a person clicks through a UI.
  • Business rules: simple form logic with no code.
  • Plug-in: only when logic must run inside the Dataverse transaction.

Process guidance

A business process flow suits step-by-step guidance. A playbook in Dynamics 365 Sales guides sellers through organisation-defined best practices in response to sales events. Read the scenario for the clue: stages means business process flow, response to an event with best practices means playbook.

Exam traps

  • Picking a canvas app when a model-driven app fits relational Dataverse data better.
  • Recommending Power Pages for internal users, or a shared canvas app for external ones.
  • Seeing Power Virtual Agents in answers: it is now Copilot Studio, and Power Apps portals is now Power Pages.
  • Choosing a desktop flow when an API or connector exists.
  • Building custom when AppSource or a Dynamics 365 app meets the need.

Practice questions

Choose an answer, then review the explanation to check your understanding.

1. Sales reps must follow the same guided stages of a sale on every device, and the stages must be consistent across the organisation. Which component fits?

Show answer

Answer: B.A business process flow guides users through stages in a model-driven app and works on any device the app runs on.

2. External customers must log in to view and update their own cases using standard Dataverse data. Which component should you recommend?

Show answer

Answer: B.Power Pages is the low-code website platform for external users, with table permissions on Dataverse data.

3. A school needs curriculum and student management, minimal custom code, and must stay in step with platform updates. What is the first place to look?

Show answer

Answer: B.Look for a prebuilt AppSource solution first. It reduces custom work and is maintained by the publisher.

4. Customers chat with a bot in natural language and must be handed to a live agent when needed, routed by skill. Which pair belongs in the design?

Show answer

Answer: A.Copilot Studio (formerly Power Virtual Agents) handles the conversation and Omnichannel for Customer Service does skill-based routing to agents.

PL-600 course outline

All 7 lessons · Course overview
  1. Requirements discovery and feasibilityPerform solution envisioning and requirement analysis Free
  2. Choosing the right Power Platform componentPerform solution envisioning and requirement analysis Free
  3. Designing the Dataverse data modelArchitect a solution Full access
  4. Environment strategy and governanceArchitect a solution Full access
  5. Integration patterns and API limitsArchitect a solution Full access
  6. ALM with solutions and pipelinesImplement the solution Full access
  7. Data migration, testing and go-liveImplement the solution Full access