Browse Certification Practice Tests by Exam Family

Microsoft AZ-802: Manage Storage and File Services

Try 10 focused Microsoft AZ-802 questions on Manage Storage and File Services, with explanations, then continue with IT Mastery.

Open the matching IT Mastery practice page for timed mocks, topic drills, progress tracking, explanations, and full practice.

Try Microsoft AZ-802 on Web View full Microsoft AZ-802 practice page

Topic snapshot

FieldDetail
Exam routeMicrosoft AZ-802
Topic areaManage Storage and File Services
Blueprint weight9%
Page purposeFocused sample questions before returning to mixed practice

How to use this topic drill

Use this page to isolate Manage Storage and File Services for Microsoft AZ-802. Work through the 10 questions first, then review the explanations and return to mixed practice in IT Mastery.

PassWhat to doWhat to record
First attemptAnswer without checking the explanation first.The fact, rule, calculation, or judgment point that controlled your answer.
ReviewRead the explanation even when you were correct.Why the best answer is stronger than the closest distractor.
RepairRepeat only missed or uncertain items after a short break.The pattern behind misses, not the answer letter.
TransferReturn to mixed practice once the topic feels stable.Whether the same skill holds up when the topic is no longer obvious.

Blueprint context: 9% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.

Sample questions

These questions are original IT Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.

Question 1

Topic: Manage Storage and File Services

A company uses Azure File Sync to sync a branch file server with an Azure file share. After a new server endpoint is added, users report that some files are not appearing at the branch. Administrators need a single monitoring view that can distinguish sync activity, cloud endpoint health, server endpoint health, and Azure File Sync agent issues. Which design best fits this requirement?

Options:

  • A. Check Event Viewer only on the branch server

  • B. Review only Azure file share capacity metrics

  • C. Review Storage Sync Service health in the Azure portal

  • D. Use Microsoft Defender for Cloud recommendations

Best answer: C

Explanation: Azure File Sync health should be monitored from the Storage Sync Service because that service owns the sync topology. Its health views let administrators inspect sync groups, cloud endpoints, server endpoints, registered servers, and agent-related status from one Azure-centered location. This directly supports troubleshooting whether the issue is with the Azure file share endpoint, a specific server endpoint, sync processing, or the Azure File Sync agent on a registered Windows Server. Local logs can help with deeper troubleshooting, but they do not provide the complete service-level view required in the scenario.

  • Azure file share capacity metrics can show storage usage or transactions, but they do not identify server endpoint or agent health.
  • Event Viewer on one server may expose local agent errors, but it misses cloud endpoint and other registered-server status.
  • Defender for Cloud focuses on security posture and recommendations, not Azure File Sync topology health.

Question 2

Topic: Manage Storage and File Services

A Windows Server file server uses File Server Resource Manager (FSRM) to block .pst files under a departmental share. Users report they can still save .pst files in one project folder.

Exhibit: FSRM configuration summary

PathFSRM objectMode / setting
D:\Shares\DeptFile screenActive, blocks *.pst
D:\Shares\Dept\LegalFile screen exceptionAllows *.pst
FSRM serviceService stateRunning

What is the most likely root cause?

Options:

  • A. The file screen is configured in passive mode

  • B. The child exception overrides the parent screen

  • C. NTFS permissions bypass FSRM screening

  • D. The FSRM service is not running

Best answer: B

Explanation: FSRM file screens can be applied at a parent folder and inherited by subfolders, but a file screen exception creates an explicit exception for a child path. In this case, the parent folder has an active screen that blocks *.pst, and the FSRM service is running, so the blocking rule is available. The key diagnostic clue is the file screen exception on D:\Shares\Dept\Legal that allows *.pst. That exception explains why the governance rule works generally but not in that folder. To enforce the requirement there, remove or modify the exception, or apply a more appropriate screen at that path.

  • Passive mode does not fit because the exhibit shows the parent screen is active, which should block matching files.
  • Stopped service does not fit because the exhibit shows FSRM is running.
  • NTFS bypass is misleading because NTFS permissions control access, not whether FSRM file screen rules apply.

