Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft PL-200 Exam - 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

by Lashaun at Sep 14, 2024, 06:14 PM

Limited Time Offer

25%

Off

Get Premium PL-200 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Paola
4 months ago
Disabling search won't help much, just a band-aid fix.
upvoted 0 times
...
Florencia
4 months ago
Wait, can we really hide columns with business rules?
upvoted 0 times
...
Wilson
4 months ago
Column-level security (D) seems like the safest bet.
upvoted 0 times
...
Buffy
4 months ago
I disagree, deleting columns isn't a good idea.
upvoted 0 times
...
Angelo
5 months ago
Option B sounds right, business rules can do that!
upvoted 0 times
...
Herman
5 months ago
Deleting the columns seems too extreme; what if we need them later? I think we should focus on hiding them instead.
upvoted 0 times
...
Lucina
5 months ago
I feel like disabling the search option isn't enough to restrict visibility. It seems like a temporary fix.
upvoted 0 times
...
Shenika
5 months ago
I think creating business rules might be the right approach since it allows us to hide specific columns without deleting them.
upvoted 0 times
...
Loren
5 months ago
I remember we discussed column-level security in class, but I'm not entirely sure if it applies here.
upvoted 0 times
...
Lavelle
5 months ago
Deleting the other address columns seems like the simplest solution, but I'm not sure if that's the best approach. We might need that data for other purposes, so I'd want to explore the other options first before resorting to that.
upvoted 0 times
...
Emogene
5 months ago
Okay, I think I've got this. Creating business rules to hide the other address columns sounds like the best approach. That way, we can keep the data intact but ensure users only see what they need to. I'll make sure to double-check the details on how to implement that in Power Apps.
upvoted 0 times
...
Tula
5 months ago
Hmm, I'm a bit unsure about this one. Disabling the search option or using column-level security both seem like potential solutions, but I'm not sure if they would fully hide the other columns from the user interface. I'll need to think this through carefully.
upvoted 0 times
...
Cary
6 months ago
This seems like a straightforward question about controlling column visibility in Power Apps. I think the key is to find a way to hide the other address columns without deleting them, since we still need to maintain the data.
upvoted 0 times
...
Dean
10 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
9 months ago
Yeah, D is the safest bet. We need to make sure those address columns stay hidden.
upvoted 0 times
...
Thomasena
9 months ago
Disabling the Search option might not be enough. D is the way to go for sure.
upvoted 0 times
...
Shaun
9 months ago
I agree, D seems like the most secure choice. We don't want users seeing what they shouldn't.
upvoted 0 times
...
Annalee
9 months ago
I think D is the best option. It's important to restrict access to those columns.
upvoted 0 times
...
...
Jaime
10 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
10 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
9 months ago
A: That could work, but I still prefer just hiding the columns from view.
upvoted 0 times
...
Melinda
10 months ago
B: I think using column-level security to remove read access is the way to go.
upvoted 0 times
...
Emeline
10 months ago
A: I agree, deleting the columns seems extreme.
upvoted 0 times
...
...
Sunny
11 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
10 months ago
Definitely, using column-level security is the way to go to restrict access to certain columns.
upvoted 0 times
...
Susana
10 months ago
Yeah, Option D seems like the most secure way to handle this.
upvoted 0 times
...
Ilene
11 months ago
I agree, Option D is the best choice to ensure data security.
upvoted 0 times
...
...
Lucia
11 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
10 months ago
Yes, creating business rules will help maintain data integrity while still allowing users to view the necessary information.
upvoted 0 times
...
Emogene
11 months ago
I agree, option B is the most appropriate solution in this case.
upvoted 0 times
...
...
Jonell
11 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
12 months ago
I agree with Nikita. It makes sense to restrict read access to those columns.
upvoted 0 times
...
Nikita
12 months ago
I think the answer is D) Use column-level security to remove read access to all users.
upvoted 0 times
...

Save Cancel