Which statement about NFS and RPC port management is true?

• A. The NFS service must be started before the RPC service. Otherwise, NFS cannot register port information with RPC.
• B. RPC provides information sharing during the NFS working process.
• C. RPC manages NFS port allocation in a unified manner.
• D. During the NFS working process, requests from the client can skip RPC and be directly sent to the server.

Answer: (C)

RPC takes care of NFS port management by using a port mapper (also known as rpcbind) to register and discover the ports used by NFS’s RPC services. The NFS server registers its RPC program number and version with the port mapper, which assigns a port and keeps the mapping. When a client needs to talk to NFS, it asks the port mapper for the port associated with the NFS RPC service and then sends its RPC requests to that port. This centralizes and unifies how ports are allocated and found, even though the actual port numbers can be dynamic. That’s why the statement about RPC managing NFS port allocation in a unified manner is true.

Other options don’t fit as well: the startup order isn’t the defining factor for port registration—RPC must be available for registration, but it isn’t a strict rule that NFS must start first. RPC is not about information sharing during NFS operation, but about enabling remote procedure calls. And NFS communications are performed through RPC; requests can’t skip RPC and go directly to the server.