PL-900 Practice Question: Manage the Microsoft Power Platform environment
An organization uses Microsoft Power Platform and wants to enforce data loss prevention (DLP) policies across all environments. They need to block the use of a specific third-party connector in all environments. What should the administrator do?
⚠ Common exam trap
Many candidates assume DLP policies must be created per environment, overlooking the tenant-level scope that provides centralized enforcement across all environments.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a tenant-level DLP policy that blocks the connector
DLP policies in Microsoft Power Platform can be configured at the tenant level to apply across all environments. By creating a tenant-level DLP policy and blocking the specific third-party connector, the administrator ensures consistent enforcement without needing to manage individual environment policies. This approach centralizes control and prevents the connector from being used in any environment.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Create a DLP policy for each environment and block the connector
Why it's wrong here
Per-environment DLP policies leave any environment without a policy unrestricted, so the connector stays usable there. Environment-scoped policies are correct when different environments need different connector groupings; a tenant-wide policy is required to block a connector across all environments simultaneously.
- ✗
Create a custom connector with the same name and block it
Why it's wrong here
A custom connector is a distinct object with its own identity, so blocking it leaves the original third-party connector usable. Custom connectors exist to wrap bespoke APIs for Power Apps and Power Automate; creating one is correct when integrating an API that has no published connector, not for restricting an existing one.
- ✗
Remove the connector from the default solution
Why it's wrong here
Removing a connector from a default solution only changes solution contents; it does not restrict connector use, since makers can still add it directly. Solutions package and transport components between environments, so this would be the right action when deploying customisations, not when enforcing tenant-wide connector blocking.
- ✓
Create a tenant-level DLP policy that blocks the connector
Why this is correct
A tenant-level DLP policy applies across every environment within the tenant, so blocking the third-party connector there satisfies the requirement to restrict it everywhere. Environment-scoped policies would only cover individual environments, leaving others unprotected. Tenant-wide scope is the mechanism that enforces the block universally.
Go deeper
Related to this question
About these practice questions
This PL-900 question is part of Courseiva's 701-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PL-900 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PL-900 exam.