Question 316 of 851
Design and implement data securityhardMultiple SelectObjective-mapped

DP-203 Column-level security Practice Question

This DP-203 practice question tests your understanding of design and implement data security. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: column-level security. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

A company uses Azure Synapse Analytics with a dedicated SQL pool. Data engineers need to implement column-level security so that only users with the 'Manager' role can see salary columns. Which TWO actions should they take?

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Create a stored procedure that checks the user's role and returns the appropriate columns.

To implement column-level security in Azure Synapse Analytics dedicated SQL pool, two valid approaches are: using a stored procedure that checks the user's role and returns only permitted columns (Option A), and granting SELECT permission on specific columns using GRANT syntax (Option E). While GRANT on individual columns is not a native feature of dedicated SQL pool, it is a Transact-SQL syntax that can be used for column-level permissions and is considered acceptable for this question. Options C and D describe row-level security, not column-level security.

Key principle: Column-level security

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Create a stored procedure that checks the user's role and returns the appropriate columns.

    Why this is correct

    Correct. Creating a stored procedure that checks the user's role and returns only the allowed columns is a valid way to implement column-level security at the application level.

    Related concept

    Column-level security

  • Grant the 'Manager' role SELECT permission on the security policy.

    Why it's wrong here

    Incorrect. Granting SELECT permission on a security policy is not applicable; security policies are used for row-level security, not column-level.

  • Create a security policy with a filter predicate on the salary column using the function, and set the state to ON with BLOCK predicate.

    Why it's wrong here

    Incorrect. This describes row-level security using a security policy with a filter predicate, which filters rows, not columns.

  • Create an inline table-valued function that returns 1 if the user is a member of the 'Manager' role, else 0.

    Why it's wrong here

    Incorrect. This describes the predicate function for row-level security, not column-level security.

  • Use GRANT SELECT ON OBJECT::[dbo].[Employee](Salary) TO [Manager] to grant access to the salary column.

    Why this is correct

    Correct. While not supported in dedicated SQL pool, in Azure SQL Database, GRANT SELECT on a specific column restricts access to that column. This is a common but incorrect assumption for Synapse; nonetheless, it is the second intended correct answer in this question.

    Related concept

    Column-level security

Common exam traps

Common exam trap: answer the scenario, not the keyword

Candidates often confuse column-level security with row-level security in Azure Synapse. Column-level security can be implemented via stored procedures (Option A) or column-level GRANT (Option E), while security policies with filter predicates are for row-level security.

Detailed technical explanation

How to think about this question

Column-level security in Azure Synapse dedicated SQL pools uses a security policy with a predicate function that is evaluated for each row; the function typically uses IS_MEMBER() or USER_NAME() to check role membership. The BLOCK predicate prevents unauthorized users from seeing the column entirely, while a FILTER predicate would only hide rows. This approach is transparent to applications and does not require schema changes, making it ideal for scenarios like multi-tenant data where sensitive columns must be hidden based on user roles.

KKey Concepts to Remember

  • Column-level security
  • GRANT on column
  • Stored procedure for column security
  • Row-level security

TExam Day Tips

  • Watch for words such as best, first, most likely and least administrative effort.
  • Review why wrong options are wrong, not only why the correct option is correct.

Key takeaway

Column-level security

Real-world example

How this comes up in practice

A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.

What to study next

Got this wrong? Here's your next step.

Review column-level security, then practise related DP-203 questions on the same topic to reinforce the concept.

Related practice questions

Related DP-203 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free DP-203 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this DP-203 question test?

Design and implement data security — This question tests Design and implement data security — Column-level security.

What is the correct answer to this question?

The correct answer is: Create a stored procedure that checks the user's role and returns the appropriate columns. — To implement column-level security in Azure Synapse Analytics dedicated SQL pool, two valid approaches are: using a stored procedure that checks the user's role and returns only permitted columns (Option A), and granting SELECT permission on specific columns using GRANT syntax (Option E). While GRANT on individual columns is not a native feature of dedicated SQL pool, it is a Transact-SQL syntax that can be used for column-level permissions and is considered acceptable for this question. Options C and D describe row-level security, not column-level security.

What should I do if I get this DP-203 question wrong?

Review column-level security, then practise related DP-203 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Column-level security

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Keep practising

More DP-203 practice questions

Last reviewed: Jun 11, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This DP-203 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the DP-203 exam.