Question 3

Topic: Manage Storage and File Services

A company migrated a finance share to a Windows Server 2022 file server that is managed through Azure Arc. Finance users connect over a site-to-site VPN by using \\files.contoso.com\Finance. They can open files but cannot create new files. The goal is to restore write access without broadening access beyond the Finance groups.

Evidence:

CheckResult
Name resolutionfiles.contoso.com resolves to FS1
TCP 445Succeeds from client subnets
SMB share ACLDomain Users: Read, FileAdmins: Full Control
NTFS ACLFinance_RW: Modify, inherited to subfolders
User membershipAffected users are in Finance_RW

Options:

  • A. Grant Domain Users Full Control on the share.

  • B. Disable NTFS inheritance on the finance folder.

  • C. Grant Finance_RW Change on the SMB share.

  • D. Change the DNS record for files.contoso.com.

Best answer: C

Explanation: SMB access is controlled by the most restrictive combination of share permissions and NTFS permissions. The evidence shows that name resolution and TCP 445 connectivity are working, and the NTFS ACL already grants Finance_RW Modify with inheritance to child folders. The blocking layer is the SMB share ACL because Domain Users has only Read and the write group has no Change permission at the share level.

Adding Finance_RW Change to the share aligns the share ACL with the NTFS design and keeps access group-based. Broad share permissions or per-user NTFS changes are unnecessary and weaken the least-privilege design.

  • Inheritance change is unnecessary because the NTFS Modify permission is already inherited to subfolders.
  • DNS change does not fit because the alias already resolves to the intended file server.
  • Broad share control may bypass the intended share-level boundary and does not meet the Finance-only constraint.

Question 4

Topic: Manage Storage and File Services

A Windows Server administrator is configuring Storage Replica for block-level replication from SRV1 in SiteA to SRV2 in SiteB. The partnership creation fails after validation.

Validation summary:

ItemSource SRV1Destination SRV2
Data volume2,048 GB2,000 GB
Log volume32 GB32 GB
File systemNTFSNTFS
Network testPassedPassed

What is the most likely root cause?

Options:

  • A. The network path is blocking SMB traffic.

  • B. The log volumes must match the data volumes.

  • C. The destination data volume is too small.

  • D. The data volumes must use ReFS.

Best answer: C

Explanation: Storage Replica performs block-level replication, so the destination data volume must be prepared to receive all replicated blocks from the source. In this scenario, the network test passed, the file system is supported, and the log volumes are present and equal in size. The decisive validation clue is that the destination data volume is 2,000 GB while the source data volume is 2,048 GB. The administrator should expand or recreate the destination data volume so it is at least as large as the source before creating the replication partnership.

The key takeaway is that Storage Replica volume sizing is validated before replication starts; a healthy network cannot compensate for an undersized destination data volume.

  • Log volume sizing is not the issue because the log volumes are separate and already equal at 32 GB.
  • ReFS requirement is incorrect because Storage Replica supports NTFS for replicated data volumes.
  • SMB blocking is not supported by the evidence because the validation summary shows the network test passed.

Question 5

Topic: Manage Storage and File Services

A company uses a DFS Namespace with DFS Replication to host departmental shares on Windows Server file servers in three offices. The company wants to modernize the file service by using Azure as the cloud-backed copy, keep local low-latency access in each office, preserve NTFS permissions, and minimize user-facing path changes. Which design is the best fit?

Options:

  • A. Map all users directly to a single Azure file share

  • B. Move the data to Azure Blob Storage and replace DFS paths

  • C. Deploy Azure File Sync and keep DFS Namespace referrals to synced servers

  • D. Deploy DFS Replication to Azure IaaS file servers

Best answer: C

