Courseiva
hardMultiple Choice

FC0-U71 Practice Question: A web application needs to send user registration…

A web application needs to send user registration data to a server. Which HTTP method should be used?

⚠ Common exam trap

Many certification exams test the misconception that PUT is the correct method for creating new resources because it is idempotent, but the trap is that PUT requires a known resource URI (e.g., /users/123), whereas POST is used when the server assigns the new resource's identifier, as in user registration.

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

✓

POST

The POST method is designed to submit data to be processed to a specified resource, such as creating a new user registration record on a server. Unlike GET, which appends data to the URL, POST sends the registration data in the request body, making it suitable for non-idempotent operations where each submission creates a new resource or triggers server-side processing.

Answer analysis

Option-by-option breakdown

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

  • ✗

    PUT

    Why it's wrong here

    PUT replaces the resource at a client-specified URI and is idempotent, so repeating the registration overwrites rather than creating a new user each time. It is tempting because it does send a body to the server, and it would be correct when the client already knows the target URI and wants a full replacement.

  • ✗

    DELETE

    Why it's wrong here

    DELETE removes an existing resource identified by its URI and carries no request body semantics for creating records, so it cannot submit registration data. It is tempting because it is a write method that changes server state, and it would be correct when the application must remove a user account or other named resource.

  • ✓

    POST

    Why this is correct

    POST carries registration data in the request body, keeping credentials out of the URL and supporting larger payloads. It satisfies the stem's need to send user data to a server, unlike GET, which appends data to the query string.

  • ✗

    GET

    Why it's wrong here

    GET appends data to the query string, exposing credentials in URLs, logs and browser history, and it is defined as a safe, idempotent retrieval method. It is tempting because it is the simplest way to transmit parameters, and it would be correct when fetching a representation without altering server state.

About these practice questions

This FC0-U71 question is part of Courseiva's 988-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This FC0-U71 practice question is part of Courseiva's free CompTIA 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 FC0-U71 exam.