Microsoft Certified Power Platform Fundamentals · Free Practice Question Medium
Question 39
Scenario: The Eat-More Corporation is a U.S.-based fast-food restaurant chain headed by Teresa Payton. The main headquarters and processing plants of the Eat-More Corporation are located in Sedona, Arizona. Eat-More has restaurants located all over the United States and has plans to expand internationally. The expansion plans are underway and have presented several IT challenges which Teresa has contracted you to advise her IT staff on.
At the moment, the topic is building apps to support business operations which will use connectors to access data from several data sources and respond to a number of events generated by components.
The team is confused about which operations they can use for connectors so Teresa asked you to step in to lead the team.
Which operations should you advise them to use for connectors? (Select two)
-
A
Triggers
-
B
Gateways
-
C
Plug-ins
-
D
Actions
Reveal correct answers
Correct answers: A, D
Explanation
You should advise the team to use Action and Triggers. Gateways are used for local access.
A connector is a proxy or a wrapper around an API that allows the underlying service to talk to Microsoft Power Automate, Microsoft Power Apps, and Azure Logic Apps. It provides a way for users to connect their accounts and leverage a set of prebuilt actions and triggers to build their apps and workflows.
Our large ecosystem of software as a service (SaaS) connectors enables you to connect apps, data, and devices in the cloud. Examples of popular connectors include Salesforce, Office 365, Twitter, Dropbox, Google services, and more.
Architecture
Architecture components
Here are the architecture components and what they do:
Credential and metadata store—A service to store connector metadata (swagger, connection, ACLs, etc.), and credentials associated with a connection.
Connector
Azure APIM (API Manager) to host all the swagger and policies. In addition to being the entry point for all calls that interact with the connector calls, Azure APIM verifies keys, tokens, certificates, and other credentials.
App Service Environment to host connector webapps.
Connector components
Each connector offers a set of operations classified as actions and triggers. Once you connect to the underlying service, these operations can be easily leveraged within your apps and workflows.
Actions
Actions are changes directed by a user. For example, you would use an action to look up, write, update, or delete data in a SQL database. All actions directly map to operations defined in the swagger.
Triggers
Several connectors provide triggers that can notify your app when specific events occur. For example, the FTP connector has the OnUpdatedFile trigger. You can build either a Logic App or a flow that listens to this trigger and performs an action whenever the trigger fires.
There are two types of triggers:
Polling Triggers—These triggers call your service at a specified frequency to check for new data. When new data is available, it causes a new run of your workflow instance with the data as input.
Push Triggers—These triggers listen for data on an endpoint, that is, they wait for an event to occur. The occurrence of this event causes a new run of your workflow instance.
Note: Triggers are not supported in Power Apps.
Use connectors
Connectors are available for use in multiple products.
Power Automate
Work smarter by building workflows and automating processes across your apps and services. Streamline notifications, sync data between systems, automate approval, and more.
Power Apps
Power Apps enables users to build cloud connected and cross platform business apps using clicks and minimal code. Create rich user experiences across the web, phones, and tablets. Assemble forms, add business logic, and take advantage of device capabilities with full creative freedom.
Logic Apps
Logic Apps is the workflow engine for Power Automate. It enables pro-developers to visually create or programmatically configure workflows in Azure. A connector in Logic Apps enables users to automate EAI, Business to business (B2B), and Business to consumer (B2C) scenarios while reaping the benefits of source control, testing, support, and operations.
https://docs.microsoft.com/en-us/azure/connectors/apis-list
Custom connectors
We offer a wide variety of connectors, but sometimes you might want to call APIs, services, and systems that aren't available as prebuilt connectors. To support more tailored scenarios, you can build custom connectors with their own triggers and actions. These connectors are function-based—data is returned based on calling specific functions in the underlying service.
https://docs.microsoft.com/en-us/connectors/custom-connectors/
A. Triggers are operations that can initiate actions in response to events generated by components. They are crucial for automating processes and ensuring that the app can respond to changes in data sources or external systems in a timely manner.
B. Gateways are not operations that are used for connectors in the context of building apps to support business operations. Gateways are typically used for connecting on-premises data sources to cloud services, rather than performing operations on data sources through connectors.
C. Plug-ins are not operations that can be used for connectors in the context of building apps to support business operations. Plug-ins are typically used for extending the functionality of a specific platform or application, rather than interacting with data sources through connectors.
D. Actions are operations that can be performed by connectors to interact with data sources and perform specific tasks. They allow the app to manipulate data, such as creating, updating, or deleting records in a database, and are essential for building apps that support business operations.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
