You are building a custom application in Azure to process resumes for the HR department. The app will monitor submissions of resumes and parse the resumes. You need to parse the resumes and save…

The correct answer is A. Power Automate. Power Automate is the correct mechanism for orchestrating this end-to-end workflow: monitoring resume submissions (e.g., from email or SharePoint), parsing the content (using AI Builder or other connectors), and saving structured contact and skills data to Common Data Service…

Submitted by lukas.cz· Apr 18, 2026

Question

You are building a custom application in Azure to process resumes for the HR department. The app will monitor submissions of resumes and parse the resumes. You need to parse the resumes and save contact and skills information into the Common Data Service. Which mechanism should you use?

Options

APower Automate
BCommon Data Service plug-in
CWeb API
DCustom workflow activity

How the community answered

(64 responses)

A
83% (53)
B
5% (3)
C
2% (1)
D
11% (7)

Explanation

Power Automate is the correct mechanism for orchestrating this end-to-end workflow: monitoring resume submissions (e.g., from email or SharePoint), parsing the content (using AI Builder or other connectors), and saving structured contact and skills data to Common Data Service (Dataverse). It provides built-in triggers, connectors, and CDS integration without custom code. Option B (CDS plug-in) runs within the CDS platform context in response to data events - it is not suited for monitoring external file submissions. Option C (Web API) is for making direct HTTP calls to CDS and would require custom code to build the full pipeline. Option D (Custom workflow activity) is a Dynamics 365 server-side extension and is not designed for parsing external files or monitoring submissions.

Community Discussion

No community discussion yet for this question.

Full PL-400 Practice