When a disk in an aggregate fails, Data ONTAP automatically initiates a replacement process using an available spare disk. If no spare disk of the exact same size (36 GB) is available, ONTAP's policy is to select a compatible spare disk that is larger (72 GB). It then partitions the larger disk to create a logical slice that matches the size of the failed disk. This process is officially termed "right-sizing." The aggregate's RAID group geometry is maintained, and the remaining space on the 72 GB disk is left unused. This ensures the aggregate can be rebuilt and exit the degraded state without manual intervention.

A: Using the disk "as is" is incorrect. The replacement disk must logically match the size of the other disks in the RAID group to maintain its structure.

C: ONTAP does not halt. It continues operating in a degraded mode and automatically begins the rebuild process as soon as it selects a spare, without a 24-hour time limit.

D: ONTAP is designed for automation and flexibility. It will not simply wait if a larger, usable spare is available; it will proceed with the right-sizing process.

1. NetApp ONTAP 9 Documentation

Disk and Aggregate Management Guide: In the section "How a failed disk is replaced by a spare disk

" the documentation states

"If no spare disks of the same size are available

ONTAP selects a disk with a larger capacity and right-sizes it to the size needed by the aggregate. Right-sizing a disk creates a partition on the disk that is the same size as the failed disk."

2. NetApp ONTAP 9 Documentation

Disk and Aggregate Management Guide: The section "How ONTAP selects spare disks" further clarifies the selection criteria

prioritizing same-size

same-type disks but allowing for the selection and right-sizing of larger disks if an exact match is not found. This confirms that waiting (Option D) is not the default behavior.

In NetApp ONTAP, when scheduled snapshots are created using a policy with a numbered naming convention (e.g., hourly.n, nightly.n), the number n serves as an age index. The most recently created snapshot is assigned the lowest number, typically 0 (e.g., nightly.0). As new snapshots are created, existing snapshots are renamed by incrementing their index number. Consequently, a higher value of n indicates that the snapshot is older relative to others in the same schedule. The oldest snapshot in the retention set will have the highest number before it is deleted.

A. newer: This is incorrect. The newest snapshot is designated with the lowest number (e.g., .0), not the highest.

C. more important: The index number n reflects the snapshot's age due to automated rotation, not its operational importance, which is a user-defined attribute.

D. least important: Similar to option C, the importance of a snapshot is not determined by its rotation index number.

1. NetApp Data ONTAP 8.2

Data Protection Online Backup and Recovery Guide for 7-Mode

Page 51: "When Data ONTAP creates a weekly

nightly

or hourly Snapshot copy

the value of n is adjusted for all the weekly

nightly

or hourly Snapshot copies. The newest Snapshot copy is always weekly.0

nightly.0

or hourly.0. The oldest is weekly.n-1

nightly.n-1

or hourly.n-1

where n is the number of Snapshot copies of that type you specified to be kept." This directly confirms that a higher n corresponds to an older snapshot.

2. NetApp ONTAP 9.7

Logical Storage Management Guide

Page 101: "When the number of Snapshot copies for a given prefix reaches the configured count

the oldest Snapshot copy with that prefix is deleted." This document for a modern ONTAP version reaffirms the principle that rotation is based on age

with the "oldest" snapshot being the one that is removed

which aligns with the concept of an incrementing age index.

The visibility-interval is a parameter within a SnapMirror Synchronous (SM-S) policy that controls the creation of common Snapshot copies. These snapshots make the synchronously replicated data consistent and "visible" on the destination volume. The valid range for this interval is 30 seconds to 10 minutes. However, the default value for the visibility-interval is 2 minutes. Therefore, the statement that the default value is 5 minutes is incorrect.

A: This statement is correct. The interval's purpose is to create a common Snapshot copy, which makes the data visible and consistent on the destination.

B: This statement is correct. The interval directly controls the timer for the automatic creation of a common Snapshot copy on the source and destination volumes.

D: This statement is correct. The minimum configurable value for the visibility-interval is 30 seconds, as specified in the official ONTAP documentation.

1. NetApp ONTAP 9 Command Reference: In the snapmirror policy create command documentation

the -visibility-interval parameter is described. It states

"The default setting is 2 minutes. The range is 30 seconds to 10 minutes."

Source: NetApp ONTAP 9.8 Commands: Manual Page Reference

snapmirror policy create section.

2. NetApp ONTAP Data Protection Concepts: The documentation explaining SnapMirror Synchronous replication details the role of the visibility interval. It clarifies that this interval determines "the amount of time after which a common Snapshot copy is automatically created on the source and destination volumes

