mediummultiple choiceObjective-mapped

A healthcare organization stores sensitive patient data in Azure SQL Database. They need to encrypt specific columns containing medical history so that even database administrators with highly privileged roles, such as 'sysadmin', cannot view the plaintext data. Additionally, they need to support complex queries on the encrypted data, including pattern matching and range comparisons. Which encryption technology should they implement?

Question 1mediummultiple choice
Full question →

A healthcare organization stores sensitive patient data in Azure SQL Database. They need to encrypt specific columns containing medical history so that even database administrators with highly privileged roles, such as 'sysadmin', cannot view the plaintext data. Additionally, they need to support complex queries on the encrypted data, including pattern matching and range comparisons. Which encryption technology should they implement?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Always Encrypted with secure enclaves

Always Encrypted with secure enclaves provides column-level encryption and supports rich computations like pattern matching and range queries within the enclave, while preventing database administrators from seeing plaintext data.

B

Distractor review

Transparent Data Encryption (TDE)

TDE encrypts the entire database at rest but automatically decrypts data when read; privileged users can access plaintext data. It does not support queries on encrypted data.

C

Distractor review

Dynamic Data Masking

Dynamic Data Masking obfuscates data from non-privileged users but does not encrypt it; privileged users can see plaintext. It does not support encrypted queries.

D

Distractor review

Row-Level Security

Row-Level Security controls access to rows based on a function but does not encrypt any data; privileged users can still read all rows.

Common exam trap

Common exam trap: authentication is not authorization

Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.

Technical deep dive

How to think about this question

This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.

KKey Concepts to Remember

  • Authentication checks who the user is.
  • Authorization controls what the user is allowed to do after login.
  • Privilege levels affect access to EXEC and configuration commands.
  • AAA, TACACS+ and RADIUS can separate login success from command access.

TExam Day Tips

  • Do not assume successful login means full administrative access.
  • Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
  • Separate login problems from permission problems before choosing the answer.

Related practice questions

Related AZ-500 practice-question pages

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

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this AZ-500 question test?

Authentication checks who the user is.

What is the correct answer to this question?

The correct answer is: Always Encrypted with secure enclaves — Always Encrypted with secure enclaves provides column-level encryption that protects data from database administrators. The 'sysadmin' role cannot access the encryption keys, which are stored outside the database engine. Secure enclaves allow rich computations (including pattern matching and range comparisons) on encrypted data by performing operations inside a secure memory region (enclave). Standard Always Encrypted supports only equality comparisons. Transparent Data Encryption encrypts the entire database at rest but does not protect data from privileged users or allow complex queries on encrypted data. Dynamic Data Masking hides data from non-privileged users but does not encrypt it. Row-Level Security restricts access at the row level but does not encrypt data.

What should I do if I get this AZ-500 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.