A library kiosk NodePort Service must preserve the client source IP for audit logs and avoid an extra SNAT hop on nodes that have local endpoints. Which Service field setting supports that goal?
Select an answer to reveal the explanation.
Short Explanation
Want the original visitor IP on the kiosk logs? externalTrafficPolicy: Local keeps external traffic on nodes that actually run the Pod and skips the extra hop that rewrites the source. Session affinity and headless Services solve different problems.
Full Explanation
For NodePort and LoadBalancer Services, externalTrafficPolicy: Local routes external traffic only to endpoints on the receiving node and preserves the client source IP by avoiding SNAT through another node. The Cluster default policy may hop to any ready endpoint and SNAT the source. sessionAffinity, publishNotReadyAddresses, and headless (clusterIP: None) Services do not provide that external source-IP preservation behavior.