Question 1mediummultiple choice
Full question →mediummultiple choiceObjective-mapped
A company uses Azure SQL Database and wants to protect sensitive data (e.g., credit card numbers) from database administrators. They require that the data is encrypted at rest and in transit, and only a client application using a specific driver can decrypt it. Which 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
Distractor review
Transparent Data Encryption (TDE)
TDE encrypts the database at rest, but the data is decrypted for the server process, so database administrators with access to the server can view plaintext data. It does not protect against DBAs.
B
Best answer
Always Encrypted
Always Encrypted encrypts sensitive columns at the client side, ensuring that the data is never exposed in plaintext to the server or DBAs. Only the client application with the column master key can decrypt the data.
C
Distractor review
Dynamic Data Masking (DDM)
DDM obfuscates data to non-privileged users when querying, but the data is still stored in plaintext. It does not provide encryption at rest or protect against DBAs who can see unmasked data.
D
Distractor review
Row-Level Security (RLS)
RLS restricts access to rows based on user context, but it does not encrypt data. DBAs with elevated permissions can bypass RLS policies.
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.
Question 1
A DevOps team wants Defender for Cloud to identify secrets exposed in GitHub repositories. What should be configured?
Question 2
A public web application should be protected from OWASP-style attacks and network-layer DDoS attacks. Which two Azure services are most relevant?
Question 3
A Sentinel scheduled rule runs every 5 minutes and looks back 1 hour. Analysts see repeated alerts for the same event. Which change best prevents duplicate detections without missing late-arriving logs?
Question 4
A SOC analyst needs a Sentinel query that detects multiple failed sign-ins followed by a successful sign-in for the same user. Which table is the best primary source?
Question 5
A Sentinel watchlist contains high-value administrator accounts. Which KQL pattern best uses it in a detection rule?
Question 6
A SOC wants a Sentinel rule to include account, host, and IP entities so analysts can pivot during investigation. What should be configured in the analytics rule?
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 — Always Encrypted is a client-side encryption technology that ensures sensitive data is encrypted on the server and can only be decrypted by authorized client applications using a designated driver (e.g., .NET Framework). Database administrators cannot view the plaintext data because they do not have access to the column master key. Transparent Data Encryption (TDE) encrypts the entire database at rest but does not protect data from administrators. Dynamic Data Masking (DDM) masks data from non-privileged users but does not encrypt it. Row-Level Security (RLS) restricts access at the row level but does not encrypt columns.
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.