exam questions

Exam PL-600 All Questions

View all questions & answers for the PL-600 exam

Exam PL-600 topic 2 question 1 discussion

Actual exam question from Microsoft's PL-600
Question #: 1
Topic #: 2
[All PL-600 Questions]

DRAG DROP -
You are designing data loss policies for a Microsoft Power Platform implementation.
You have the following requirements:
✑ Solutions that use the HTTP connector must not include any other connectors.
✑ Prevent the use of the Microsoft Forms connector.
✑ Allow the use of the Azure DevOps connector.
You need to determine in which data policy group to add each connector.
To which data policy group should you assign the connector? To answer, drag the appropriate setting to the correct drop targets. Each source may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.
NOTE: Each correct selection is worth one point.
Select and Place:

Show Suggested Answer Hide Answer
Suggested Answer:
Box 1: Business -
If you put a connector in the Business group, it can only be used with other connectors from that group in any given app or flow.

Box 2: Non-business -
DLP policies enforce rules for which connectors can be used together by classifying connectors as either Business or Non-Business.

Box 3: Blocked -
Sometimes you might want to block the usage of certain connectors altogether by classifying them as Blocked.
Data policy group Business blocked
Reference:
https://docs.microsoft.com/en-us/power-platform/admin/wp-data-loss-prevention

Comments

