Correct Answer is C .
Please refer this article https://community.dynamics.com/blogs/post/?postid=ffff9d86-c304-4fc7-a5c8-ed47e3e64eb5 , which removes the possibility of answer B , Refer conclusion : Conclusion
Setting Searchable property to No, makes the field disappear from the available fields for the Filter configuration, but it won’t hide the field when adding columns to the view. This property has no impact on behaviour of the Global and Quick Find Search.
Option B, "Disable the Search option for the columns," would not be sufficient in this context. Disabling the search option will only prevent users from using that specific column as a search criterion in the search bar. It does not hide the column entirely from views, filters, or reports. Users would still be able to see the column's data, just not search directly on that column.
In contrast, using column-level security to remove read access to all users (option C) effectively makes the column's data invisible to users who don't have the appropriate permissions. This means the data won't appear in views, filters, or reports unless the user has explicit permission to see it, which fits the scenario you've provided much better.
You would still be able to acccess this column through a power automate for example, letting you retrieve confidential data. I think this is not the correct solution.
Instead it should be option C.
Option B only answers second part of question - ensuring it is not visible in search or views.
first part of the question - users should be able to see only address1 in table. witch means other addresses shouldn't be visible if you open table directly, thus C is correct as it answers both parts of the question.
Column-level security allows you to control access to specific columns in a table, ensuring that only authorized users can view or edit those columns. This method is effective in hiding the other address columns from users while still keeping the data intact in the table.
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?
A. Delete the other address columns from the table.
B. Disable the Search option for the columns.
C. Use column-level security to remove read access to all users.
D. Create business rules to hide the other address columns.
The correct answer is B because it directly meets the question’s requirement: hiding additional address columns from views and filters only. Disabling the Searchable option removes these columns from views, filters, and searches, while still allowing access in forms if needed.
Option C (column-level security) would completely block access to these columns everywhere, which is more restrictive than necessary for this scenario. Thus, Option B provides a simpler, more targeted solution.
I was convinced it was C, but I believe you are right, actually, because the question wouldn't have specified, “… when creating views and filters…” otherwise.
Use column-level security to remove read access to all users is the correct solution. It allows for granular control of field-level visibility, ensuring that users only see the address1 fields and cannot access or filter the other address columns.
The correct answer is C. Use column-level security to remove read access to all users.
Column-level security in Power Apps allows you to control who has access to view data in specific columns. By removing read access to the other address columns for all users, you can ensure that these columns are not visible when users are creating views and filters. This does not delete the columns or affect their functionality, it simply hides them from users who do not have the necessary permissions.
Correct answer is C. Enable column-level security and don't set up any profiles. Any users not defined in these profiles won’t have access to the column in question.
Enable Column Security:
Sign in to Power Apps.
Select Dataverse > Tables.
Choose the relevant table.
Under Schema, click Columns.
In the Columns list, select the desired column.
Expand Advanced options, and then under General, enable or disable Enable column security1.
Configure Security Profiles:
Create one or more security profiles to manage access permissions.
Each profile can grant different permissions at the column level:
Read: Read-only access to the column’s data.
Create: Users or teams can add data to this column when creating a row.
Update: Users or teams can update the column’s data after it has been created.
Assign these profiles to specific users or teams based on your requirements.
Any users not defined in these profiles won’t have access to the column. https://learn.microsoft.com/en-us/power-platform/admin/field-level-security
Read last sentence in Configure column permissions.
This section is not available anymore. Please use the main Exam Page.PL-200 Exam Questions
Log in to ExamTopics
Sign in:
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.
ShrikrishnaG
Highly Voted 1Â year, 10Â months agoinscho
1Â year, 9Â months agoAhmedRN
Highly Voted 2Â years, 1Â month agoEnzor
4Â months, 2Â weeks agoNewb007
2Â years, 1Â month agoskallig
Most Recent 2Â months, 2Â weeks agoDoubleO7
2Â months, 4Â weeks agoPaula0485
3Â months, 1Â week ago0521f7a
3Â months, 2Â weeks agokillionb12
4Â months, 3Â weeks agoABDFormacion
5Â months, 2Â weeks agoRangelPrime
6Â months agotheTeknician
4Â months, 3Â weeks agofec067d
6Â months, 4Â weeks agoRaviA
7Â months ago[Removed]
8Â months, 4Â weeks ago5f14337
9Â months, 2Â weeks agogina_the_boss
10Â months agonqthien041292
11Â months agob304b2c
11Â months, 4Â weeks agob304b2c
11Â months, 4Â weeks agob304b2c
11Â months, 4Â weeks agojkaur
1Â year ago