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 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=

2.

3. ==> Removing gossip encryption key...

4. error: Unexpected response code: 500 (12 errors occurred:

5. * WAN error: 5/5 nodes reported failure

6. * CONSUL-NODE-A.dc-1: Removing the primary key is not allowed

7. * CONSUL-NODE-C.dc-1: Removing the primary key is not allowed

8. * CONSUL-NODE-B.dc-1: Removing the primary key is not allowed

9. * CONSUL-NODE-D.dc-1: Removing the primary key is not allowed

10. * CONSUL-NODE-E.dc-1: Removing the primary key is not allowed

11. * dc-1 (LAN) error: 5/5 nodes reported failure

12. * CONSUL-NODE-E: Removing the primary key is not allowed

13. * CONSUL-NODE-A: Removing the primary key is not allowed

14. * CONSUL-NODE-D: Removing the primary key is not allowed

15. * CONSUL-NODE-B: Removing the primary key is not allowed

16. * CONSUL-NODE-C: Removing the primary key is not allowed

Options :

A :

wait until the old key is invalidated by Consul based upon the configured validity date

B : configure Consul to use the new key using the consul keyring -use command

C :

the original gossip key on a Consul cluster cannot be deleted

D : wait for Raft to replicate the new key across all cluster nodes before you can remove it

Answer: A

Question 3

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?

Options :

A :

the response only included the three underutilized nodes

B :

the DNS query must specify how many nodes to return in the response

C : the health check is failing for the other two servers

D : Consul has a maximum response of three nodes in a given DNS query

Answer: C

Question 4

True or False? A service definition can include multiple health checks.

Options :

A : false

B : true

Answer: B

Question 5

When storing data in the Consul K/V, what type of nodes will replicate the Consul K/V data to ensure high availability.

Options :

A : all servers, including servers in all Consul federated datacenters

B : clients within the local Consul datacenter

C : servers within the local Consul datacenter

D : both clients and servers within the local Consul datacenter

Answer: C

Higher Test Marks with Free Online Consul-Associate Exam Practice

Buying Options: