A transit authority must let guest users share a public IPv4 address outbound while publishing one civic web portal on a fixed public IP. Which NAT combination matches those goals?
Select an answer to reveal the explanation.
Short Explanation
Guests share the on-ramp with PAT—many insides, one (or few) public outsides. The portal needs a reserved parking spot: static NAT to a fixed public IP. Mix those two and you cover casual browsing plus a published service.
Full Explanation
PAT/NAT overload multiplexes many private clients onto shared public addresses for outbound Internet. Static NAT creates a persistent one-to-one mapping suitable for inbound publishing of a portal. Reversing those roles, omitting the portal mapping, or avoiding NAT entirely with scarce public IPv4 fails the dual requirement.