A company runs applications on Windows and Linux EC2 instances across multiple Availability Zones using Auto Scaling groups. They need durable shared storage that uses SMB for Windows, NFS for Linux, provides sub-millisecond latency, and is shared read/write across instances. Which three steps accomplish this?

Amazon FSx for NetApp ONTAP Multi-AZ is the correct choice because it supports both SMB (for Windows) and NFS (for Linux), offers sub-millisecond latency, and provides shared read/write access across instances, meeting all specified requirements. EFS is primarily NFS-based and doesn't natively support SMB for Windows instances. gp3 EBS volumes are block storage, not shared file systems, and cannot be simultaneously mounted by multiple instances in a shared read/write fashion. Updating the launch template user data ensures that newly launched instances automatically mount the shared file system, providing consistent configuration. Finally, performing an instance refresh on each Auto Scaling group replaces existing instances with new ones launched from the updated template, ensuring all instances utilize the new shared storage without manual intervention. Updating existing EC2 instances manually is not scalable or automated for Auto Scaling groups.