Spring Cloud Professional Standards & Competencies 5

Question 1

Which metric dimension should a Spring Cloud architect monitor to assess the health of a circuit breaker in production?

Accepted Answer

Circuit breaker state (CLOSED, OPEN, HALF_OPEN), call volume, and failure rate

Answer

Monitoring circuit breaker state transitions, call volume, and failure rate together provides a complete picture of dependency health and failure tolerance.

Question 2

What does following the 12-Factor App principle of 'backing services' mean in the context of Spring Cloud configuration?

Accepted Answer

Databases, queues, and caches should be treated as attached resources configured via environment or config server, not hardcoded

Answer

Treating backing services as attached resources means their connection details come from configuration (not code), enabling seamless environment promotion and swapping.

Question 3

A senior engineer notices that Spring Cloud microservices are making synchronous HTTP calls for operations that don't require immediate responses. What professional improvement should they recommend?

Accepted Answer

Refactor to event-driven, asynchronous messaging via Spring Cloud Stream

Answer

Replacing unnecessary synchronous calls with asynchronous event-driven messaging via Spring Cloud Stream reduces coupling and improves overall system resilience and throughput.

Question 4

What is the professional implication of setting a very low timeout on a Feign client in Spring Cloud?

Accepted Answer

It can cause premature failures for operations that legitimately need more processing time, increasing error rates

Answer

Excessively low timeouts cause valid requests to fail unnecessarily; timeouts must be calibrated against actual P99 response time baselines with headroom for variance.

Question 5

Which Spring Cloud practice supports the principle of 'design for failure' in distributed systems?

Accepted Answer

Implementing timeouts, retries with exponential backoff, circuit breakers, and fallbacks for every inter-service call

Answer

Designing for failure means proactively implementing resilience patterns — timeouts, retries, circuit breakers, and fallbacks — so partial failures don't cascade into full outages.

Spring Cloud Practice Test

Spring Cloud Practice Test

Spring Cloud Professional Standards & Competencies 5