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 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?
To ensure that users can only view the address1 columns in the Account table and that the other address columns are not visible when creating views and filters, column-level security should be implemented. This feature allows the restriction of read access at the column level, thereby making specific columns invisible to users who do not have the necessary permissions. This approach ensures the columns are hidden from views and filters without deleting them from the table or affecting the search options.
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.
Is should be B. When you uncheck Searchable option for a field, it does not show in views or filters.
I think your right.
C is for sure correct.
Just created a non-searchable column. You can't add it as a filter but you CAN add the column to the view.
Column-level security is typically used to restrict access to specific columns within a table, rather than removing read access to an entire table. It is designed to control access to sensitive data and ensure that users can only access certain columns based on their permissions or roles. While it provides a robust mechanism for securing sensitive data within a table, it is not intended for the complete removal of read access to an entire table for all users.
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.
can't be C because of the "all users", otherwise both could be correct. so B is correct
Vote C
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.
seems C
B it's not possible with c https://learn.microsoft.com/en-us/power-platform/admin/field-level-security
That's interesting that this is an exam question. With the onset of the new UI, this was one point i raised as a bug and product idea (for me it is a UI bug). Because the ability to add non-searchable fields to the view, eventually, enables the user to 'search' by it as a filter. non-searchable is a difficult thing in such a context (I would love this be removed as it clutters the edit view area with many unused fields... bad user experience...)
in the old ui it was 100% B. Disable the Search option for the columns. with the new UI c) may be a way but... means that you would have to use FLS for every OOTB field to be hidden / shown to let the user only see the fields needed. this is a bit much work.
I believe the wording here is incorrect. What they mean in the question is "filters in views". Then the answer B makes sense.
From Bing Chat Enterprise the answer is C: You should C. Use column-level security to remove read access to all users for the other address columns. This will ensure that these columns are not visible to users when creating views and filters. Deleting the columns from the table (option A) could potentially impact other areas of the system where these columns are used. Disabling the Search option for the columns (option B) would not prevent them from being visible in views and filters. Business rules (option D) are typically used for form logic and wouldn’t necessarily hide the columns in views and filters.
although the selected answer happens to be correct, please do not reference "Bing Chat" nor "Bard" nor "ChatGPT" as if it's the source of truth #..#; 'cause it's not!
ChatGPT: Option B suggests disabling the Search option for the columns. Disabling the Search option would prevent users from using those columns in search queries or filters, but it would not make the columns themselves invisible. Users would still be able to see the columns and their data if they accessed the table or view directly. It does not provide the necessary security to hide sensitive information from users who should not have access. To ensure that users cannot even see the other address columns in the Account table when creating views and filters, column-level security (Option C) is the appropriate approach. This method restricts access to the columns entirely for users who shouldn't have permission, effectively hiding them from view and ensuring data security.
The Answer not on the selected Since when use one address go to left navigation and click the three dots ... then add to selection section and deleted the default all address,
There is no Answer here, Since when want to use only Address 1 first go to the left navigation and front of address 1 click the three dots ... then click add to selection section then remove the default all addresses on selected section so set all addresses like this if need may need address 2 or 3 and so on