You have a Consul cluster running production workloads in your environment. However, you've discovered that the cluster was initially deployed without gossip
encryption configured, which means that traffic is being sent in cleartext. The security team has requested this to be updated ASAP. However, you can't take an outage on
the Consul service right now, knowing the server nodes will stop communicating once you start editing the configuration files one by one.
How can you enable gossip encryption on the existing cluster without affecting the services it is currently providing the business?
What are two ways that a client or service can programmatically discover healthy nodes for a service registered in a local Consul cluster? (select two)
Stephen is using Consul for service discovery, but he also wants to store data in the Consul K/V for application variables that need to be retrieved at runtime. However,
the application is currently architected to read data directly from a local file, not from a remote K/V service like Consul.
What Consul feature can Stephen use to retrieve data from Consul without re-architecting the application?