Your organization uses NFS to share data from Oracle Solaris servers to Oracle Solaris clients. For the nfsmapid daemon to work properly the client and server must be on the same domain. Select the…

Question

Options

• Athe nfsmapid_domain parameter in the mapid SMF service.
• Bthe nfsmapid_domain parameter in the /etc/default/nfs file
• Cthe domain name in the /etc/default/domainname file, if it exists.
• Da_nfsv4idmapdomain TXT record found by the configured domain name servers

• A
  83% (30)
• B
  3% (1)
• C
  6% (2)
• D
  8% (3)

Explanation

Option A is correct because Oracle Solaris's Service Management Facility (SMF) is the authoritative, runtime configuration layer - the nfsmapid_domain property set directly on the mapid SMF service takes highest precedence, overriding all other sources. Option B (/etc/default/nfs) is the second-highest source, but it is a legacy flat-file configuration that SMF properties supersede. Option C (/etc/default/domainname) is checked even later in the lookup chain and only applies if the file exists. Option D (the DNS _nfsv4idmapdomain TXT record) is the fallback of last resort, used only when no explicit configuration is found locally.

Memory tip: Think of the precedence as "newest wins" - SMF is Oracle Solaris's modern service framework and always outranks old-style config files (/etc/default/*), which in turn outrank external DNS lookups. If you can set it in SMF, that setting rules.

No community discussion yet for this question.