Explanation: Azure File Sync is the best modernization path when DFS-based file data still needs Windows Server file-service behavior at branch or office locations. You create an Azure file share as the cloud endpoint, install the Azure File Sync agent on the file servers, and add server endpoints for the local share paths. DFS Replication can then be retired for that data set after migration, while DFS Namespace can continue to provide familiar paths and referrals to the local synced servers. This keeps NTFS ACLs and SMB access patterns while adding a cloud-backed authoritative copy and optional cloud tiering. A direct Azure file share can work for some users, but it does not provide the same local cache design for each office.

  • Blob replacement fails because Azure Blob Storage is object storage and does not preserve the SMB file-server experience for DFS users.
  • DFS-R to Azure VMs keeps the older replication model instead of modernizing with Azure File Sync and an Azure file share cloud endpoint.
  • Direct single share mapping misses the requirement for local low-latency access in each office.

Question 6

Topic: Manage Storage and File Services

A Windows Server file server hosts \\FS1\Departments, which contains subfolders for HR, Legal, and Research. Members of ResearchUsers should access only the Research folder and should not see other department names. A test Research user can open Research, sees HR and Legal in the share root, and receives Access Denied when opening them. What is the most likely root cause?

Options:

  • A. The share lacks Offline Files configuration

  • B. SMB encryption is disabled on the share

  • C. Access-based enumeration is not enabled on the share

  • D. The client is using an unsupported SMB dialect

Best answer: C

Explanation: Access-based enumeration controls whether users can see files and folders for which they do not have access. In this scenario, NTFS permissions are already preventing the Research user from opening HR and Legal, but the folder names are still visible at the share root. That symptom points to enumeration exposure, not failed authorization. Enabling access-based enumeration on the SMB share, together with correct NTFS ACLs on each department folder, supports the intended access while hiding unrelated data from users who lack permissions. SMB encryption and SMB dialect issues affect transport security or connectivity, not selective folder visibility.

  • Encryption setting is unrelated because the user can connect and authorization is being enforced.
  • Offline Files affects client-side caching, not whether unrelated folders are listed.
  • SMB dialect is unlikely because the client successfully accesses the share and opens the permitted folder.

Question 7

Topic: Manage Storage and File Services

A company stores departmental data in an Azure file share. A branch office has a Windows Server 2022 file server that must provide local SMB access to the same namespace, cache only frequently used files locally, and keep at least 15% free space on the data volume. Which configuration should you use?

Options:

  • A. Use DFS Replication between the file server and the Azure file share.

  • B. Add a server endpoint without enabling cloud tiering.

  • C. Add a server endpoint and enable cloud tiering with 15% volume free space.

  • D. Map the Azure file share directly on each client by using SMB.

Best answer: C

Explanation: Azure File Sync uses a Storage Sync Service, a sync group, a cloud endpoint for the Azure file share, and one or more server endpoints for Windows Server paths. To make a branch file server provide local SMB access while avoiding full local storage consumption, enable cloud tiering on the server endpoint. Cloud tiering keeps the full namespace visible on the server but recalls file content on demand and tiers cold content to Azure Files. The volume free space policy, such as 15%, tells Azure File Sync how much free space to preserve on the local volume. Direct SMB access to Azure Files does not create a local cache, and DFS Replication is not the mechanism for syncing with Azure Files.

  • Direct SMB mapping bypasses the branch file server cache and does not enforce a local volume free-space target.
  • DFS Replication synchronizes between Windows Server targets, not directly with an Azure file share as a cloud endpoint.
  • No cloud tiering can synchronize data but does not meet the requirement to cache only frequently used files and preserve free space.

Question 8

Topic: Manage Storage and File Services

A company hosts departmental file shares on an on-premises Windows Server. Remote users on unmanaged networks need secure SMB access from Windows 11 devices without deploying a traditional VPN or exposing TCP 445 to the internet. The server can be upgraded or replaced if needed, and users must keep using existing AD DS-based share and NTFS permissions. Which design best fits these requirements?

Options:

  • A. Expose SMB over TCP 445 and require SMB encryption.

  • B. Deploy SMB over QUIC with a trusted TLS certificate and UDP 443 access.

  • C. Publish the file server through Microsoft Entra Application Proxy.

  • D. Require a point-to-site VPN before mapping the shares.

