NS0-155 Netapp Data ONTAP 7-Mode Administrator Free Practice Exam Questions (2025 Updated)

https://library.netapp.com/ecmdocs/ECMP1196890/html/man5/na_exports.5.html

IP addresses and wildcards can be used when specifying host targets in exports.

User names are not valid exports options, save for the anon option which utilizes a local system UID or user name (i.e. no user name mapping or resolution is performed.)

The highest level in the filesystem that can be specified for an export is the volume level. Implicitly this means that each volume must be exported separately.

An export provides access to paths below the export, implying that multiple paths on the same volume can be exported from an export.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_vol.1.html

vol options nosnapdir [on|off]

If this option is on, it disables the visible .snapshot directory that is normally present at client mount points, and turns off access to all other .snapshot directories in the volume. The default setting is off.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_fcp.1.html

fcp show initiator [ -v ] [ adapter ]

If no adapter name is given, information about all initiators connected to all adapters are shown.

The command displays the portname of initiators that are currently logged in with the Fibre Channel target adapters. If the portname is in an initiator group setup through the igroup command, then the group name is also displayed. Similarly, all aliases set with the fcp wwpn-alias command for the portname are displayed as well.

If the -v flag is given, the command displays the Fibre Channel host address and the nodename/portname of the initiators as well.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_reallocate.1.html

The -p option requests that reallocation of user data take place on the physical blocks in the aggregate, but the logical block locations within a flexible volume are preserved.

Aggregate reallocation is not supported on aggregates created prior to Data ONTAP 7.2.

Using the -p option may reduce the extra storage requirements in a flexible volume when reallocation is run on a volume with snapshots. It may also reduce the amount of data that needs to be transmitted by SnapMirror on its next update after reallocation is performed on a SnapMirror source volume.

Disks must be assigned to an aggregate to be used as raid group members or spares. Unassigned disks are displayed as "not owned".

http://backdrift.org/man/netapp/man1/na_sysstat.1.html

http://redhunter.com/blog/2010/02/11/netapp-consistency-points-in-cacti/

cp_from_log_full (log full) - the current NVRAM bank is full and the system switches to the other one and starts writing this to disk. Very heavy write activity.

cp_from_cp (aka Back to Back) - filer is overloaded. The write traffic is coming in faster than it can be written and the filer is running out of NVRAM capacity in one bank before the data in the other bank can be written.

cp_from_busy is not a real cp type

cp_from_timer - 10 seconds since the last CP – it means the system is pretty idle write-wise.

http://backdrift.org/man/netapp/man1/na_snap.1.html

Snapshots can be made of volumes or aggregates; most commonly the former. The question refers to a file system, or more specifically a volume.

You cannot snapshot directories or qtrees alone.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_options.1.html

nfs.per_client_stats.enable

Enables/disables the collection and display of perclient NFS statistics, as described in na_nfsstat(1). Valid values for this option are on or off. The default value for this option is off.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man5/na_snapmirror.conf.5.html

Each relationship entry of the /etc/snapmirror.conf file is a single line containing space-separated fields.

The entry has this format:

Source destination arguments schedule schedule

This is the schedule used by the destination node for updating the mirror. It informs the SnapMirror scheduler when transfers will be initiated. The schedule field can contain the word sync to specify fully synchronous mirroring, semi-sync to specify semi-synchronous mirroring, or a cron-style specification of when to update the mirror.

visibility_interval

The value for this argument is a number optionally followed by the suffixes: s (seconds), m (minutes) or h (hours). If a suffix is not specified, value is interpreted as seconds. This argument controls the amount of time before an automatic snapshot is created on the source volume that is synchronously mirrored. The value is the number of seconds between automatically created snapshots. The default value is 3 minutes. A small number here can negatively affect the performance of the mirror. This argument is ignored for asynchronous mirrors.

Outstanding (deprecated)

This argument controls the performance versus synchronicity trade-off for synchronous mirrors. The value for this argument is a number followed by the suffixes: ops (operations), ms (milliseconds) or s (seconds). Setting a value less than 10s configures the mirror to run in fully synchronous mode. Setting a value greater than or equal to 10s configures the mirror to run in semi-synchronous mode. This argument is ignored for asynchronous mirrors. Please note that this is a deprecated option. Use the schedule field to specify the synchronous mode for the mirror.

cksum

This controls which checksum algorithm is used to protect the data transmitted by SnapMirror. Currently supported values are "none", "crc32c", and "crc32c_header_only". The value "crc32c_header_only" has been added only for volume SnapMirror and is not supported for synchronous SnapMirror and qtree SnapMirror.

https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_snap.1.html

snap restore [ -f ] [ -t vol | file ] [ -s snapshot_name ] [ -r restore_as_path ]

vol_name | restore_from_path

Reverts a volume to a specified Snapshot copy, or reverts a single file to a revision from a specified Snapshot copy.

Before reverting the volume or file, the user is requested to confirm the operation. The -f option suppresses this confirmation step.

https://library.netapp.com/ecmdocs/ECMP1196890/html/man1/na_ifstat.1.html

http://backdrift.org/man/netapp/man1/na_netdiag.1.html

ifstat - display device-level statistics for network interfaces

netdiag - perform network diagnostics

Data OnTap can simultaneously serve NAS and SAN protocols. CIFS, NFS, and FC protocol are examples of NAS and SAN protocols respectively.

Data OnTap 7.1 or later does not support DAFS.

DFS provides location transparency and redundancy by allowing shares in multiple different locations to be logically grouped under one folder, or DFS root. While practically a CIFS server shared by a Data OnTap filer can be a DFS target, DFS namespaces can only be hosted on Windows systems.

https://library.netapp.com/ecmdocs/ECMP1196991/html/GUID-D4D7C7F0-9063-4099-B5CA-8FEE619EEF1D.html

SyncMirror is a feature of Data OnTap used to mirror data to two separate aggregates. It allows for real-time mirroring of data to matching aggregates physically connected to the same storage system.

SyncMirror provides for synchronous mirroring of data, implemented at the RAID level. You can use SyncMirror to create aggregates that consist of two copies of the same WAFL file system. The two copies, known as plexes, are simultaneously updated. Therefore, the copies are always identical. The two plexes are directly connected to the same system.

The following provides information about the activities of SyncMirror:

SyncMirror can be used to mirror aggregates and traditional volumes. (A traditional volume is essentially an aggregate with a single volume that spans the entire aggregate.)

SyncMirror cannot be used to mirror FlexVol volumes. However, FlexVol volumes can be mirrored as part of an aggregate.

SyncMirror is different from synchronous SnapMirror.

http://backdrift.org/man/netapp/man1/na_sysstat.1.html

sysstat [ -c count ] [ -s ] [ -u | -x | -m | -f | -i | -b ] [ -d ] [ interval ]

-f For the default format display FCP statistics.

The FCP default output format is as follows:

CPU NFS CIFS FCP Net kB/s Disk kB/s FCP kB/s Cache

in out read write in out age

###% ##### ##### ##### ##### ##### ##### ##### ##### ##### >##

http://hd.kvsconsulting.us/netappdoc/801docs/html/ontap/smg/GUID-866DD79D-D2A6-4FBA-B0BDA63560FECEFF.html

In OnTap 8.0, when UNIX security style is selected, only UNIX security objects can be used. The correct answer is GID, UID and UNIX permissions.

Basic UNIX permissions are organized into three classes: user, group, and others.

UNIX operating systems identify users with a numerical value: a user identifier, also known as a UID or User ID. Each user is a member of a group of the same name as the user. Like UIDs, groups (GIDs) are also specified using a numerical value.