Storage Admin HubConfiguration · Protection · Recovery
Interview Q&A · ONTAP 9

NetApp interview: basic questions and answers

Ten foundation questions on ONTAP objects, NAS, SAN, snapshots, capacity and health.

Scenario

For junior through experienced administrator interviews, answer the definition first, then give a small operational example. These questions build the vocabulary used in the advanced and expert sets.

Before you change production

Commands and screens can differ by release and platform. Replace example names and documentation IP addresses. Check prerequisites, impact, current health and rollback with your change owner.

1. What are the main components of an ONTAP cluster?

  1. A cluster contains one or more nodes, commonly arranged in high-availability pairs. Data SVMs provide client-facing storage services. Aggregates or local tiers hold physical capacity; FlexVol volumes hold logical data; LIFs provide network access. A single client request crosses several of these objects.
  2. Example: a Linux client mounts /projects using an SVM NFS data LIF. The /projects junction maps to a FlexVol volume backed by a local tier on a node. Its HA partner can take over storage if the owner node fails, provided the supported design and client network paths are healthy.
Read-only example
cluster show
storage failover show
vserver show
volume show
Verify

You can trace client address → SVM → volume → storage placement → HA partner.

2. What is a data LIF and how is it different from a management LIF?

  1. A logical interface has an IP address and a role/service assignment. Data LIFs carry client NFS, SMB or SAN traffic for a data SVM. Cluster and node management LIFs carry administrative access; intercluster LIFs handle cluster peering and replication traffic. The service a LIF carries matters as much as its address.
  2. Example: an admin logs in to the cluster management address to inspect a volume while Linux clients use 192.0.2.30 as the NFS data endpoint. A healthy admin login does not prove the NFS VLAN or client route is working.
Read-only example
network interface show
network port show
Verify

Name which address the administrator, NFS client and SnapMirror transfer each use.

3. What is the difference between an aggregate and a volume?

  1. The aggregate or local tier groups physical storage and supplies usable capacity and performance. A volume is the logical container presented through a NAS namespace or used to hold SAN LUNs. Many volumes can share a tier; resizing a volume does not create physical disks or guarantee free aggregate capacity.
  2. Example: a 2 TiB thin-provisioned volume can show ample logical free space while the local tier is nearly full because other volumes, snapshots or metadata consume capacity. Check volume and tier space together before enlarging a volume or promising an application more storage.
Read-only example
storage aggregate show
volume show-space
Verify

Explain logical volume free space versus shared physical headroom.

4. What is a junction path in ONTAP NAS?

  1. A junction path mounts a volume into an SVM namespace. NFS clients traverse that namespace through the SVM data LIF; SMB shares can point to a path within it. A volume can be online yet inaccessible at the expected path if its junction is absent or the parent path has unsuitable permissions.
  2. Example: vol_projects mounted at /projects is exported to one Linux subnet. Verify the volume junction and the export policy for /projects and parent traversal before changing client mount syntax.
Read-only example
volume show -fields junction-path,policy
vserver export-policy rule show
Verify

Explain why an online volume is not enough to make /projects mountable.

5. How do NFS and SMB differ as NAS protocols?

  1. Both provide file access, but NFS clients typically use UNIX identity and export-policy rules, whereas SMB commonly uses Windows/AD authentication, share permissions and NTFS ACLs. Exact versions and security flavors change behavior; neither protocol grants access based solely on network reachability.
  2. Example: an NFS client gets access denied because its IP does not match an export rule; an SMB user connects but cannot write because the share permits browsing while a file ACL denies creation. Diagnose at the appropriate authorization layer.
Verify

Name a protocol-specific identity, policy and client command for each.

6. What are a LUN and an igroup?

  1. A LUN is a block device within an ONTAP volume. An igroup lists approved host initiators: iSCSI IQNs or FC WWPNs. A LUN mapping associates the LUN with an igroup and presents a LUN ID, enabling that host to discover it over its valid target paths.
  2. Example: mapping lun_db to an igroup for linux01 does not format it or create a Linux filesystem. The host must discover the correct serial and supported multipath topology before any filesystem or datastore operation.
Read-only example
lun show
igroup show
lun mapping show
Verify

Explain how host transport visibility differs from LUN authorization.

7. What is a Snapshot and what does it consume?

  1. An ONTAP snapshot is a point-in-time view of a volume based on shared block references. Creation is efficient because it does not make a full second copy at that moment; as active data changes, blocks retained by snapshots can consume additional capacity. A snapshot on the same cluster cannot replace an off-cluster DR copy.
  2. Example: an hourly snapshot allows a quick file restore after accidental deletion. If a large file changes repeatedly, snapshots can retain older blocks and increase physical use. Monitor snapshot space, volume headroom and local-tier headroom together.
Read-only example
volume snapshot show
volume show-space
Verify

Distinguish quick local recovery from site-level recovery.

8. What is SnapMirror and what is RPO?

  1. SnapMirror replicates data or selected recovery points to a destination under a relationship policy and schedule. RPO is the maximum acceptable data loss measured in time, not simply the configured schedule. Actual transfer completion and lag must meet it.
  2. Example: hourly asynchronous updates can leave up to roughly one interval plus any failed or delayed transfer worth of recent writes unavailable after a source outage. A healthy relationship with excessive lag can still miss the business RPO.
Read-only example
snapmirror show -fields health,lag-time,last-transfer-error
Verify

Explain why “schedule hourly” is not proof of an achieved one-hour RPO.

9. What is takeover versus giveback?

  1. Takeover moves service responsibility from a failed or maintained HA node to its partner. Giveback returns storage ownership after the original node is ready. Availability still depends on correct network paths, disk connectivity and host multipath or NAS client behavior.
  2. Example: before planned maintenance, check that both nodes are healthy and takeover is possible. After giveback, confirm both nodes return to intended ownership, client access remains available and there are no unresolved hardware or failover alerts.
Read-only example
storage failover show
cluster show
system health alert show
Verify

State the precheck and client validation, not only the takeover command.

10. What should a daily storage health check include?

  1. Check node/HA status, hardware alerts, aggregate and volume space, data LIFs, protocol service health, SnapMirror lag/errors, backups and recent events. Prioritize any user impact or protection failure over a cosmetic warning. Compare with a baseline and ticket already known issues.
  2. Example: volume usage is 72%, but its containing aggregate has only 4% physical headroom and the DR transfer has failed twice. The cluster is still serving I/O, yet capacity and recoverability need action. Document owner, threshold and next check time.
Read-only daily sample
cluster show
storage failover show
system health alert show
storage aggregate show
volume show-space
snapmirror show
Verify

Produce an actionable finding rather than a screen capture of healthy output.