Best answer: B

Explanation: SMB over QUIC is the best fit when users need SMB file access over untrusted networks without a traditional VPN. It carries SMB traffic inside a QUIC transport secured with TLS 1.3, typically using UDP 443, and it does not require exposing TCP 445 to the internet. Because the workload remains SMB, existing share permissions, NTFS permissions, and AD DS-based access control can continue to apply. The server must support SMB over QUIC and use a certificate trusted by clients. The key distinction is that SMB over QUIC changes the secure transport path, not the file authorization model.

  • Exposing TCP 445 increases internet-facing attack surface and does not meet the requirement to avoid exposing that port.
  • A point-to-site VPN can secure access, but it violates the requirement to avoid traditional VPN dependency.
  • Microsoft Entra Application Proxy is for HTTP-based applications, not native SMB file share publishing.

Question 9

Topic: Manage Storage and File Services

You are configuring storage for a standalone Windows Server 2022 file server with four identical local SSDs. The workload performs frequent small writes. The storage must tolerate one physical disk failure, keep write latency low, and use Windows Server software-defined resiliency rather than hardware RAID. Which configuration should you use?

Options:

  • A. A storage pool with a two-way mirror virtual disk

  • B. Storage Replica between two local volumes

  • C. A storage pool with a parity virtual disk

  • D. A storage pool with a simple virtual disk

Best answer: A

Explanation: Storage Spaces provides software-defined storage by grouping physical disks into a storage pool and creating virtual disks with a resiliency type. For a standalone file server that must tolerate one disk failure and support frequent small writes, a two-way mirror is the best fit. It stores copies of data across disks, so the volume can remain available after a single disk fails, and mirror layouts typically provide lower write latency than parity for random-write workloads. Simple spaces do not provide resiliency, while parity is better suited to capacity-efficient, read-heavy or sequential workloads. Storage Replica protects data by replicating volumes between locations or servers; it is not the local disk resiliency mechanism requested here.

  • Simple space fails because it stripes data without fault tolerance, so a disk failure can cause data loss.
  • Parity space meets basic resiliency but is a poorer fit for frequent small writes due to parity write overhead.
  • Storage Replica solves volume replication or disaster recovery, not local software-defined disk resiliency within a server.

Question 10

Topic: Manage Storage and File Services

A Windows Server file share \\FS1\Departments must allow all employees to browse the share root, but users should see only the department folders they can access. A user in GG-Marketing can see the Payroll folder but receives “Access is denied” when opening it.

Exhibit: Current configuration

SettingValue
Share permissionsAuthenticated Users: Read
Folder enumeration modeUnrestricted
Root NTFS permissionsAuthenticated Users: List folder
Payroll NTFS permissionsGG-Payroll: Modify

Options:

  • A. The share permission is too restrictive

  • B. The root NTFS permission blocks traversal

  • C. The Payroll NTFS permission is missing inheritance

  • D. Access-based enumeration is disabled

Best answer: D

Explanation: Access-based enumeration controls whether users can see files and folders in a share when they do not have permission to access those items. In this scenario, the user can browse the share root, so the root list permission is working as intended. The access-denied message on Payroll shows NTFS is correctly preventing access to that folder. The mismatch is visibility: FolderEnumerationMode is set to Unrestricted, so Windows displays the folder even to users without NTFS access. Setting the share to access-based enumeration would hide folders such as Payroll from users outside GG-Payroll.

  • Share permissions are not the issue because Authenticated Users can reach the share and NTFS is enforcing the folder denial.
  • NTFS inheritance is not required for GG-Payroll access if the explicit folder permission grants the needed access.
  • Root traversal is working because the user can browse the share root and see folder names.

Continue with full practice

Use the Microsoft AZ-802 Practice Test page for the full IT Mastery practice bank, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Try Microsoft AZ-802 on Web View Microsoft AZ-802 Practice Test

Free review resource

Read the Microsoft AZ-802 Cheat Sheet for compact concept review before returning to timed practice.

Revised on Monday, May 25, 2026