Question 274 of 2,015
REST APIs and Data ModelsmediumMultiple SelectObjective-mapped

Quick Answer

The correct answer identifies PUT as idempotent and GET as safe, because idempotent methods guarantee that multiple identical requests produce the same server state, while safe methods do not modify any resource. PUT achieves idempotency by replacing the entire resource at the target URI with the payload, so calling it once or a hundred times yields the same result. On the ENCOR 350-401 exam, this distinction tests your understanding of RESTful design principles, often appearing in a "choose two" format where common traps include confusing POST or PATCH as idempotent. Remember that safe methods are read-only (GET, HEAD, OPTIONS), while idempotent methods include PUT and DELETE—but not POST, which creates new resources, and not PATCH, which applies partial updates and is typically non-idempotent. A helpful mnemonic: "Safe is for sight, idempotent is for repeats—PUT and DELETE are repeat-friendly, POST is not."

CCNP REST APIs and Data Models Practice Question

This 350-401 practice question tests your understanding of rest apis and data models. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.

Which two statements about REST API HTTP methods are true? (Choose two.)

Question 1mediummulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

GET is a safe method that must not change server state.

The correct answers are A and D. A is correct because GET is defined as a safe method that does not modify server state. D is correct because PUT is idempotent — multiple identical requests produce the same result. B is incorrect because POST is not idempotent; it often creates new resources. C is incorrect because DELETE is idempotent, not non-idempotent. E is incorrect because PATCH is typically non-idempotent unless applied carefully.

Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • GET is a safe method that must not change server state.

    Why this is correct

    Correct because GET is defined as safe and idempotent in REST.

    Related concept

    Static NAT maps one inside address to one outside address.

  • POST is idempotent, meaning multiple identical requests have the same effect.

    Why it's wrong here

    Incorrect because POST is not idempotent; it typically creates new resources.

  • DELETE is non-idempotent and each request may have a different outcome.

    Why it's wrong here

    Incorrect because DELETE is idempotent; after the first deletion, subsequent requests return the same result.

  • PUT is idempotent and replaces the entire resource at the target URI.

    Why this is correct

    Correct because PUT is idempotent and replaces the resource.

    Related concept

    Static NAT maps one inside address to one outside address.

  • PATCH is always idempotent because it uses a patch document.

    Why it's wrong here

    Incorrect because PATCH is not necessarily idempotent; it depends on the patch semantics.

Common exam traps

Common exam trap: NAT rules depend on direction and matching traffic

NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.

Detailed technical explanation

How to think about this question

NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.

KKey Concepts to Remember

  • Static NAT maps one inside address to one outside address.
  • PAT allows many inside hosts to share one public address using ports.
  • Inside local and inside global describe the private and translated addresses.
  • NAT ACLs identify traffic for translation, not always security filtering.

TExam Day Tips

  • Identify inside and outside interfaces first.
  • Check whether the scenario needs static NAT, dynamic NAT or PAT.
  • Do not confuse NAT matching ACLs with normal packet-filtering intent.

Key takeaway

NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.

Real-world example

How this comes up in practice

A small business has 20 workstations on the 192.168.1.0/24 network and one public IP from its ISP. The router uses PAT (NAT overload) so all 20 devices share one public address using different source ports. NAT questions test whether you understand the four address terms and which direction each translation applies.

What to study next

Got this wrong? Here's your next step.

Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related 350-401 NAT questions on configuration and troubleshooting.

Related practice questions

Related 350-401 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free 350-401 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this 350-401 question test?

REST APIs and Data Models — This question tests REST APIs and Data Models — Static NAT maps one inside address to one outside address..

What is the correct answer to this question?

The correct answer is: GET is a safe method that must not change server state. — The correct answers are A and D. A is correct because GET is defined as a safe method that does not modify server state. D is correct because PUT is idempotent — multiple identical requests produce the same result. B is incorrect because POST is not idempotent; it often creates new resources. C is incorrect because DELETE is idempotent, not non-idempotent. E is incorrect because PATCH is typically non-idempotent unless applied carefully.

What should I do if I get this 350-401 question wrong?

Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related 350-401 NAT questions on configuration and troubleshooting.

What is the key concept behind this question?

Static NAT maps one inside address to one outside address.

About these practice questions

Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 more ways this is tested on 350-401

These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.

Variation 1. Which two statements about REST API HTTP methods are true? (Choose two.)

medium
  • A.GET requests are idempotent and safe.
  • B.POST requests are idempotent and safe.
  • C.PUT requests are idempotent.
  • D.DELETE requests are safe.
  • E.PATCH requests are always idempotent.

Why A: In REST APIs, the GET method is used to retrieve a representation of a resource without side effects (idempotent and safe). The PUT method is used to update or create a resource at a specific URI and is idempotent, meaning multiple identical requests have the same effect as a single request. POST is not idempotent; it is typically used to create a new resource at a server-defined URI. DELETE is idempotent but not safe. PATCH is used for partial updates and is not necessarily idempotent.

Last reviewed: Jun 18, 2026

Question Discussion

Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.

Loading comments…

Sign in to join the discussion.

This 350-401 practice question is part of Courseiva's free Cisco certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the 350-401 exam.