PL-900 - Describe the Business Value of Microsoft Power Platform - Section 1.2

Describe how Power Platform connects with Microsoft 365, Dynamics 365, Azure, and third-party applications.

Describe how Power Platform integrates with Microsoft 365, Dynamics 365, and Azure services through its connector ecosystem. Recognise that third-party connectors extend this reach, and distinguish which integration path suits a given scenario.

Microsoft 365 integrationDynamics 365Azure servicesthird-party connectorsPower Platform ecosystem

Practice question for this objective

Free sampleDescribe the Business Value of Microsoft Power Platformhard

A healthcare provider is planning how to reach external systems from its cloud flows. Some target systems, such as Office 365 and Google services, are widely used, while one legacy in-house scheduling API has no ready-made integration. Which statements about Power Platform connectors correctly describe how each need is met and the value each connector type provides? (Select 2 answers)

  • APrebuilt connectors are predefined and can be used without modification, addressing commonly used business process scenarios Correct
  • BA custom connector is a function-based connector you build to support a tailored scenario such as the legacy in-house scheduling API Correct
  • CConnectors expose actions and triggers, so the legacy in-house scheduling API can be reached without building any custom connector
  • DEvery external system must use a custom connector, because prebuilt connectors cannot reach third-party SaaS services
  • EPrebuilt connectors require you to write function-based code before they address common scenarios
Prebuilt connectors cover common scenarios with no code, while custom connectors extend reach to bespoke systems, together giving broad integration value. The grounding distinguishes prebuilt connectors, which are predefined and need no modification for common scenarios, from custom connectors, which are function-based and built to support tailored needs like a legacy API.

Why A is correct: Correct. Prebuilt connectors are predefined and can be used without modification, addressing commonly used business process scenarios is one of the keyed answers. The grounding distinguishes prebuilt connectors, which are predefined and need no modification for common scenarios, from custom connectors, which are function-based and built to support tailored needs like a legacy API.

Why B is correct: Correct. A custom connector is a function-based connector you build to support a tailored scenario such as the legacy in-house scheduling API is one of the keyed answers. The grounding distinguishes prebuilt connectors, which are predefined and need no modification for common scenarios, from custom connectors, which are function-based and built to support tailored needs like a legacy API.

Why C is wrong: Connectors do expose actions and triggers, but a legacy API with no prebuilt connector still needs a custom connector to reach it, so claiming none is required is wrong and does not meet the legacy need.

Why D is wrong: Prebuilt connectors are exactly the ready-made integrations for popular SaaS services like Office 365 and Google services, so claiming custom is always required contradicts the grounding.

Why E is wrong: The grounding states prebuilt connectors need no modification; it is custom connectors that are function-based and built by you, so this reverses the two types.

See more PL-900 practice questions, answers explained.

More in this domain

Back to all Describe the Business Value of Microsoft Power Platform objectives, or the PL-900 cert hub.

Examworthy is not affiliated with or endorsed by Microsoft. Original, blueprint-aligned practice material only.