[Solved] Examine this REST API function designed for graceful degradation:async function fetchUserProfile() { try { const profile = await getFullProfile();... } }What is the key issue in this implementation? | Rest API

Rest API - Rate Limiting and Throttling

Examine this REST API function designed for graceful degradation:

async function fetchUserProfile() {
  try {
    const profile = await getFullProfile();
    return profile;
  } catch (error) {
    getBasicProfile();
  }
}

What is the key issue in this implementation?

AThe function does not log the error for debugging purposes.

BThe try block does not handle asynchronous errors properly.

CThe fallback function getBasicProfile() is called but its result is not returned.

DThe function should throw the error instead of catching it.

Step-by-Step Solution

Solution:

Step 1: Analyze the try block
The function awaits getFullProfile() and returns its result if successful.
Step 2: Analyze the catch block
In the catch block, getBasicProfile() is called but its result is not returned, so the function implicitly returns undefined.
Final Answer:
The fallback data is not returned, causing the function to fail graceful degradation. -> Option C
Quick Check:
Ensure fallback results are returned [OK]

Quick Trick: Always return fallback data in catch blocks [OK]

Common Mistakes:

MISTAKES

Ignoring the need to return fallback data
Assuming calling fallback function is enough
Not handling async errors properly

Master "Rate Limiting and Throttling" in Rest API

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More Rest API Quizzes

Examine this REST API function designed for graceful degradation:

Step 1: Analyze the try block

Step 2: Analyze the catch block

Final Answer:

Quick Check:

Want More Practice?