The *LoadBalancer• service type is the most suitable for exposing your TCP-based application on port 8080 to external clients. It will automatically create a load balancer in the cloud provider's infrastructure, allowing external access to your application. Option 'A' (ClusterlP) only allows access from within the cluster. Option 'C' (NodePort) exposes the service on a specific port on each node, making it accessible via the node's IP address. Option 'D' (ExternalName) is for exposing services that are already externally accessible using a DNS name. Option 'E' (Headless) is for services where you want to access Pods directly by their names, which is not the case here.

https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#delete

The Deployment will create 3 Pods with the label 'app: nginx' because the 'selector' and 'template.metadata.labels' sections specify this. The Deployment will use the 'nginx:l. 14.2' image to create the Pods as defined in the 'spec.template.spec.containers' section. The Deployment itself does not create a Service. You would need to create a separate Service resource to expose the Pods on port 80.

Istio's AuthonzationPolicy feature allows you to define granular authorization rules based on request attributes, including headers, user identities, and other context. This enables you to control access to microservices based on specific conditions. Option A is for authentication, not authorization. Option C is for traffic management. Option D is for telemetry. Option E is for service discovery and configuration.

https://kubernetes.io/docs/concepts/overview/working-with-objects/_print/