Bird
0
0

Which HTTP method is NOT considered safe and idempotent according to REST principles?

easy📝 Syntax Q12 of 15
Rest API - REST API Fundamentals
Which HTTP method is NOT considered safe and idempotent according to REST principles?
APOST
BPUT
CGET
DDELETE
Step-by-Step Solution
Solution:
  1. Step 1: Recall safe and idempotent HTTP methods

    GET, PUT, and DELETE are idempotent; GET is safe. POST is neither safe nor idempotent.
  2. Step 2: Identify the method that is not safe and idempotent

    POST changes server state and can create multiple resources, so it is not idempotent or safe.
  3. Final Answer:

    POST -> Option A
  4. Quick Check:

    POST is not safe or idempotent [OK]
Quick Trick: POST changes data and is not idempotent [OK]
Common Mistakes:
  • Thinking PUT is unsafe
  • Confusing DELETE as unsafe
  • Assuming GET modifies data

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Rest API Quizzes