A county is replacing aging Windows file servers that provide SMB shares and NTFS ACLs for public-health case files, planning drawings, and permit attachments, with departments in separate AWS accounts joined to the same Active Directory domain. Which target architecture should architects select for the migrated file platform?
Select an answer to reveal the explanation.
Short Explanation
Windows shops live on SMB and Active Directory, not mystery object APIs. FSx for Windows File Server is the managed file cabinet that still speaks the language the desktops and NTFS ACLs already know. Glacier, a lonely EBS volume, and stuffing files into DynamoDB skip the protocol and identity work.
Full Explanation
When a migrated Windows file estate depends on SMB, NTFS ACLs, and Active Directory identities across multiple department accounts, Amazon FSx for Windows File Server is the Task 4.3 target rather than block or object substitutes. Join the file system to the existing domain so users keep familiar shares and ACLs without rewriting clients. Glacier is archival object storage, a single EBS volume is not a multi-account shared Windows file service, and DynamoDB is not an SMB file protocol.