[Solved] A microservice uses this code snippet for graceful degradation:try { data = fetchFromService() } catch (Exception e) { data = null } return data.toString()What is the main problem with this code? | Microservices

Microservices - Resilience Patterns

A microservice uses this code snippet for graceful degradation:

try {
  data = fetchFromService()
} catch (Exception e) {
  data = null
}
return data.toString()

What is the main problem with this code?

AIt does not handle exceptions properly

BIt returns null.toString() causing a runtime error

CIt always returns an empty string

DIt retries the service call infinitely

Step-by-Step Solution

Solution:

Step 1: Understand exception handling and return statement
If fetchFromService() fails, data is set to null, then data.toString() is called.
Step 2: Identify the error caused by calling toString() on null
Calling toString() on null causes a runtime NullPointerException or similar error.
Final Answer:
It returns null.toString() causing a runtime error -> Option B
Quick Check:
Calling toString() on null causes error [OK]

Quick Trick: Calling method on null causes runtime error [OK]

Common Mistakes:

MISTAKES

Master "Resilience Patterns" in Microservices

9 interactive learning modes - each teaches the same concept differently

More Microservices Quizzes

A microservice uses this code snippet for graceful degradation: