NetApp NS0-155 Online Practice Questions and Exam Preparation

NetApp NS0-155 Online Questions & Answers

• Question 111:

  Which command displays the statistics for Ethernet network interfaces?

  A. ifconfig
  B. ifstat
  C. sysconfig
  D. sysstat
  B. ifstat

  ---

  https://library.netapp.com/ecmdocs/ECMP1196890/html/man1/na_ifstat.1.html ifstat - display device-level statistics for network interfaces

• Question 112:

  Which three protocols can coexist on a NetApp storage system? (Choose three)

  A. DAFS
  B. CIFS
  C. DFS
  D. FCP
  E. NFS
  B. CIFS
  D. FCP
  E. NFS

  ---

  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.

• Question 113:

  Which action will cause a currently in-sync SnapMirror relationship to fail out of sync?

  A. Running snapmirroe update on the source storage system.
  B. Running snapmirror release on the source storage system.
  C. Modifying the /etc/snapmirror.conf file for the relationship on the source storage system
  D. Modifying the /etc/snapmirror.conf file for the relationship on the destination storage system.
  D. Modifying the /etc/snapmirror.conf file for the relationship on the destination storage system.

  ---

  https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_snapmirror.1.html https:// library.netapp.com/ecmdocs/ECMP1196979/html/man5/na_snapmirror.conf.5.html snapmirror update [ -S source ] [ -k kilobytes ] [ -s src_snap ] [ -c

  create_dest_snap ] [ -w ] destination For asynchronous mirrors, an update is immediately started from the source to the destination to update the mirror with the contents of the source.

  For synchronous mirrors, a snapshot is created on the source volume which becomes visible to clients of the destination volume.

  The snapmirror update command must be issued on the destination filer. snapmirror release source { filer:volume | filer:qtree } Tell SnapMirror that a certain direct mirror is no longer going to request updates. If a certain destination is no

  longer going to request updates, you must tell SnapMirror so that it will no longer retain a snapshot for that destination. This command will remove snapshots that are no longer needed for replication to that destination, and can be used to

  clean up SnapMirror-created snapshots after snapmirror break is issued on the destination side.

  The source argument is the source volume or qtree that the destination is to be released from. The destination argument should be either the destination filer and destination volume name or the destination filer and destination qtree path. You

  can use a line from the output of the snapmirror destinations command as the set of arguments to this command. The /etc/snapmirror.conf file exists on the node containing the mirror used for SnapMirror.

• Question 114:

  When using a Protection Manager policy to manage Open Systems SnapVault backups on a UNIX server, which three are valid objects to include in the data set? (Choose three.)

  A. A file
  B. A qtree
  C. A directory
  D. The entire client
  A. A file
  C. A directory
  D. The entire client

  ---

  Open Systems Snap Vault runs on servers, so the objects that can be selected for backup will be host- based. Qtrees are objects on the storage system.

  

• Question 115:

  Node 1 in a clustered pair detects that it has lost connectivity to one of its disk shelves. Node 1 is still up, but it cannot see one of its disk shelves. However, the partner node, Node 2, can see all of the Node 1's disk shelves. Which feature will cause Node 2 to monitor this error condition for a period of three minutes by default, and then forcibly take over Node 1 if the error condition persists?

  A. Auto enable of giveback
  B. Negotiated Fail Over
  C. Takeover on panic
  D. Cf.quickloop.enable
  B. Negotiated Fail Over

  ---

  http://www.wafl.co.uk/cf/

  http://wafl.co.uk/options/

  Negotiated failover is a general facility which supports negotiated failover on the basis of decisions made by various modules.

  cf.takeover.on_disk_shelf_miscompare

  This option allows negotiated takeover to be enabled when the cluster nodes detect a mismatch in disk shelf count. By default, this option is set to off.

  This option is available only when cluster is licensed and changing the value on one filer automatically changes the value on the partner filer.

• Question 116:

  UNIX allows file access based on___________.

  A. NT ACLs and UNIX permissions.
  B. NT ACLs and SID.
  C. GID or UID and UNIX permissions.
  D. GID or UID and ACLs.
  C. GID or UID and UNIX permissions.

  ---

  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.

