Server mapping entries have fewer elements than session entries, so it can be applied in...

Explanation From HCIA-Security documents:

A server mapping entry is a lightweight record used to describe a static or semi-static mapping relationship that helps the device forward traffic from an external user to an internal server. Compared with a session entry, it contains fewer fields because it does not need to maintain full connection state information such as TCP state, sequence-related tracking, timers for each direction, and the complete flow 5-tuple details used for every active connection.

In NAT scenarios, server mapping is commonly created for NAT Server (port mapping/port forwarding). This lets Internet users initiate connections to a public IP address and port, and the device translates and forwards the traffic to the specified intranet server and service port.

In ASPF scenarios, server mapping can be used to support certain protocols and service openings by creating an association that guides traffic handling, while the detailed per-connection information is still maintained later in the session table after the connection is established. Because server mapping enables inbound reachability to internal servers with fewer parameters than a full session, the statement is TRUE.