Deploy Multi-AZ FSx for NetApp ONTAP per Region with a scheduled SnapMirror relationship to the on-premises array
A company is migrating its product development teams from an on-premises data center to a hybrid environment. The new environment will add four AWS Regions and will give the developers the ability to use the Region that is geographically closest to them. All the development teams use a shared set of Linux applications. The on-premises data center stores the applications on a NetApp ONTAP storage device. The storage volume is mounted read-only on the development on-premises VMs. The company updates the applications on the shared volume once a week. A DevOps engineer needs to replicate the data to all the new Regions. The DevOps engineer must ensure that the data is always up to date with deduplication. The data also must not be dependent on the availability of the on-premises storage device. Which solution will meet these requirements?
Community Votes
100% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The source is NetApp ONTAP, so the only approach that preserves ONTAP-native efficiency such as deduplication and incremental transfer is SnapMirror to FSx for NetApp ONTAP (C). Option A routes the data through an S3 File Gateway with cron copies plus cross-Region replication, which converts it to an object-store copy, loses the file-system semantics, and depends on scheduled jobs. Option D uses DataSync to EFS on a daily schedule, which is both less frequent than required and does not deduplicate. Option B is a mismatched design, pairing an FSx File Gateway with Windows file servers for a NetApp source.
The source is a NetApp ONTAP device mounted read-only, updated weekly, and the data must stay continuously deduplicated, be replicated to four Regions, and stop depending on the on-premises device's availability. Amazon FSx for NetApp ONTAP provides a managed ONTAP file system in each Region, and configuring a scheduled SnapMirror relationship between the on-premises array and those instances keeps the cloud copies current while ONTAP's deduplication reduces transferred and stored data. SnapMirror is native to ONTAP, so the on-premises device is the replication source rather than a runtime dependency.
Copying the data to an S3 File Gateway with cron jobs and cross-Region replication (A) — this flattens an ONTAP file system into objects through a gateway, loses the native ONTAP incremental and deduplication behavior, and depends on a scheduled job rather than continuous replication; it also leaves the on-premises device in the data path. Using DataSync to copy daily into EFS (D) — a daily schedule cannot satisfy continuously up-to-date data, and EFS provides no deduplication. Using an FSx File Gateway with Windows File Server (B) — neither product matches a NetApp ONTAP source.
Community Discussion (6 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The on-premises source is a NetApp ONTAP storage device, and the requirement to stay deduplicated and continuously current points to ONTAP's own replication technology. Amazon FSx for NetApp ONTAP delivers a managed ONTAP file system, deployed as Multi-AZ instances and volumes in each of the four Regions, and configuring a scheduled SnapMirror relationship between the on-premises array and the FSx for ONTAP instances keeps the cloud copies incrementally up to date while ONTAP deduplication avoids transferring redundant blocks. Because the cloud file systems are independent ONTAP instances that receive replicated data, the solution no longer depends on the on-premises device remaining available.Why the Other Options Are Wrong
A creates an Amazon S3 File Gateway in the data center, copies data to it with a cron job, and then uses S3 cross-Region replication. This objectifies an ONTAP file system, loses ONTAP-native incremental transfer and deduplication, and depends on a scheduled job rather than continuous replication. B creates an FSx File Gateway and then FSx for Windows File Server file servers, which is a mismatched design for a NetApp ONTAP source and still relies on cron to copy the data. D creates EFS file systems and uses a DataSync agent with a daily schedule, which cannot satisfy continuously up-to-date data and offers no deduplication. C is correct.Community Comment Notes
Community voted C (90). Commenters cited the AWS documentation on migrating to FSx for ONTAP with SnapMirror, noting that Multi-AZ FSx for ONTAP instances provide high availability and replication. limelight04 questioned whether C addresses deduplication and independence from the on-premises device, but SnapMirror's scheduled, incremental replication with ONTAP deduplication is exactly what satisfies both.Official Reference
Related Analysis
Practice All DOP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full DOP-C02 Practice Test →