Scenario: You have an application that uses Consul service discovery to connect to backend services in order to process data submitted by end-users. The front-end web
service consists of 3 containers, while the backend service consists of 5 static virtual machines. All of the front-end web servers and the backend servers are registered
with Consul.
During normal operations, a user complains that the data processing is taking too long. To troubleshoot, you run a DNS query against the DNS name for the backend
service, but discover that the response only contains three of the virtual machines. Why would Consul only respond with three servers rather than all five?
You need to deny communication between the customer-db service and the payment service using an intention. You open the command line and issue the following
command:
$ consul intention create customer-db payment
However, the two services can still initiate new connections even after the intention is created. What would explain this?
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?
You have created a new gossip encryption key using consul keygen and installed it using the command consul keyring -install
TX/1dsj67x/4XdTeSG1Cb5RdC/cbAbv9Hch4H8cL8nk=.
However, when you try and delete the original gossip encryption key, you receive an error. Based on the error message below, what steps need to be taken in order to be
able to remove the old gossip encryption key?
1. $ consul keyring -remove /d+jMNoQWICjMvddXJXzyGPDWiEOFgApvUJcuPRcves=