• Question 117:

  Which three statements are true about SnapLock volumes? (Choose three.)

  A. SnapMirror supports SnapLock volumes.
  B. There are two types of SnapLock volumes.
  C. SnapLock volumes support per-file retention periods.
  D. In Data ONTAP 7.2.5.1 and later, SnapLock Compliance volumes are not supported on the V-Series controller with NetApp Storage.
  A. SnapMirror supports SnapLock volumes.
  B. There are two types of SnapLock volumes.
  C. SnapLock volumes support per-file retention periods.

  ---

  https://library.netapp.com/ecmdocs/ECMP1196889/html/GUID-8ACE3CAB-D338-4AFC-A530- 0D0FEC3B9F94.html The snaplock command manages compliance related functionality on the system. A volume created using the vol command (see na_vol(1)) is a snaplock volume when either the enterprise or compliance option is chosen. Enterprise and compliance SnapLock volumes allow different levels of security assurance. https:// library.netapp.com/ecmdocs/ECMP1196889/html/GUID-D4533C47-441D-41AB-A8A2- 272A2BFC431C.html

  SnapLock operates fundamentally at the file level.

• Question 118:

  What is the maximum distance between a standard clustered pair at 2Gbps?

  A. 10 meters
  B. 50 meters
  C. 100 meters
  D. 500 meters
  D. 500 meters

  ---

  https://communities.netapp.com/servlet/JiveServlet/previewBody/4803-102-1-6405/tr-3548.pdf The maximum cable length supported for 2Gbps is 500m, the same as the max cable length between a NetApp storage system and a FC switch.

  Stretch MetroCluster (sometimes referred to as nonswitched) is simply an active-active configuration that can extend up to 500m depending on speed and cable type. It also includes synchronous mirroring (SyncMirror? and the ability to do a site failover with a single command. See Figure 2. Additional resiliency can be provided through the use of multipathing.

  

• Question 119:

  When using MetroCluster in a forced takeover mode, identify two methods for restricting access to the disaster site node. (Choose two.)

  A. Use manual fencing.
  B. Use the cf giveback -f command.
  C. Use the cf forcetakeover -d command.
  D. Turn off power to the disaster site node.
  E. Isolate the failed node from the surviving node.
  A. Use manual fencing.
  D. Turn off power to the disaster site node.

• Question 120:

  What is the correct format for the scheduling component of a SnapVault schedule?

  A. cnt[@day_list][@hour_list]
  B. YYYY-MM-DD
  C. Crontable format
  D. List of dates in ISO Date format
  A. cnt[@day_list][@hour_list]

  ---

  https://library.netapp.com/ecmdocs/ECMP1196979/html/man1/na_snapvault.1.html http:// www.geekyfacts.com/index.php?option=com_contentandview=articleandid=64:snapvault snapvault snap sched [ -f ] [ -x ] [ -o options ] [ volname

  [ snapname [ schedule ]]] schedule is cnt[@day_list][@hour_list] or cnt [@hour_list][@day_list] In the schedule, cnt tells SnapVault how many of the snapshots to keep for primaries and for non- SnapLock secondary volumes. The snapshots

  will be numbered newest to oldest from 0 to cnt-1. When creating a new snapshot, SnapVault will delete the oldest snapshots, increment by one the number on the remaining snapshots and then create a new number 0 snapshot. If a

  snapshot is missing from the sequence (e.g. sv.0, sv.1, and sv.3 exist but sv.2 does not), only snapshots that need to be renumbered to make room for the new sv.0 snapshot will be renumbered. In the example, sv.0 and sv.1 would be

  renamed to sv.1 and sv.2, but sv.3 would remain unchanged.

  The cnt in the schedule is interpreted differently for SnapVault secondary SnapLock volumes. For SnapLock secondary volumes, snapshots are created with a name that includes an encoded date and time of when the snapshot is created.

  These snapshots are never renamed and they are never automatically deleted. These snapshots may be deleted using snap delete after the retention period of the snapshot has expired. If cnt is 0, no snapshots will be taken. If cnt is any nonzero value, snapshots will be taken and no snapshots will be automatically deleted. If specified, the day_list specifies which days of the week the snapshot should be created. The day_list is a comma-separated list of the first three letters of

  the day:

  mon, tue, wed, thu, fri, sat, sun. The names are not case sensitive. Day ranges such as mon-fri can also be given. The default day_list is mon-sun, i.e. every day.

  If specified, the hour_list specifies which hours of the day the snapshot should be created, on each scheduled day. The hour_list is a comma-separated list of the hours during the day, where hours are integers from 0 to 23. Hour ranges such

  as 8-17 are allowed. Also, step values are allowed in conjuction with ranges. For example, 0-23/2 means "every two hours". The default hour_list is 0, i.e.

  midnight on the morning of each scheduled day.