Microservices Service Discovery and Registry 2

Question 1

In client-side service discovery, which component is responsible for selecting a specific service instance to call?

Accepted Answer

The client itself

Answer

The service registry

Answer

A central load balancer

Answer

The API gateway only

Question 2

What is the main drawback of client-side service discovery?

Accepted Answer

Discovery logic must be implemented in every client

Answer

It requires a dedicated DNS server

Answer

It cannot use a service registry

Answer

It only works with synchronous calls

Question 3

In server-side service discovery, where does the client send its request?

Accepted Answer

To a router or load balancer that queries the registry

Answer

Directly to a chosen instance

Answer

To the registry first, then the instance

Answer

To a DNS cache only

Question 4

Which AWS feature is a common example of server-side service discovery?

Accepted Answer

Elastic Load Balancer with target groups

Answer

S3 bucket policies

Answer

CloudFront edge caching

Answer

IAM roles

Question 5

A benefit of server-side discovery over client-side discovery is that:

Accepted Answer

Discovery logic is centralized and abstracted from clients

Answer

It eliminates the need for any registry

Answer

It guarantees zero network latency

Answer

Clients no longer need network access

Question 6

Which tool is commonly used as a dedicated service registry in microservices?

Accepted Answer

Netflix Eureka

Answer

Redis Pub/Sub

Answer

Apache Kafka

Answer

Nginx static config

Question 7

What information does a service typically provide when registering with a registry?

Accepted Answer

Network location (host/IP and port) and metadata

Answer

Only its name

Answer

Its source code

Answer

The full request payload