Memory hook: Namespace locates; permissions authorize; replication copies.
Must remember
- SMB share permissions and NTFS permissions combine to determine effective access; inspect both. FSRM provides quotas, file screening and classification capabilities, not a replacement for file ACLs.
- DFS Namespaces provides a logical path; DFS Replication copies supported file data. Azure File Sync caches/synchronizes supported Windows file-server data with Azure Files and can use cloud tiering.
- Azure Files requires compatible identity/network access and share/filesystem permissions. Plan migration, file fidelity, recall behavior, backup and synchronization health rather than merely copying paths.
- SMB over QUIC secures supported SMB access over QUIC; SMB Direct uses RDMA for supported high-performance paths. SMB encryption/signing and protocol settings address different risks and capabilities.
- Storage Spaces pools disks; Storage Spaces Direct builds supported clustered storage; Storage Replica provides supported block-level replication. Plan disks, volumes, resiliency, fault domains, Storage QoS and iSCSI authentication/networking.
- Choose NTFS/ReFS by workload and feature support. Deduplication reduces duplicate blocks for supported workloads; BitLocker encrypts volumes. Store recovery keys securely and test recovery independently of the protected machine.
Choose under exam pressure
| Requirement | Choice and reason |
|---|---|
| Users need one stable path across file servers | DFS Namespace, with separate replication/availability design. |
| Keep local access to a large Azure-backed file dataset | Azure File Sync with deliberate tiering and cache sizing. |
Traps
- DFS Namespace alone does not replicate file contents.
- Replication can copy deletion or corruption and therefore does not replace backups.
Active recall
1. What determines effective SMB file access?
Both share-level permissions and filesystem ACLs, including group membership and deny behavior.
2. What does cloud tiering do?
Keeps selected file content in the cloud while preserving local namespace/access through recall.
3. Why protect BitLocker recovery keys separately?
A machine failure or lockout must not also remove the only recovery path.
4. What is SMB Direct for?
Supported low-latency/high-throughput SMB using RDMA.
5. Why choose filesystem deliberately?
NTFS and ReFS support different features and workload scenarios.