Chosen Answer:
This is a voting comment (?). It is better to Upvote an existing comment if you don't have anything to add.
Switch to a voting comment New
Daniel1992
Highly Voted 2 years, 8 months ago
I think it is 1- Non-Business 2- Business
upvoted 28 times
BrettusMaximus
2 years, 5 months ago
1- Non-Business 2- Business 3- Block Best practice is to move all business connectors to business first. (Dataverse, sharepoint, Office 365, SAP etc). If you don't want HTTP it is non-business DevOps is an important connector because it enables the business systems to be maintained and tuned.
upvoted 9 times
...
JAVI1771
2 years, 7 months ago
100% connectors are in business by default. If you want to exclude the HTTP action to only be used alone then makes much more sense to move it to Non-Business and leave all of te other ones in Business.
upvoted 5 times
[Removed]
2 years, 7 months ago
coonectors are in non-business by default https://docs.microsoft.com/en-us/power-platform/admin/create-dlp-policy
upvoted 5 times
MrMiniMite
2 years, 6 months ago
Yes, non-business is the default, so the given answer sounds good.
upvoted 7 times
nicknamety
1 year, 6 months ago
The default category can be changed via settings to be either Non Business or Business.
upvoted 1 times
...
...
...
...
ChrisHK
2 years, 7 months ago
I agree
upvoted 1 times
...
...
TamerElsayad
Highly Voted 1 year, 8 months ago
When a new policy is created, by default all connectors are placed in the Non-Business group. From there they can be moved to Business or Blocked based on your preference. For that I would choose : 1- Business to be used alone 2- Non-business for the default ones 3- Blocked
upvoted 14 times
HiJaak
1 year, 2 months ago
Agree with Tamer as to achieve "Solutions that use the HTTP connector must not include any other connectors." the HTTP connector should be moved into a different group. And this group should be "Business" because "Non-business" is the default one and all potentially new connectors will appear here so HTTP could be used with other connectors. If you want to move all connectors to "'Business" leaving HTTP only on "Non-business", then "Business" should also be set as the default group to avoid new connectors get along with HTTP. That's why I would choose as Tamer: 1- Business to be used alone 2- Non-business for the default ones 3- Blocked
upvoted 4 times
...
xanr4711
1 year, 8 months ago
I absolutely agree with Tamer. All conntectors will reside in Non-Business by default. To single out HTTP, the easiest and only way is to exclusively assign it to Business.
upvoted 3 times
...
...
Hamed64
Most Recent 3 weeks, 4 days ago
The Three Main DLP Groups Business Connectors in this group are considered trusted and can share data with each other. Example: SharePoint, Dataverse, Azure DevOps Non-Business Connectors in this group are less trusted or external. They can share data with other non-business connectors, but not with business connectors. Example: Twitter, Gmail, HTTP Blocked Connectors in this group are completely disabled. They cannot be used in any app or flow. Example: Microsoft Forms (if restricted), Facebook, or any connector you want to prohibit.
upvoted 1 times
...
loftuscheek
3 months, 2 weeks ago
HTTP connector non business devops business forms blocked
upvoted 1 times
loftuscheek
3 months, 2 weeks ago
business non business blocked
upvoted 1 times
...
...
naoms
4 months ago
1- Business 2- Non-business 3- Blocked
upvoted 1 times
...
WASSIM2020
5 months, 1 week ago
1- Non-Business 2- Business 3- Block
upvoted 1 times
...
nqthien041292
7 months, 3 weeks ago
When a new policy is created, by default all connectors are placed in the Non-Business group. From there they can be moved to Business or Blocked based on your preference. For that I would choose : 1- Business to be used alone 2- Non-business for the default ones 3- Blocked
upvoted 3 times
...
MrEz
10 months ago
Pivot Description Business (n) Connectors for business-sensitive data. Connectors in this group can't share data with connectors in other groups. Non-Business/ Default (n) Connectors for non-business data, such as personal use data. Connectors in this group can't share data with connectors in other groups. Blocked (n) Blocked connectors can't be used where this policy is applied. http-> business (problem: it would not allow to add any other connector to business according to the requirement) devops -> such as personal use data.
upvoted 1 times
...
OldHand1
1 year, 5 months ago
Has to be Non-Business, Business, Blocked. I can see the argument for making https business, but I think its being over-thought. If you say Business because new connectors (which are not mentioned) are released to non-business by default then you also have to allow for other connectors we might want to use which means you would have to lump ever other connector you want to use as non-business or blocked. You also have to acknowledge the default group can be set to be either. I think this is one where there is the answer MS wants to hear and another perfectly valid answer. DevOps is a business thing, and there are many other valid connectors you would want to use for business.
upvoted 2 times
...
Acrious
1 year, 6 months ago
Business: because you want to make it separate and by default it would have been grouped with all the other connectors as non-business is the default. Being HTTP versus HTTPS has no bearing on the non-business/business selection per se. Non-Business: the default, which would allow this to work, no need to change it to business (which would also let it work) but no need. Blocked: easy choice
upvoted 3 times
...
nicknamety
1 year, 6 months ago
I consider HTTP should be in the non-business category, not so much that is is less safe than HTTPS but because it is an external request passed through the internet. Azure DevOps (a Microsoft product) would be an internally hosted application (that likely has business documents linked/attached to it) and should instead be in the business category.
upvoted 1 times
...
alejoRZ96
1 year, 6 months ago
1. Business 2. Non-Business 3. block All connectors are in non-business by default https://docs.microsoft.com/en-us/power-platform/admin/create-dlp-policy
upvoted 2 times
...
BrahderLau
1 year, 9 months ago
"...When a new policy is created, by default all connectors are placed in the Non-Business group. From there they can be moved to Business or Blocked based on your preference..." https://learn.microsoft.com/en-us/power-platform/admin/dlp-connector-classification You can move everything essential to "Business", while HTTP connector remained as "Non-business" so that it is not able to work with other connectors
upvoted 4 times
...
ricknod
1 year, 10 months ago
This should be: 1. Non-Business 2. Business 3. Blocked SEE: Because child flows share an internal dependency with the HTTP connector, the grouping that admins choose for HTTP connectors in a DLP policy might affect the ability to run child flows in that environment or tenant. Make sure your HTTP connectors are classified in the appropriate group for your child flows to function. If there are any concerns in classifying the connector as Business in shared environments such as the default environment, *** our advice is to classify it as Non-Business *** or to block it. Then, *** create dedicated environments where makers can use HTTP connectors ***, but restrict the maker list so that you can unblock makers from building child flows. From <https://learn.microsoft.com/en-us/power-platform/admin/dlp-connector-classification>
upvoted 3 times
...
KaDevi
1 year, 10 months ago
What is the correct answer?
upvoted 1 times
...
CRMBug
2 years, 1 month ago
1- Non-Business 2- Business 3- Block
upvoted 1 times
...
Icky
2 years, 6 months ago
non-Business, Business, Blocked
upvoted 1 times
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...