Quick Answer
The answer is sending an email when a new record is created, as this directly demonstrates one of the most common uses of connectors in Power Automate: automating notifications based on data events. Connectors act as bridges between Power Automate and external services, providing pre-built triggers and actions that eliminate the need for custom code. In this case, the Dataverse connector’s “When a record is created” trigger pairs with an email action to instantly alert a user, showcasing how connectors streamline business processes by reacting to database changes. On the Microsoft Power Platform Fundamentals PL-900 exam, this scenario tests your understanding of how connectors enable integration without manual intervention. A common trap is confusing triggers (like “when a record is created”) with actions (like “send an email”), so remember that connectors supply both halves of the automation. For a memory tip, think “trigger then action” — the connector first detects the event, then performs the task.
This PL-900 practice question tests your understanding of identify foundational components of microsoft power platform. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Which THREE are common uses of connectors in Power Automate? (Choose three.)
Build a custom user interface
Why wrong: Power Apps function.
Create a record in Dataverse
Common data operation.
Post a message to Microsoft Teams
Common Teams connector.
Create a real-time dashboard
Why wrong: Power BI capability, not connector.
Send an email when a new record is created
Common email connector use.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Create a record in Dataverse
Option B is correct because connectors in Power Automate provide pre-built actions and triggers to interact with external services. The Dataverse connector includes a 'Create a new record' action, enabling automated creation of rows in Dataverse tables without custom code, directly from a flow.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Build a custom user interface
Why it's wrong here
Power Apps function.
Create a record in Dataverse
Why this is correct
Common data operation.
Related concept
Read the scenario before looking for a memorised answer.
Post a message to Microsoft Teams
Why this is correct
Common Teams connector.
Related concept
Read the scenario before looking for a memorised answer.
Create a real-time dashboard
Why it's wrong here
Power BI capability, not connector.
Send an email when a new record is created
Why this is correct
Common email connector use.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates may confuse connectors with other Power Platform components, mistakenly thinking connectors can build UIs (Power Apps) or create dashboards (Power BI), when connectors are strictly for integration and automation.
Detailed technical explanation
Connectors in Power Automate wrap RESTful APIs of services like Microsoft Teams, Dataverse, and Exchange Online, exposing them as triggers and actions. For example, the 'Send an email' action uses the Office 365 Outlook connector, which calls the Microsoft Graph API's /users/{id}/sendMail endpoint. The 'Post a message' action in the Teams connector uses the Graph API's /teams/{id}/channels/{id}/messages endpoint, requiring proper authentication and permissions.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Identify foundational components of Microsoft Power Platform — study guide chapter
Learn the concepts, then practise the questions
Identify foundational components of Microsoft Power Platform practice questions
Targeted practice on this topic area only
All PL-900 questions
976 questions across all exam domains
Microsoft Power Platform Fundamentals PL-900 study guide
Full concept coverage aligned to exam objectives
PL-900 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PL-900 questions linked to Identify foundational components of Power Platform.
Practise PL-900 questions linked to Demonstrate capabilities of Power BI.
Practise PL-900 questions linked to Describe complementary Microsoft Power Platform solutions.
Practise PL-900 questions linked to Demonstrate the capabilities of Power Automate.
Practise PL-900 questions linked to Describe the business value of Microsoft Power Platform.
Practise PL-900 questions linked to Manage the Microsoft Power Platform environment.
Practise PL-900 questions linked to Identify foundational components of Microsoft Power Platform.
Practise PL-900 questions linked to Demonstrate the capabilities of Power BI.
Practise PL-900 questions linked to Demonstrate the capabilities of Power Apps.
Practise PL-900 questions linked to Demonstrate the capabilities of Microsoft Copilot Studio.
Practise PL-900 questions linked to Demonstrate the capabilities of Power Pages.
Practise PL-900 questions linked to PL-900 fundamentals.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Identify foundational components of Microsoft Power Platform — This question tests Identify foundational components of Microsoft Power Platform — Read the scenario before looking for a memorised answer..
The correct answer is: Create a record in Dataverse — Option B is correct because connectors in Power Automate provide pre-built actions and triggers to interact with external services. The Dataverse connector includes a 'Create a new record' action, enabling automated creation of rows in Dataverse tables without custom code, directly from a flow.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Last reviewed: Jun 11, 2026
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.