The correct answer is to use SAS tokens or managed identities for authentication, and rely on default encryption at rest and in transit. This combination works because Azure Event Hubs automatically encrypts data at rest using Azure Storage Service Encryption and secures data in transit with TLS, so no additional configuration is needed for encryption. For authorization, shared access signatures (SAS) or managed identities provide fine-grained control over which applications can publish messages, without requiring network-level restrictions. On the AZ-204 exam, this question tests your understanding of the separation between encryption (a built-in, always-on feature) and authorization (an explicit access control mechanism). A common trap is confusing network security tools like firewalls or private endpoints with authorization—they control connectivity, not identity-based permissions. Remember the memory tip: “Encryption is automatic; authorization is explicit.”
AZ-204 Implement Azure security Practice Question
This AZ-204 practice question tests your understanding of implement azure 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. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. 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.
You are designing a solution that uses Azure Event Hubs to ingest telemetry data. The data must be encrypted at rest and in transit. Additionally, you need to ensure that only authorized applications can publish messages to the event hub. Which combination of features should you use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use SAS tokens or managed identities for authentication, and rely on default encryption at rest and in transit.
Option D is correct because Event Hubs enables encryption at rest by default (Azure Storage Service Encryption) and in transit via TLS, and uses shared access signatures (SAS) or managed identities for authorization. Option A is wrong because firewall restricts network access, not authorization. Option B is wrong because private endpoints are for network isolation. Option C is wrong because managed identity provides authorization, but encryption at rest is default.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use managed identities for applications and enable encryption at rest using customer-managed keys.
Why it's wrong here
Encryption at rest is default; managed identities are for auth, but the question asks for both encryption and authorization.
✓
Use SAS tokens or managed identities for authentication, and rely on default encryption at rest and in transit.
Why this is correct
Event Hubs encrypts at rest by default and in transit via TLS; SAS or managed identities authorize publishers.
Related concept
Authentication checks who the user is.
✗
Use Azure Private Link to connect applications to Event Hubs.
Why it's wrong here
Private Link provides network isolation, not authorization.
✗
Enable Azure Firewall on the Event Hubs namespace and use IP filtering.
Why it's wrong here
Firewall controls network access, not authorization.
Common exam traps
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.
Detailed technical explanation
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.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related AZ-204 questions on access control and AAA configuration.
Implement Azure security — This question tests Implement Azure security — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Use SAS tokens or managed identities for authentication, and rely on default encryption at rest and in transit. — Option D is correct because Event Hubs enables encryption at rest by default (Azure Storage Service Encryption) and in transit via TLS, and uses shared access signatures (SAS) or managed identities for authorization. Option A is wrong because firewall restricts network access, not authorization. Option B is wrong because private endpoints are for network isolation. Option C is wrong because managed identity provides authorization, but encryption at rest is default.
What should I do if I get this AZ-204 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related AZ-204 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
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 →
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.
This AZ-204 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 AZ-204 exam.
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.
Sign in to join the discussion.