Question 1

Which of the following are benefits of using Consul for service discovery? (select 3)

Options :

A :

simplified communication between microservices

B : reduction or elimination of load balancers for east/west traffic

C : single point of contact for a service where the underlying containers may be dynamic or frequently change

D : scheduling of services and containers for application redundancy

Answer: A,B,C

Question 2

Which of the following is responsible for managing membership and broadcasting messages to the cluster?

Options :

A : Raft (Paxos)

B : Discovery chain

C : Serf (SWIM)

D : Prepared Queries

Answer: C

Question 3

Scenario: You have multiple services registered with Consul for your e-commerce site, including the front-end service, the shipping service, the inventory service, and the

cart service. To safeguard your customer's shipping addresses, you want to ensure that communication between the front-end and the shipping service is denied and that

traffic is only permitted from the cart service.

What feature of Consul Connect can you use to permit access to the shipping service from the cart service and deny communication from the front-end service?

Consul-Associate-Part-2-Q57-page32-image4

Options :

A : Intentions

B : Consul agent

C : Consul ACLs

D : Consul Namespaces

Answer: A

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

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