Service Discovery — Eureka — Concept Check
Questions on Service Discovery — Eureka. Service instances register with a registry (Eureka, Consul) on startup; clients query the registry or use client-side load balancing (Ribbon/Spring Cloud LoadBalancer) to resolve addresses.
Questions in this quiz
8 questions on Service Discovery — Eureka — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.An instance of a microservice registered with Eureka is not visible to clients immediately after startup. What could be the reason?
- AThe Eureka server is down.
- BThe instance did not register with Eureka.
- CThe registry cache on clients updates every 30 seconds.
- DThe instance failed to send a heartbeat.
2.A service instance registered with Eureka stops sending heartbeats. What will happen after 90 seconds?
- AThe instance will be evicted from the registry.
- BThe instance will automatically restart.
- CThe instance will continue to be available.
- DThe instance will be marked as unhealthy but remain registered.
3.In a Spring Cloud application using Eureka, what does the annotation `@LoadBalanced` enable?
- AService health checks.
- BDynamic scaling of instances.
- CAutomatic registration with Eureka.
- DResolution of `lb://` URIs to service instances.
4.A developer believes that Kubernetes requires Eureka for service discovery. What is the correct approach in Kubernetes?
- ARely on external DNS providers.
- BUse Kubernetes Services for DNS-based discovery.
- CUse Eureka for internal service resolution.
- DDeploy Eureka alongside Kubernetes.
5.What happens if a Eureka client sets `register-with-eureka` to `false`?
- AThe client will not be able to discover other services.
- BThe client will not send heartbeats.
- CThe client will not cache the registry.
- DThe client will not register itself with the Eureka server.
6.A microservice using Spring Cloud LoadBalancer is experiencing uneven load distribution. What could be the issue?
- AThe Eureka server is not running.
- BThe service instances are not registered.
- CThe clients are not using `lb://` URIs.
- DThe load balancing algorithm may not be set to round-robin.
7.A developer claims that Eureka automatically scales instances based on load. Why is this incorrect?
- AEureka handles service discovery, not scaling.
- BEureka relies on Kubernetes for scaling.
- CEureka uses client-side load balancing for scaling.
- DEureka scales instances based on health checks.
8.What is the default lease renewal interval for a service instance in Eureka?
- A30 seconds
- B90 seconds
- C15 seconds
- D60 seconds