hardMultiple ChoiceObjective-mapped
PL-900 Practice Question: A non-profit organization has deployed a Power…
A non-profit organization has deployed a Power Pages site for volunteer registration. The site uses Dataverse to store volunteer profiles and their availability. Volunteers can log in using their Microsoft Entra ID (formerly Azure AD) accounts. The organization now wants to extend the site to allow volunteers to sign up for specific shifts, which requires integration with a third-party scheduling API. The API requires an OAuth 2.0 client credentials flow with a client secret. You need to securely call this API from Power Pages without exposing the secret to client-side code. What should you do?
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Create a Power Automate flow that calls the scheduling API using an HTTP action with OAuth 2.0, and call that flow from Power Pages using the 'Run a flow' button.
The correct approach is to create a Power Automate flow that calls the scheduling API using an HTTP action with OAuth 2.0 and client credentials. Power Automate runs server-side, so the client secret can be securely stored using environment variables or connector references, preventing client-side exposure. Option A (JavaScript with Fetch API) is insecure because the secret would be visible in client-side code. Option C (custom connector) stores secrets in the connector but is typically used for client-side calls and does not provide the same level of security for server-side execution. Option D (Azure Function) is a valid server-side option but adds unnecessary complexity compared to using Power Automate, which is natively integrated with Power Pages.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use JavaScript with the Fetch API to call the scheduling API directly, embedding the client secret in a configuration file.
Why it's wrong here
Embedding secrets in client-side code is insecure.
- ✓
Create a Power Automate flow that calls the scheduling API using an HTTP action with OAuth 2.0, and call that flow from Power Pages using the 'Run a flow' button.
Why this is correct
Power Automate runs server-side and can securely store secrets using environment variables or connector settings.
- ✗
Create a custom connector for the API using OAuth 2.0 with a client secret stored in the connector.
Why it's wrong here
Custom connectors are used for client-side calls; the secret would still be exposed in the browser.
- ✗
Deploy an Azure Function that proxies the API calls and stores the secret in Azure Key Vault; call the function from Power Pages.
Why it's wrong here
The Azure Function proxy bypasses Power Pages’ native custom connector feature, which can securely store the client secret and directly perform the OAuth 2.0 client credentials flow against the third-party API without needing an additional service. This option is tempting because combining Azure Functions with Key Vault is a standard approach for securing API secrets from client-side exposure in web applications, and would be correct when the integration demands custom server-side processing beyond Power Pages’ built-in connector logic.
Go deeper
Related to this question
About these practice questions
Courseiva writes every PL-900 question from scratch — 904 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.