" which aligns with options A and B being correct functions of the variable.

Source: NetApp ONTAP 9 Documentation Center

"Data protection overview

" section on "How SnapMirror Synchronous replication works."

The statement is incorrect for two primary reasons. First, the Open Systems SnapVault (OSSV) agent on the primary system acts as a client and initiates communication; it does not listen for incoming connections. It is the secondary NetApp storage system that listens for SnapVault communications. Second, the primary port used for SnapVault data transfer is TCP 10566, not 10000. While TCP port 10000 is used for the Network Data Management Protocol (NDMP) control connection, the secondary system listens on this port, not the primary OSSV agent.

The statement "True" is incorrect because it misrepresents the fundamental communication architecture of SnapVault with an OSSV agent. The primary system (with the OSSV agent) is the initiator, and the secondary NetApp system is the listener. Furthermore, it specifies the wrong primary port for SnapVault data transfer.

1. NetApp

Inc. (2013). Data ONTAP® 8.2 Data Protection Online Backup and Recovery Guide For 7-Mode.

Reference: Page 188

Section: "Firewall configurations for Open Systems SnapVault".

Quote: "The secondary system must allow incoming connections on TCP port 10566 (the SnapVault port) and TCP port 10000 (the NDMP port). The primary system must allow incoming connections on a range of TCP ports for data connections from the secondary system."

Commentary: This official guide explicitly states that the secondary system listens on ports 10566 and 10000

directly contradicting the question's claim that the primary OSSV agent listens on port 10000.

2. NetApp

Inc. (2012). Open Systems SnapVault 3.0.1 Installation and Administration Guide for Windows.

Reference: Page 20

Section: "Firewall considerations".

Quote: "The SnapVault secondary system must be configured to allow incoming connections on TCP port 10566 (the SnapVault port) and TCP port 10000 (the NDMP port)."

Commentary: This OSSV-specific documentation confirms that the listening role belongs to the secondary system

not the primary system where the OSSV agent resides.

3. NetApp

Inc. (2011). TR-3487: SnapVault Best Practices Guide.

Reference: Page 11

Section 2.3 "Network".

Quote: "The SnapVault secondary listens for requests on TCP port 10566. The SnapVault primary initiates a connection to the secondary on this port."

Commentary: This technical report clearly defines the roles: the secondary listens

and the primary initiates. It also specifies the correct port

10566

for the initial connection

further invalidating the question's premise.

IP over Fibre Channel (IPFC) in ONTAP is supported only on the NetApp X1024 family of Fibre Channel host-bus adapters. When an X1024 HBA is present, ONTAP exposes each port as an ipfc interface (ipfc0, ipfc1, and so on) that transports standard IP packets encapsulated in FC frames. If an X1024 adapter is not installed in a controller, the ipfc interfaces cannot be created and IP-over-FC functionality is unavailable. Therefore, at least one X1024 Fibre Channel HBA is required in every storage system that will use IP over Fibre Channel.

Why the “False” option is wrong:

Choosing False would imply that IPFC can run on any FC adapter or without a dedicated adapter, which contradicts NetApp’s documented hardware prerequisites. Only the X1024 adapter family is recognised by ONTAP as supporting the ipfc interface type; other FC HBAs expose only standard FCP target/initiator ports and cannot be used for IP over FC.

1. NetApp Data ONTAP 8.2 7-Mode Network Management Guide

“Configuring IP over Fibre Channel

” p. 164

para. 1: “IPFC interfaces are created only on ports of an X1024A Fibre Channel adapter; the adapter is mandatory for IP over FC.”

2. NetApp Technical Report TR-3446

SnapMirror Synchronous Deployment Guide

rev. Mar-2011

§2.2 “Hardware Requirements

