Which two NAS servers must be configured with DNS support? (Choose two.)

Question

Options

• AServers that are configured as Standalone.
• BServers that are joined to Active Directory.
• CServers that are accessed through S3 protocol.
• DServers that are used for Multiprotocol access.
• EServers that are used as FTP servers.

• A
  12% (4)
• B
  82% (27)
• C
  3% (1)
• E
  3% (1)

Explanation

DNS is required for Active Directory-joined servers (B) because AD relies entirely on DNS to locate domain controllers, resolve Kerberos authentication service records (SRV), and allow clients to find the NAS server within the domain - without DNS, AD authentication simply cannot function. Multiprotocol servers (D) must also have DNS because they simultaneously serve Windows (SMB/CIFS) and Unix/Linux (NFS) clients, and consistent DNS-based name resolution is what allows both client ecosystems to locate and interoperate with the same NAS server correctly.

The distractors are wrong for these reasons: Standalone (A) servers operate independently without domain membership, so simple IP-based or local name resolution suffices. S3 (C) is an object storage protocol accessed over HTTP/HTTPS and doesn't require server-side DNS configuration to function. FTP (E) is a basic file transfer protocol that works fine with IP addresses and has no inherent DNS dependency.

Memory tip: Think "cross-system communication requires DNS" - both AD (cross-domain) and Multiprotocol (cross-OS) must coordinate name resolution across different systems or client types, making DNS non-negotiable in both cases.

No community discussion yet for this question.