CompTIA
Checkpoint
ISC
HP
Dell
EC-Council
EXIN
Fortinet
ITIL®
Juniper
PMI
Microsoft
VMware
Avaya
Google
Salesforce
Amazon
Palo Alto Networks
Certiport
ISC2
All Vendors
  2. Home
  3. Exams
  4. Microsoft
  5. PL-400

Free PL-400 Exam Braindumps

DRAG DROP (Drag and Drop is not supported)
You are designing a custom connector for an internal API used by Contoso, LLC.

Authentication to the API is carried out by using an API key. The API key is stored within Azure Key Vault. Each environment has a separate instance of the API with a different API key.

You need to reference the API key from Key Vault in the custom connector.

Which four actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.

NOTE: More than one order of answer choices is correct. You will receive credit for any of the correct orders you select.

  1. See Explanation section for answer.

Answer(s): A

Explanation:





Step 1: Create an environment variable named APIKey(contoso_APIKey)
Use environment variables in solution custom connectors
Applications often require different configuration settings or input parameters when deployed to different environments. Environment variables store the parameter keys and values, which can then serve as input to various other application objects.

Environment variables can use the following syntax in custom connector fields:
@environmentVariables("environmentVariableName")

Example
@environmentVariables("cr49f_SharePointSiteURL_7weem")

Step 2: Remove the current value
Create an environment variable in a solution
1. Sign in to Power Apps (make.powerapps.com), and then on the left pane select Solutions. If the item isn’t in the side panel pane, select …More and then select the item you want.

2. Open the solution you want or create a new one.

3. On the command bar, select New > More, and then select Environment variable.

4. On the right pane, complete the following columns, and then select Save:

Display name. Enter a name for the environment variable.

Name. The unique name is automatically generated from the Display name, but you can change it.

Data Type. Select from Decimal number, Text, JSON, Two options, Data source, or Secret.

Current Value. Also known as the value. This property is optional and is a part of the environment variable value table. When a value is present, it's used, even if a default value is also present. *Remove the value from your solution if you don't want to use it in the next environment* . The values are also separated into separate JSON files within the exported solution.zip file and can be edited offline.

Step 3: Create a connection
To use the values from environment variables in any of the fields on the Security tab, do the following:

Select New > Automation > Custom connector.

On the Security tab, enter the environment variable syntax to refer to an environment variable.



Step 4: Use the syntax @environmentVariables("contoso.ApiKey")
Environment variables with the data type Secret can now be used in custom connectors. You need to configure the Azure Key Vault by using the steps outlined here. In the security configuration UI, the value is masked. You'll need to use the following syntax: @environmentVariables("environmentVariableName")


Reference:

https://learn.microsoft.com/en-us/connectors/custom-connectors/environment-variables
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/environmentvariables#use-azure-key-vault-secrets



You are creating a plug in that connects to a third-party REST API.

The API credentials must be secured so they are visible only to system administrators. The API credentials must not interfere with other system functionality.

You need to store the credentials.

Which method should you use?

  1. Plug-in secure configuration
  2. Text environment variable
  3. Connection reference
  4. Plug-in unsecure configuration

Answer(s): A

Explanation:

Pass configuration data to your plug-in
When you register a plug-in, you may optionally specify configuration data to pass to the plug-in at run-time. Configuration data allows you to define how a specific instance of a registered plug-in should behave. This information is passed as string data to parameters in the constructor of your class. There are two parameters named unsecure and secure. Use the first unsecure parameter for data that you don't mind if someone else can see. Use the second secure parameter for sensitive data.

The following code shows the three possible constructor signatures for a plug-in class named MyPlugin.

public MyPlugin() {}
public MyPlugin(string unsecure) {}
public MyPlugin(string unsecure, string secure) {}

The secure configuration data is stored in a separate table that only system administrators have privileges to read.

Incorrect:
Not B: Text environment variable
Would be insecure.

Not C: Use a connection reference in a solution with Microsoft Dataverse
A connector is a proxy or a wrapper around an API that allows the underlying service to talk to Microsoft Power Automate, Microsoft Power Apps, and Azure Logic Apps. It provides a way for users to connect their accounts and use a set of prebuilt actions and triggers to build their apps and workflows.

A connection is a stored authentication credential for a connector, for example OAuth credentials for the SharePoint connector.

Limits
* Canvas apps don't recognize connection references on custom connectors. To work around this limitation, after a solution is imported to an environment the app must be edited to remove and then readd the custom connector connection.


Reference:

https://learn.microsoft.com/en-us/power-apps/developer/data-platform/write-plug-in
https://learn.microsoft.com/en-us/power-apps/maker/data-platform/create-connection-reference



DRAG DROP (Drag and Drop is not supported)
You plan to integrate Microsoft Dataverse data to a system using a Microsoft Azure function.

You configure the message containing the data to be sent asynchronously. You need to plan for the following errors:

-The failure of business logic that uses a synchronous plug-in.
-The Azure function is unreachable.

You need to determine the behavior when an error occurs.

Which retry behavior will be used? To answer, move the appropriate retry behaviors to the correct error scenarios. You may use each retry behavior once, more than once, or not at all. You may need to move the split bar between panes or scroll to view content.

NOTE: Each correct selection is worth one point.


  1. See Explanation section for answer.

Answer(s): A

Explanation:



Box 1: Message is not sent and will not retry.
The failure of business logic that uses a synchronous plug-in.

Box 2: Message is not sent and will retry continually.
The Azure function is unreachable.



A company requires a plug-in that makes multiple requests to an external web service. The plug-in must not time out when the web service has issues or is slow to respond.

You need to create the plug-in.

What should you do?

  1. Assign the IOrganizationService object to a member variable.
  2. Register the plug-in to run synchronously.
  3. Register the plug-in step once for each web service request.
  4. Set the HTTP connection timeout value explicitly to limit how long each connection can remain open.

Answer(s): D

Explanation:

This ensures that the plug-in doesn't wait indefinitely for a response and avoids timing out due to slow web service responses.






Post your Comments and Discuss Microsoft PL-400 exam with other Community members:

PL-400 Exam Discussions & Posts