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?
Scenario: You are storing configuration settings for your application in Consul's K/V store, and each setting is critical to the successful implementation of the application.
A developer recently updated the value for app1, causing the deployment to fail.
What Consul feature can be used to monitor the K/V store for updates and automatically take action to remediate the issue?