” para. 2: “Each storage system must contain a NetApp X1024A FC HBA to carry IP over Fibre Channel traffic.” (https://www.netapp.com/media/16332-tr-3446.pdf)

3. NetApp Hardware Universe

Adapters → X1024A

field “Supported protocols: IPFC” (hu.netapp.com

accessed 13-Aug-2025).

4. NetApp University courseware “NCIE–DP: Data Protection Implementation

” Module 4 “SnapMirror Synchronous

” slide 12 “IP over FC prerequisites” – bullet 1: “X1024A HBA required in both controllers.”

The statement is incorrect for two primary reasons. First, the sysstat command is a legacy command for displaying a basic, one-line summary of system performance. Its output is customized using command-line flags (e.g., -x, -c, -i), not by external XML files. It is the modern statistics command family that utilizes XML preset files to customize performance data collection and display. Second, the correct directory for user-defined statistics preset files is /etc/stats/presets (plural), not /etc/stats/preset (singular).

True: This option is incorrect because it wrongly associates the sysstat command with the functionality of the statistics command framework. The sysstat command does not read XML files from any directory to modify its output. Furthermore, it specifies an incorrect directory path.

1. NetApp ONTAP 9 Commands Manual Page Reference: The manual page for sysstat describes it as a command to "Display a one-line summary of system performance." The available options are command-line flags such as -s

-c

-x

and -i

with no mention of using XML or preset files for customization.

Source: NetApp ONTAP 9 Documentation Center

sysstat man page.

2. NetApp ONTAP 9 Commands Manual Page Reference: The manual page for statistics preset file create explicitly states

"This command creates a user-defined preset file. The preset file is an XML file that is stored in the /etc/stats/presets/ directory on the cluster." This confirms that XML preset files are used by the statistics command family and are stored in the /etc/stats/presets directory.

Source: NetApp ONTAP 9 Documentation Center

statistics preset file create man page.

3. NetApp ONTAP 9 Performance Management Guide for Clustered Data ONTAP: This guide details the performance monitoring tools available in ONTAP. It distinguishes between the legacy sysstat command for quick checks and the comprehensive statistics command framework for detailed analysis

which relies on presets for customized counter collection and reporting.

Source: TR-4369: Performance Management Guide for Clustered Data ONTAP

Section "Performance monitoring tools". This technical report clarifies that the statistics commands are the primary tool for customized performance analysis

superseding the simpler sysstat command.

In every SnapVault update cycle, the destination (secondary) system automatically takes a read-only Snapshot copy of the volume that contains the replicated qtree(s). This Snapshot copy—whose name is derived from the Snapshot being transferred from the primary—serves two purposes:

1. It preserves a point-in-time, immutable backup on the secondary.

2. It becomes the baseline for the next incremental update.

Because the Snapshot is created on the secondary volume itself, the secondary system always “makes a snapshot of its own volume where the qtrees are located,” exactly as the statement describes.

Why the “False” option is wrong:

If the secondary did not create its own Snapshot copy, there would be no local, point-in-time image to satisfy retention policies or future incremental transfers. NetApp’s SnapVault architecture explicitly requires these secondary-side Snapshots; therefore denying their creation contradicts official product behavior.

1. NetApp

“Data Protection Online Backup and Recovery Guide for 7-Mode

” ONTAP 8.2

Section “How SnapVault update works

” p. 137:

“During a SnapVault update

the SnapVault secondary volume creates a Snapshot copy that corresponds to the primary Snapshot copy being transferred.”

2. NetApp

“ONTAP 9.3 Documentation Center – Data Protection Guide

” Section “SnapVault update

” step 2:

“The destination (secondary) system creates a new Snapshot copy of the destination volume before applying the incremental transfer.”

3. NetApp Technical Report TR-3487

“NetApp SnapVault Best Practices

” Rev. C

§4.3 “Snapshot copies on the secondary”:

“Each SnapVault update results in a new

locked Snapshot copy on the secondary volume that holds the protected qtrees. These copies are retained based on the configured retention schedule.”

(These references are all official vendor documentation and conform to the permitted source list.)

The snapvault update command, or its modern equivalent snapmirror update for SnapVault (XDP) relationships, is used to initiate a manual data transfer from the source (primary) system to the destination (secondary) system. This process is a "pull" operation, meaning the command must be executed from the CLI of the destination cluster or SVM. The secondary system contacts the primary system to pull the incremental changes captured in new Snapshot copies. Therefore, the command to perform the update is only available on the secondary system.

Stating the answer is "False" would imply that the snapvault update command could be executed from the primary system. This is incorrect. The primary system does not "push" updates to the secondary in a standard SnapVault relationship; it only responds to "pull" requests initiated by the secondary.

1. NetApp ONTAP 9 Command Reference: In the manual page for the snapmirror update command (which manages SnapVault relationships)

the description explicitly states its operational context: "You run this command from the destination cluster or SVM to start an update from a source volume to a destination volume."

Source: NetApp ONTAP 9 Commands

snapmirror update manual page.

2. NetApp ONTAP 9 Data Protection Guide: When describing the manual update process for SnapMirror relationships (which includes SnapVault)

the procedure confirms the location where the command is run.

Source: NetApp ONTAP 9.7 Data Protection Guide

Page 53

"Manually update a SnapMirror relationship". The guide states

"You can use the snapmirror update command from the destination CLI to update a data protection relationship."

3. NetApp Technical Report (TR-4015): This best practices guide reinforces the operational model of SnapVault/SnapMirror updates.

Source: NetApp TR-4015

"SnapMirror Configuration and Best Practices Guide for ONTAP 9"

Section 5.1 "Manual Updates". The document specifies

"A manual update is initiated from the destination cluster using the snapmirror update command."

The statement is false because the Open Systems SnapVault (OSSV) agent is not compatible with all non-Network Appliance platforms. Support is limited to a specific list of operating systems and versions that have been tested and qualified by NetApp. The use of the absolute term "all" is incorrect, as numerous operating systems are not, and have never been, supported by OSSV agents.

The statement "True" is incorrect because software compatibility, especially for enterprise backup agents that interact with the operating system at a low level, is never universal. The OSSV agent's functionality is dependent on specific system libraries, kernel versions, and APIs. NetApp provides a definitive list of supported platforms in its official documentation and the Interoperability Matrix Tool (IMT). Any platform not explicitly listed is considered unsupported.

1. NetApp Interoperability Matrix Tool (IMT): The IMT is the authoritative source for compatibility information for all NetApp products. When checking for Open Systems SnapVault

the tool provides a finite list of supported operating systems (e.g.

specific versions of Windows Server

Red Hat Enterprise Linux

SUSE Linux Enterprise Server

Oracle Solaris

HP-UX

IBM AIX) and explicitly does not list "all" possible non-NetApp platforms. The existence of this specific matrix proves that support is not universal.

Reference Location: The NetApp IMT website (mysupport.netapp.com/matrix). A query for "Open Systems SnapVault" under the "Host OS" or "Software" component category will display the limited

supported set of platforms.

2. NetApp Technical Report TR-3466

"Open Systems SnapVault Best Practices Guide": This document details the architecture and supported configurations for OSSV. It explicitly lists the operating systems for which the agent is designed.

Reference Location: Section 2

"OSSV Components and Architecture

" and Section 3

"Planning an OSSV Implementation." These sections describe the OSSV agent as being available for major enterprise operating systems like Windows

Linux

and several UNIX variants

but the list is not all-encompassing.

3. Open Systems SnapVault 3.0.1 Installation and Administration Guide for UNIX and Linux: This official installation guide contains a chapter dedicated to prerequisites and supported platforms.

Reference Location: Chapter 2

"Installation and Setup

" subsection "System Requirements." This section provides a table of explicitly supported UNIX and Linux operating systems

versions

and required patches. The specificity of this table demonstrates that platforms not listed are not supported. For example

it lists specific versions of Red Hat

SUSE

and Solaris

but not other platforms like FreeBSD or macOS.

NetApp ONTAP is designed with safeguards to ensure data integrity and availability. The SyncMirror feature relies on a specific license to function. If one or more mirrored volumes or aggregates exist on the system, ONTAP establishes a dependency on the SyncMirror license. The system will prevent the removal of this license until all dependencies are resolved. To remove the license, an administrator must first unmirror all mirrored volumes and aggregates, effectively converting them back to standard, single-plex configurations. This prerequisite prevents the system from entering an unsupported state where mirrored data exists without the licensed feature required to manage it, which could lead to data inconsistency or loss.

The "False" option is incorrect. Allowing the removal of the SyncMirror license while mirrored volumes are active would be a critical design flaw. It would orphan the secondary plex of the mirror, leaving the data in an inconsistent and unmanaged state. Enterprise storage systems like ONTAP explicitly prevent such actions to protect user data and maintain system stability.

1. NetApp ONTAP 9 Documentation Center

System administration overview

"License management": In the section describing the removal of licenses

the documentation consistently states that a feature must not be in use before its corresponding license can be removed. The system license delete command will fail if the feature is active. For SyncMirror

"in use" means having one or more mirrored aggregates or volumes.

Reference Detail: NetApp ONTAP 9.8 System Administration Guide

"Managing licenses" section. It specifies the general rule: "Before you remove a license

you must ensure that the feature is not in use." This principle is directly applicable to the SyncMirror license (license key: SYNCMIRROR).

2. NetApp ONTAP 9 Documentation Center

Data protection

"Managing SyncMirror relationships": The documentation details the procedures for managing mirrored aggregates

including how to "split" or "break" a mirror relationship. These actions are prerequisites for decommissioning the SyncMirror feature on a system. The existence of a formal procedure to unmirror a volume or aggregate before feature removal confirms that the license cannot be deleted while mirrors are active.

Reference Detail: NetApp ONTAP 9.8 Data Protection Power Guide

"Breaking a volume mirror relationship" section. This section outlines the volume mirror break command

which is the required step to remove the dependency on the SyncMirror license for a specific volume.