Question 1

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?

Options :

A : set up an ACL to automatically restart the Consul service when a value is changed

B :

configure a watch and execute a script to update the application

C : set up health checks to monitor for changes to the K/V store

D : use the raft consensus protocol to replicate the changes from the other nodes when a value is changed

Answer: A

Question 2

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?

Options :

A :

Generate the new encryption key using consul keygen. Update all the Consul server agent configuration files with the new encryption key. Using a scheduling tool,

execute the consul reload command for all nodes at the same time. This will ensure that there is minimal downtime for the Consul service.

B :

Generate the new encryption key using consul keygen. Update each Consul agent configuration file with the new configuration and set additional parameters to

verify incoming and outgoing encryption to false. Use rolling updates to walk through the steps of ultimately setting the parameters to true.

C :

Generate the new encryption key using consul keygen. Use the command consul keyring -install <key> and push the new encryption key out to all participating

nodes in the cluster. Finally, use the command consul keyring -use <key> to instruct Consul to use the key for encryption

D :

Generate the new encryption key using consul keygen. Update the Consul server agent configuration files with the new encryption key and issue a kill -HUP

<process ID> command so the Consul service reloads and picks up the new gossip configuration. Update and restart as a rolling update across the cluster so only a

single node is offline at a time.

Answer: B

Question 3

Which of the following are valid Consul watch types that you can use to monitor updates in Consul? (select five)

Options :

A : keyprefix

B : service

C : services

D : login

E : nodes

F : alarm

G : key

Answer: A,B,C

Question 4

You have two Consul datacenters and you want to enable federation so services in dc1 can discover services in dc2. You run the consul join wan node2.example.com.

However, servers in dc1 can not communicate with servers in dc2 and vice versa. Based on the snippets of the server configuration files can be found below, why would

this be assuming network connectivity is working as expected?

dc1 configuration

1. "datacenter": "dc1",

2. "server": true,

3. "key_file": "/etc/consul.d/cert.key",

4. "cert_file": "/etc/consul.d/client.pem",

5. "ca_file": "/etc/consul.d/chain.pem",

6. "verify_incoming": true,

7. "verify_outgoing": true,

8. "verify_server_hostname": true,

9. "ui": true,

10. "encrypt": "XIUEktl3YjG9KPJfaBU1xE69IZ0XhsNCSH423FyknJE=",

11. "bootstrap_expect": 5,

12. "enable_syslog": true,

dc2 configuration

1. "datacenter": "dc2",

2. "server": true,

3. "key_file": "/etc/consul.d/cert.key",

4. "cert_file": "/etc/consul.d/client.pem",

5. "ca_file": "/etc/consul.d/chain.pem",

6. "verify_incoming": true,

7. "verify_outgoing": true,

8. "verify_server_hostname": true,

9. "ui": true,

10. "encrypt": "LSBSOZI5+9EX/kdY8u27mX50rk1ywcprfUCoSZjnpUg=",

11. "bootstrap_expect": 5,

12. "enable_syslog": false,

Options :

A : the gossip keys need to match between federated datacenters

B : the verify_incoming setting should be set to false before WAN federation can be configured

C : the client certificates are issued from different CAs

D : the syslog configurations do not match

Answer: A

Question 5

You are using the Consul KV store and need to be able to easily list all of the keys in a given path. What is the easiest way to do so?

Options :

A :

consul kv read -recursive

B : consul kv get -recurse

C : consul kv read

D : consul kv get *.*

Answer: B

Higher Test Marks with Free Online Consul-Associate Exam Practice

Buying Options: