Microsoft Certified Power Platform Fundamentals · Free Practice Question Medium
Question 27
Scenario: You are working as a consultant at Avengers Security. At the moment, you are consulting with Tony, the lead of the IT team and the topic of discussion is Power Platform APIs.
Tony likes the idea of implementing a Microsoft Power Platform solution, but is concerned about the ability to interact with a custom API.
Which is the best response for Tony?
-
A
Microsoft Power Platform uses connectors that hold a series of functions available for developers.
-
B
Microsoft Power Platform offers the ability to create custom connectors for this purpose which allow you to connect to Power Apps and Power Automate.
-
C
Microsoft Power Platform has over 270 connectors to use in these situations.
-
D
Microsoft Power Platform uses the Mulesoft api integration tool to connect third-party and custom apis which will work for any type of api.
Reveal correct answer
Correct answer: B
Explanation
You can build out a custom connector to bridge your app or workflow to the API.
Microsoft Power Platform is made powerful by its ability to leverage data across many platforms. To do this, components of Microsoft Power Platform use connectors. You can think of connectors as a bridge from your data source to your app or workflow which allows information to be conveyed back and forth. Connectors allow you to extend your business solutions across platforms and add functionality for your users.
Data Sources
In order to understand the types of connectors and what you can do with them, you must first understand the types of data sources to which they connect. The two types of data sources are tabular and function-based.
Tabular data - A tabular data source is one that returns data in a structured table format. Power Apps can directly read and display these tables through galleries, forms, and other controls. Additionally, if the data source supports it, Power Apps can create, edit, and delete data from these data sources. Examples include Microsoft Dataverse, SharePoint, and SQL Server.
Function-based data - A function-based data source is one that uses functions to interact with the data source. These functions can be used to return a table of data but offer more extensive action such as the ability to send an email, update permissions, or create a calendar event. Examples include Office 365 Users, Project Online, and Azure Blob Storage.
Both of these data source types are commonly used to bring data and additional functionality to your solutions.
As you can see, connecting to data sources allows you to integrate disparate parts of your business solutions to build them out cohesively.
Connectors
Connectors are the bridges from your data source to your app, workflow, or dashboard. Microsoft Power Platform has more than 275 connectors available to common data sources. Connectors are divided into standard and premium. Some popular standard connectors are SharePoint, Outlook, and YouTube. Premium connectors require additional licensing for your app and/or users. A few premium connectors are SQL Server, Survey Monkey, and Mail Chimp. The connector reference in the summary and resources unit lists all connectors and whether they are considered standard or premium. You can also use AppSource to source and install apps and use the connectors to non-Microsoft services.
Connectors can provide input and output between the data source and Power Platform, which can accelerate the delivery of Microsoft Power Platform business solutions. For instance, using Dynamics 365 apps such as Customer Service, you can set up Power Automate to notify users when specific customer types are added. Or you can use a SharePoint document library to store files that are fed into Power Apps to manage and distribute. Microsoft also provides connectors to their Azure services, providing advanced AI techniques to do tasks such as reading text off images or cognitive services like recognizing faces in images.
All Microsoft Power Platform business solutions can be used and implemented into Microsoft 365 apps such as Teams. This allows users to play Power Apps within Teams or run Power Automate from actions and events within Teams.
Triggers and Actions
Once you have established a data source and configured your connector, there are two types of operations you can use, triggers or actions.
Triggers are only used in Power Automate and prompt a flow to begin. Triggers can be time based, such as a flow which begins every day at 8:00 am, or they could be based off of an action like creating a new row in a table or receiving an email. You will always need a trigger to tell your workflow when to run.
Actions are used in Power Automate and Power Apps. Actions are prompted by the user or a trigger and allow interaction with your data source by some function. For example, an action would be sending an email in your workflow or app or writing a new line to a data source.
Now that you understand what connectors are and how to use them, let's look at what to do when there isn't a connector already built for your data source.
Custom Connectors
While Microsoft Power Platform offers more than 200 connectors, you also have the option to build a custom connector. This will allow you to extend your app by calling a publicly available API, or a custom API you are hosting in a cloud provider, such as Azure. API stands for Application Programming Interface and holds a series of functions available for developers. Connectors work by sending information back and forth across these APIs and gathering available functions into Power Apps or Power Automate. Because these connectors are function-based, they will call specific functions in the underlying service of the API to return the corresponding data.
An advantage of building custom connectors is that they can be used in different platforms, such as Power Apps, Power Automate, and Azure Logic Apps.
Creating Custom Connectors
You can create custom connectors using 3 different approaches:
While the requirements for each approach will vary, they all require a Power Apps per app or per user plan. Each link above points to the instructions for each approach.
A. Microsoft Power Platform connectors do indeed hold a series of functions available for developers to use when integrating with various systems. However, in the case of interacting with a custom API, creating a custom connector tailored to the specific API requirements would be the most appropriate approach.
B. Microsoft Power Platform offers the ability to create custom connectors specifically for interacting with custom APIs. These custom connectors can be used in Power Apps and Power Automate to seamlessly integrate with external systems and services, providing a flexible and efficient solution for Tony's concerns.
C. While Microsoft Power Platform does offer a wide range of connectors, having over 270 options, these connectors are pre-built integrations with popular services and applications. They may not directly address Tony's need to interact with a custom API, as custom connectors are more suitable for this purpose.
D. Microsoft Power Platform does not use the Mulesoft API integration tool for connecting to third-party or custom APIs. Instead, it provides the capability to create custom connectors or leverage existing connectors to interact with external systems. Using Mulesoft for API integration would introduce unnecessary complexity and may not be the most efficient solution for Tony's needs.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
