Independence Day Deal! Unlock 25% OFF Today – Limited-Time Offer - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft Exam PL-200 Topic 2 Question 86 Discussion

Actual exam question for Microsoft's PL-200 exam
Question #: 86
Topic #: 2
[All PL-200 Questions]

A company uses Power Apps.

Users must be able to view only the address1 columns in the Account table.

You need to ensure other address columns are not visible to users when creating views and filters.

What should you do?

Show Suggested Answer Hide Answer
Suggested Answer: A

Contribute your Thoughts:

Dean
1 months ago
I'm torn between B and D, but I think I'd lean towards D. Removing read access is the surest way to keep those pesky users out of the other address columns. Wouldn't want them to get any funny ideas, you know?
upvoted 0 times
Reita
5 days ago
Yeah, D is the safest bet. We need to make sure those address columns stay hidden.
upvoted 0 times
...
Thomasena
9 days ago
Disabling the Search option might not be enough. D is the way to go for sure.
upvoted 0 times
...
Shaun
10 days ago
I agree, D seems like the most secure choice. We don't want users seeing what they shouldn't.
upvoted 0 times
...
Annalee
11 days ago
I think D is the best option. It's important to restrict access to those columns.
upvoted 0 times
...
...
Jaime
1 months ago
Option A seems a bit too simple. Disabling the Search option won't really hide the other columns, it'll just make them a bit harder to find. Gotta go with a more comprehensive solution here.
upvoted 0 times
...
Dulce
1 months ago
Option C is just too drastic. Deleting the other address columns? That's like throwing the baby out with the bathwater. I'd rather hide them from view than get rid of them entirely.
upvoted 0 times
Carin
14 days ago
A: That could work, but I still prefer just hiding the columns from view.
upvoted 0 times
...
Melinda
22 days ago
B: I think using column-level security to remove read access is the way to go.
upvoted 0 times
...
Emeline
24 days ago
A: I agree, deleting the columns seems extreme.
upvoted 0 times
...
...
Sunny
2 months ago
I'd go with Option D. Using column-level security to remove read access to all users is a more robust and secure solution. Don't want any curious users peeking at the other address columns!
upvoted 0 times
Pauline
1 months ago
Definitely, using column-level security is the way to go to restrict access to certain columns.
upvoted 0 times
...
Susana
1 months ago
Yeah, Option D seems like the most secure way to handle this.
upvoted 0 times
...
Ilene
2 months ago
I agree, Option D is the best choice to ensure data security.
upvoted 0 times
...
...
Lucia
2 months ago
Option B seems like the best choice. Creating business rules to hide the other address columns will ensure users can only see the address1 column, without permanently deleting the other columns.
upvoted 0 times
Victor
1 months ago
Yes, creating business rules will help maintain data integrity while still allowing users to view the necessary information.
upvoted 0 times
...
Emogene
2 months ago
I agree, option B is the most appropriate solution in this case.
upvoted 0 times
...
...
Jonell
3 months ago
I'm not sure about that. Maybe we could also consider option B) Create business rules to hide the other address columns.
upvoted 0 times
...
Jules
3 months ago
I agree with Nikita. It makes sense to restrict read access to those columns.
upvoted 0 times
...
Nikita
3 months ago
I think the answer is D) Use column-level security to remove read access to all users.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77