[Solved] Why might a response envelope include both a 'message' and a 'status' field instead of just one? — Ans: 'status' indicates success or failure; 'message' provides human-readable details | Rest API

Rest API - Request and Response Format

Why might a response envelope include both a 'message' and a 'status' field instead of just one?

A'status' is for developers; 'message' is for machines

B'status' indicates success or failure; 'message' provides human-readable details

C'message' replaces 'status' in error cases only

DBoth fields are redundant and should not be used together

Step-by-Step Solution

Solution:

Step 1: Understand roles of status and message
Status is a simple code like 'success' or 'error'; message explains what happened.
Step 2: Explain why both are useful
Clients use status to check flow; message helps users or developers understand details.
Final Answer:
'status' indicates success or failure; 'message' provides human-readable details -> Option B
Quick Check:
Status = code, message = explanation [OK]

Quick Trick: Status codes flow; messages explain details [OK]

Common Mistakes:

Master "Request and Response Format" in Rest API

9 interactive learning modes - each teaches the same concept differently

More Rest API Quizzes

Why might a response envelope include both a 'message' and a 'status' field instead of just one?