Question 793 of 1,000
Secure compute, storage, and databaseshardMultiple ChoiceObjective-mapped

Quick Answer

The correct answer is to rely on Azure Cosmos DB’s automatic encryption at rest, enforce TLS for data in transit, and implement row-level security through application code. Encryption at rest is enabled by default in Cosmos DB, using Azure Storage Service Encryption to protect PII without any manual configuration, while transport layer security (TLS) is enforced to secure data in transit. Row-level security, however, is not a native database feature in Cosmos DB; it must be built into the application layer using user-defined functions or stored procedures that filter query results based on the authenticated user’s role. On the AZ-500 exam, this question tests your ability to distinguish between Azure services—common traps include selecting Always Encrypted or Dynamic Data Masking, which are SQL Server-specific, or Azure Disk Encryption, which applies only to VM disks. Remember the memory tip: “Cosmos encrypts by default, TLS for the road, row security is code you load.”

AZ-500 Secure compute, storage, and databases Practice Question

This AZ-500 practice question tests your understanding of secure compute, storage, and databases. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 security solution for Azure Cosmos DB that stores Personally Identifiable Information (PII). You need to encrypt data at rest and in transit. You also need to implement row-level security to restrict access based on user role. What should you configure?

Question 1hardmultiple choice
Full question →

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

Encryption at rest is automatically enabled; enforce TLS for transit; implement row-level security via application code.

Option D is correct because Cosmos DB encryption at rest is enabled by default and enforced through the service, transport encryption uses TLS, and row-level security is implemented using user-defined functions or stored procedures in the application layer. Option A is wrong because Always Encrypted is for SQL Server. Option B is wrong because Azure Disk Encryption is for VMs. Option C is wrong because Dynamic Data Masking is for SQL Server.

Key principle: Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.

Answer analysis

Option-by-option breakdown

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

  • Enable Azure Disk Encryption on the Cosmos DB account.

    Why it's wrong here

    Azure Disk Encryption is for VMs, not Cosmos DB.

  • Enable Always Encrypted and configure column encryption.

    Why it's wrong here

    Always Encrypted is not supported in Azure Cosmos DB.

  • Use Dynamic Data Masking to restrict sensitive data.

    Why it's wrong here

    Dynamic Data Masking is a SQL Server feature, not Cosmos DB.

  • Encryption at rest is automatically enabled; enforce TLS for transit; implement row-level security via application code.

    Why this is correct

    Cosmos DB encrypts data at rest by default, enforces TLS, and row-level security must be implemented in the application.

    Related concept

    CIDR notation defines the prefix length.

Common exam traps

Common exam trap: usable hosts are not the same as total addresses

Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.

Detailed technical explanation

How to think about this question

Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.

KKey Concepts to Remember

  • CIDR notation defines the prefix length.
  • Block size helps identify subnet boundaries.
  • Network and broadcast addresses are not usable hosts in normal IPv4 subnets.
  • The required host count determines the smallest suitable subnet.

TExam Day Tips

  • Write the block size before choosing the subnet.
  • Check whether the question asks for hosts, subnets or a specific address range.
  • Do not confuse /24, /25, /26 and /27 host counts.

Key takeaway

Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related AZ-500 subnetting questions on CIDR, address ranges, and subnet selection.

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.

Practice this exam

Start a free AZ-500 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 AZ-500 question test?

Secure compute, storage, and databases — This question tests Secure compute, storage, and databases — CIDR notation defines the prefix length..

What is the correct answer to this question?

The correct answer is: Encryption at rest is automatically enabled; enforce TLS for transit; implement row-level security via application code. — Option D is correct because Cosmos DB encryption at rest is enabled by default and enforced through the service, transport encryption uses TLS, and row-level security is implemented using user-defined functions or stored procedures in the application layer. Option A is wrong because Always Encrypted is for SQL Server. Option B is wrong because Azure Disk Encryption is for VMs. Option C is wrong because Dynamic Data Masking is for SQL Server.

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

Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related AZ-500 subnetting questions on CIDR, address ranges, and subnet selection.

What is the key concept behind this question?

CIDR notation defines the prefix length.

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 AZ-500 practice questions

Last reviewed: Jun 20, 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 AZ-500 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-500 exam.