nerdexam
Microsoft

PL-600 · Question #228

A local bank uses Microsoft Power Platform apps to store customer data. The bank IT director discovers that all employees can see the social security numbers of their customers. The IT team does not…

The correct answer is B. Create a column-level security profile and add users. D. Enable column-level security for the social security number column. To restrict access to customer social security numbers to only the vice president of finance, you must enable column-level security for that specific column and then create a security profile to define permissions and assign the authorized users.

Submitted by cyberguy42· Apr 18, 2026Architect a solution

Question

A local bank uses Microsoft Power Platform apps to store customer data. The bank IT director discovers that all employees can see the social security numbers of their customers. The IT team does not understand how column-level security works and needs help with the design. You need to recommend a solution to the bank that meets the following requirements: - The system must restrict access to customer social security numbers to the vice president of finance only. - The vice president of finance must be able to read and update customer social security numbers. Which two actions should you recommend? Each correct answer presents part of the solution. NOTE: Each correct selection is worth one point.

Options

  • ASet the values for the read permission and for the update permission for social security number to
  • BCreate a column-level security profile and add users.
  • CEnable column-level security for the member table.
  • DEnable column-level security for the social security number column.
  • ECreate a business unit.

How the community answered

(57 responses)
  • A
    9% (5)
  • B
    84% (48)
  • C
    5% (3)
  • E
    2% (1)

Why each option

To restrict access to customer social security numbers to only the vice president of finance, you must enable column-level security for that specific column and then create a security profile to define permissions and assign the authorized users.

ASet the values for the read permission and for the update permission for social security number to

Permissions are set within a column-level security profile, not directly on the column itself in this manner, making this choice an incomplete and vague step.

BCreate a column-level security profile and add users.Correct

After enabling column-level security on a specific column, a column-level security profile must be created to define the specific permissions (read, update) for that column and then assign the designated users to this profile. This allows granular control over who can perform which actions on the secured column.

CEnable column-level security for the member table.

Enabling column-level security for an entire table is incorrect; column security is designed to restrict access to specific columns, not all columns in a table.

DEnable column-level security for the social security number column.Correct

The first step in implementing column-level security for a specific data field, such as the social security number, is to enable this security feature directly on that particular column within the Dataverse table definition. This action flags the column as requiring restricted access based on defined security profiles.

ECreate a business unit.

Business units are used for row-level security and hierarchical data access, not for restricting access to individual columns within a table.

Concept tested: Dataverse column-level security implementation

Source: https://learn.microsoft.com/en-us/power-apps/maker/data-platform/field-level-security

Topics

#Power Platform Security#Dataverse#Column-Level Security#Field Security Profile

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PL-600 Practice