Microsoft Certified Power Platform Functional Consultant Associate · Free Practice Question Easy
Question 42
To include HTTP triggers / actions within a DLP policy, which schema version must you use when creating that DLP policy?
-
A
2018-11-01
-
B
2016-01-01
-
C
2019-01-01
-
D
2017-07-21
Reveal correct answer
Correct answer: A
Explanation
Power Platform Management connectors are managed like any other connector in Power Platform.
HTTP triggers and actions can only be managed through the existing DLP editor, with some actions being performed by an administrator. The partial reason for this parameter is because HTTP triggers and actions are considered to be built in and technically aren't considered connectors, even though they might have similar characteristics.
However, because of customer needs and past feedback, it is possible to manage the triggers/actions that are shown in the following image.
These triggers/actions can only be managed in DLP policies that have a schema version of 2018-11-01, which is discussed in the linked blog. By using a new schema version, it allows organizations to make the decision to implement these changes. Otherwise, it's highly possible that some flows will be broken, depending on how an organization wants to classify the connectors as business or non-business.
For example, if the HTTP action was previously not managed and is being used with connectors from the Business data group and is then placed in the Non-business data group, then any flows that are using this configuration will be suspended because of DLP violations.
By using this new schema version, DLP policies can be constructed by using either of the following tables:
Power Platform Management connector
Power Apps and Power Automate PowerShell cmdlets
However, using PowerShell is the simplest path forward. Additional information about PowerApps and Power Automate PowerShell cmdlets can be found at PowerShell support for Power Apps.
After installing the prerequisite PowerShell modules, you can run the following statement, (New-AdminDlpPolicy -DisplayName "HTTP DLP Policy" -SchemaVersion 2018-11-01), which will create a new DLP policy that includes support for HTTP when you include a -SchemaVersion parameter of 2018-11-01. After you have run the previous statement, you'll be asked to sign in by using your admin credentials.
After the command has been run, you'll be provided a status output that includes the internal PolicyName and other attributes.
If you go to the Power Automate Admin Centre, you'll discover that the DLP policy has been created.
Note: Because an environment parameter was not specified when you created this DLP policy, it will be applicable to the entire tenant.
After you have explored this DLP policy, you'll find that your HTTP triggers and actions are included in your default data group, which in this case is No business data allowed. These connectors can be managed just like any other connectors and can be added to the Business data only data group.
A. The correct schema version to use when including HTTP triggers/actions within a DLP policy is 2018-11-01. This schema version supports the necessary configurations and settings for HTTP triggers/actions to be properly integrated into the DLP policy.
B. The schema version 2016-01-01 does not support the inclusion of HTTP triggers/actions within a DLP policy. It lacks the specific configurations and settings required for handling HTTP-related functionalities in the policy.
C. The schema version 2019-01-01 is not the correct choice for including HTTP triggers/actions within a DLP policy. It may not have the specific configurations and settings tailored for handling HTTP functionalities effectively within the policy.
D. The schema version 2017-07-21 also does not provide the necessary support for including HTTP triggers/actions within a DLP policy. It may lack the updated features and capabilities required for managing HTTP-related components in the policy.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
