Question 1

You need to determine the leader node for the Consul cluster. What command allows you to quickly identify the nodes and their current roles within the cluster?

Example of the command's output:

1. Node ID Address State Voter RaftProtocol

2. CONSUL-NODE-A 121abb4c-16fb-c8ec-2e2b-9595925de4dc 10.0.10.238:8300 follower true 3

3. CONSUL-NODE-C 4bead426-4471-0924-598f-cd6ce0015ebc 10.0.10.48:8300 follower true 3

4. CONSUL-NODE-E c44e8ab1-1132-1b22-9501-479c690c9e1b 10.0.10.105:8300 leader true 3

5. CONSUL-NODE-D ba86541f-cd93-6ada-b763-709b0fc6c09f 10.0.11.163:8300 follower true 3

6. CONSUL-NODE-B 2528cba1-06ea-4837-fc7b-13e44af19b0d 10.0.11.141:8300 follower true 3

Options :

A : consul nodes -leader

B : consul members

C :

consul raft- list

D :

consul operator raft list-peers

Answer: D

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

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

Question 4

Given the following screenshot, what path would you use to access the value shown?

Consul-Associate-Part-1-Q57-page28-image4

Options :

A : key/values/app1/config

B : kv/app1/config

C : app1/config/database

D : app1/config

Answer: C

Question 5

Scenario: You're deploying Consul in a dedicated environment, and due to the complex network layout, you are forced to funnel traffic through a firewall that will perform

a NAT (network address translation) for the Consul node. What configuration parameter can be used to identify what IP address that the other nodes in the cluster should

use to communicate with Consul?

Options :

A :

-client

B :

-bind

C :

-serf-lan-bind

D : -advertise

Answer: D

Higher Test Marks with Free Online HCCAO-003 Exam Practice

Buying Options: