PL-500 Question #120: Real Exam Question with Answer & Explanation

Question

Drag and Drop Question A company uses an enterprise resource planning (ERP) system. The ERP system has an API. The company requires a custom connector for the ERP system. You need to create the custom connector. In which order should you perform the actions? To answer, move all actions from the list of actions to the answer area and arrange them in the correct order. Answer:

Explanation

The correct order for creating an Azure custom connector involves defining general details, then security, then actions, and finally testing the connection.

Approach. To correctly create a custom connector, the actions must be performed in a logical sequence reflecting the connector's configuration stages:

1. Enter name and host details: This is the initial step to configure the connector's basic information, such as its name, description, and the base URL (host) of the ERP system's API it will connect to. This corresponds to the 'General' tab in the custom connector creation wizard.
2. Identify authentication type: After defining the basic details, the next crucial step is to specify how the custom connector will authenticate with the underlying ERP API. This could involve API keys, OAuth 2.0, Basic authentication, etc., and corresponds to the 'Security' tab.
3. Define actions and triggers: Once the basic information and authentication are set up, you proceed to define the specific operations (actions) that the connector will expose and any optional triggers. This involves mapping to the API's endpoints and specifying request/response parameters, corresponding to the 'Definition' tab.
4. Test the connection: The final step in the creation process is to test the configured actions and ensure that the connection to the API works as expected, using the defined authentication and operations. This corresponds to the 'Test' tab.

Common mistakes.

• common_mistake. A common mistake is attempting to test the connection before defining the authentication or the actions/triggers. Without proper authentication details or defined operations, the test would inevitably fail or be impossible to execute. Another incorrect approach would be to define actions and triggers before setting up the basic host details or authentication, as the API endpoints and security rely on these foundational configurations to function correctly.

Concept tested. The underlying technical concept being tested is the sequential process and required steps for creating a custom connector in platforms like Power Automate or Power Apps, demonstrating an understanding of how to integrate with an external API by configuring its general information, security, definition of operations, and subsequent testing.

No community discussion yet for this question.