01. Stakeholders ask why the DR copy can lag behind production by a noticeable amount, and how that lag can be tightened without changing the replication technology.
What primarily determines the recovery point of an async SnapMirror relationship?
a) The direction chosen for a later reverse-resync operation.
b) The transfer schedule, since data between updates is not yet replicated.
c) Whether storage efficiency is preserved on each transfer.
d) The read-only state of the destination during normal operation.
02. An administrator reports that a replication relationship shows a healthy state, yet monitoring indicates the time since its last successful transfer now exceeds the agreed recovery point.
What does this condition most directly tell you, and where should you look first?
a) The destination volume is corrupt and a single-file restore is required to repair it
b) The destination Snapshot schedule is retaining too many historical copies
c) The relationship must be treated as broken and fully re-initialized from an empty baseline before it can resume transferring any data
d) The primary site has clearly failed and a failover to the destination should begin right away
e) lag now exceeds the RPO, so the last good transfer is too old — investigate the transfer path first
03. Monitoring flags a replication relationship whose lag keeps climbing across several cycles. Before escalating, you want to confirm the two most likely mechanical causes.
Which checks directly test whether the transfers themselves are failing to keep up?
(Choose three.)
a) Confirm the destination aggregate still has free space to accept incoming transfers
b) Increase the local Snapshot retention count held on the destination
c) Check that the relationship's transfer schedule is still enabled and firing on time
d) Rotate and re-key the application encryption certificates that are stored on the source volume before doing anything else
e) Verify that inter-site bandwidth is sufficient for each transfer to finish before the next one is due
04. In a healthy SnapMirror active sync relationship, a host maps the same LUN through paths to both the primary and secondary clusters.
How does the host normally direct its I/O across those paths?
a) It sends all reads to the secondary and all writes to the primary, by design
b) It uses the primary paths that ALUA reports active/optimized, keeping the secondary paths as standby
c) It selects a path at random for each command, giving no path any preference
d) It stripes every write evenly across both clusters at the same moment, purely for throughput balance
05. You are sizing a new asynchronous replication solution that must move a large daily change rate to a remote secondary while still meeting the agreed recovery point.
Which dependencies must the design account for so the relationship can consistently meet its target?
(Choose three.)
a) Adequate capacity on the secondary to hold the replicated data and its retained copies
b) Sufficient inter-site network bandwidth to complete each transfer within its interval
c) Conversion of every source volume to a legacy 7-Mode layout before any replication is permitted to begin on the cluster
d) Disabling all local Snapshot schedules on the source volume
e) Cluster peering established between the source and destination clusters
06. A compliance team requires that specific point-in-time versions of a dataset be kept for several years, while the operations team separately needs quick recovery of recent working versions for day-to-day mistakes.
How should the protection policies be designed to serve both needs?
a) A long-retention SnapVault policy for the archive plus short-lived local copies for recent recovery
b) Use a mirror-only policy that deletes older copies after each successful transfer
c) Keep only a large number of local Snapshot copies on the primary and no secondary
d) Configure a single synchronous relationship and rely on it exclusively for both long-term archival and everyday recent-version recovery
e) Present a FlexClone of the volume and treat that clone as the compliance archive
07. Developers need a writable copy of last night's production database Snapshot to test a schema change, without disturbing production and without a full-size data copy.
Which SnapCenter workflow best fits this repurposing need?
a) A brand-new full backup, copied byte-for-byte into a separate spare volume.
b) A restore-in-place workflow that simply overwrites the live production database.
c) A schedule change, running the backups more frequently during the test phase.
d) A clone workflow provisioning a writable copy solely from a Snapshot for dev/test.
e) A SnapMirror break that redirects application clients over to the DR site.
08. The primary cluster hosting a production volume has been lost. A scheduled asynchronous relationship to a remote secondary is in place, and the application must be brought back online from the secondary as quickly as possible.
What is the correct sequence to restore service and later return to the primary once it is repaired?
a) Restore the destination volume from an older Snapshot copy before allowing any access
b) Break the relationship so the destination is writable and serve from it, then reverse-resync and failback later
c) Serve the application from the destination while it remains read-only until the primary returns
d) Wait for the primary to be repaired and resume the original relationship untouched
e) Delete the current relationship, initialize a completely new one from the destination, and then copy the entire dataset back to the rebuilt primary
09. Auditors require a periodic disaster-recovery exercise that confirms the replicated dataset is usable, but the exercise must not interrupt the live replication relationship or alter the real destination data.
Which approach lets you validate the recovery copy without disrupting the relationship?
a) Perform a SnapRestore on the destination to a prior copy for the test window
b) Break the relationship, run the validation test against the now-writable destination, and then resync the relationship again afterward
c) Failover to the destination and serve production from it during the exercise window
d) Redirect the source application to write directly into the destination volume
e) Create a FlexClone of the destination volume and test the application against the clone
10. Before deploying a specific SnapCenter plug-in against a particular ONTAP release and application version, an engineer must confirm the exact combination is supported.
Where should the engineer confirm the plug-in, application, and ONTAP version combination is supported?
a) A community forum thread that describes one individual user's particular setup.
b) The newest available release, on the assumption that latest is always compatible.
c) The NetApp Interoperability Matrix Tool, the only supported-combination source.
d) The SnapCenter job log left over from an unrelated earlier deployment run.
e) Whatever version pairing a colleague recalls having worked in a past project.