Drag and Drop Question A company uses Power Apps. The company requires a canvas app that connects to the following sources: - SharePoint list - Microsoft 365 mailbox - SOAP API You need to select…

Question

Exhibit

Answer Area

Explanation

This question tests the ability to distinguish between standard and custom connector types in Power Apps based on common data sources like SharePoint, Microsoft 365 mailboxes, and generic SOAP APIs.

Approach. The correct approach is to drag 'Standard' to 'SharePoint list' because Power Apps has a rich, pre-built connector for SharePoint. Similarly, 'Standard' should be dragged to 'Microsoft 365 mailbox' as Microsoft 365 services, including Outlook mailboxes, have readily available standard connectors in Power Apps. Finally, 'Custom' should be dragged to 'SOAP API'. While some specific APIs might have standard connectors, a generic 'SOAP API' typically requires a custom connector to define its operations, parameters, and authentication methods for use within Power Apps, as there isn't a universal standard connector for all possible SOAP APIs.

Common mistakes.

• common_mistake. A common mistake would be to assign 'Custom' to SharePoint or Microsoft 365 mailbox. These are widely used Microsoft services with comprehensive, pre-built standard connectors, making a custom connector unnecessary and overly complex. Another mistake would be to assign 'Standard' to a generic 'SOAP API'. Unless a specific SOAP API is explicitly stated to have a standard connector, it generally falls under the custom connector category because Power Apps needs to be configured to understand its unique structure and operations.

Concept tested. The core concept being tested is the understanding of Power Apps connector types- specifically, when to use a 'Standard' (pre-built) connector versus a 'Custom' (user-defined) connector for various data sources and APIs.

No community discussion yet for this question.