Implement Power Platform Integrations Flashcards
7 cards from real PL 400 practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Implement Power Platform Integrations flashcards as text
Which Microsoft Graph API permission scope is required for a Power Platform custom connector to read all users' calendars in an organization?
Answer: Calendars.Read (application)
Application permission Calendars.Read allows the connector to read all users' calendars without a signed-in user context, requiring admin consent.
A Power Apps model-driven app requires real-time data from an external REST API. Which approach avoids storing data in Dataverse while still displaying it in the app?
Answer: Use a virtual table with a custom virtual table provider
Virtual tables (virtual entities) surface external data directly in model-driven apps by delegating CRUD operations to a custom provider at query time.
What is the correct way to pass a Bearer token to a downstream API inside a Power Automate HTTP action?
Answer: Set the Authorization header to 'Bearer {token}'
The HTTP standard requires Bearer tokens to be sent in the Authorization header with the 'Bearer ' prefix.
Which Power Automate action lets you iterate over paged OData responses from Dataverse when the result set exceeds 5,000 rows?
Answer: Do until loop checking @odata.nextLink
OData paged responses include an @odata.nextLink property; a Do Until loop that follows this link until it is empty retrieves all rows beyond the 5,000-row page limit.
In the context of Power Platform integration, what is the role of Azure API Management (APIM) when fronting backend services?
Answer: It provides policy enforcement, rate limiting, and a stable URL for custom connectors to call
APIM acts as a façade that applies policies (throttling, auth, transformation) and exposes a consistent endpoint, which custom connectors target instead of backend services directly.
A Dataverse plug-in must read a configuration value that differs between dev and production without redeploying the plug-in. What is the recommended approach?
Answer: Use the plug-in's unsecure configuration field in the step registration
The unsecure (and secure) configuration fields in the plug-in step registration allow environment-specific strings to be passed to the plug-in without redeployment.
Which authentication flow is most appropriate for a server-to-server integration between an Azure Function and Dataverse where no user interaction is possible?
Answer: Client credentials flow
The client credentials flow authenticates using a client ID and secret (or certificate) without user involvement, making it ideal for daemon/service integrations.