- A
Uses SOAP for message exchange
Why wrong: SOAP is a different protocol, not characteristic of REST.
- B
Maintains server-side session state
Why wrong: REST APIs are stateless; no session state is stored on the server.
- C
Is stateless between requests
Statelessness is a key constraint of REST.
- D
Returns data in JSON format
JSON is a common data format for REST APIs.
- E
Uses HTTP methods like GET and POST
REST APIs rely on HTTP methods for operations.
Question 43 of 1,000
FC0-U61 Software Development Practice Question
This FC0-U61 practice question tests your understanding of software development. 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.
A REST API is used by a mobile app to retrieve data. The API returns responses in a specific format. Which THREE of the following are typical characteristics of a REST API?
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
✓
Is stateless between requests
REST APIs are stateless by design, meaning each request from a client to the server must contain all the information needed to understand and process the request. The server does not store any client context between requests, which improves scalability and reliability. This statelessness is a core constraint of the REST architectural style, as defined by Roy Fielding in his doctoral dissertation.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Uses SOAP for message exchange
Why it's wrong here
SOAP is a different protocol, not characteristic of REST.
- ✗
Maintains server-side session state
Why it's wrong here
REST APIs are stateless; no session state is stored on the server.
- ✓
Is stateless between requests
Why this is correct
Statelessness is a key constraint of REST.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Returns data in JSON format
- ✓
Uses HTTP methods like GET and POST
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that REST APIs must use JSON exclusively, but while JSON is common, REST can return data in any format (e.g., XML, HTML, plain text) as long as it adheres to REST constraints.
Detailed technical explanation
How to think about this question
Under the hood, REST leverages HTTP methods (GET, POST, PUT, DELETE) as verbs to perform CRUD operations on resources identified by URIs. Statelessness means that each HTTP request is independent, so load balancers can distribute requests to any server without needing sticky sessions, which is critical for horizontal scaling in cloud environments. A real-world scenario is a mobile banking app where each API call includes an authentication token (e.g., JWT) in the header, ensuring the server does not need to remember previous login states.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A practitioner preparing for the FC0-U61 exam encounters this exact type of scenario on the job. The correct answer here is not the most general option — it is the best answer for the specific constraint described. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Real exam questions reward reading the full scenario before eliminating options, because the constraint defines which answer fits.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Software Development — study guide chapter
Learn the concepts, then practise the questions
- →
Software Development practice questions
Targeted practice on this topic area only
- →
All FC0-U61 questions
1,000 questions across all exam domains
- →
CompTIA ITF+ FC0-U61 study guide
Full concept coverage aligned to exam objectives
- →
FC0-U61 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related FC0-U61 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
IT Concepts and Terminology practice questions
Practise FC0-U61 questions linked to IT Concepts and Terminology.
Infrastructure practice questions
Practise FC0-U61 questions linked to Infrastructure.
Applications and Software practice questions
Practise FC0-U61 questions linked to Applications and Software.
Software Development practice questions
Practise FC0-U61 questions linked to Software Development.
Database Fundamentals practice questions
Practise FC0-U61 questions linked to Database Fundamentals.
Security practice questions
Practise FC0-U61 questions linked to Security.
Software Development Concepts practice questions
Practise FC0-U61 questions linked to Software Development Concepts.
FC0-U61 fundamentals practice questions
Practise FC0-U61 questions linked to FC0-U61 fundamentals.
FC0-U61 scenario practice questions
Practise FC0-U61 questions linked to FC0-U61 scenario.
FC0-U61 troubleshooting practice questions
Practise FC0-U61 questions linked to FC0-U61 troubleshooting.
Practice this exam
Start a free FC0-U61 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 FC0-U61 question test?
Software Development — This question tests Software Development — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Is stateless between requests — REST APIs are stateless by design, meaning each request from a client to the server must contain all the information needed to understand and process the request. The server does not store any client context between requests, which improves scalability and reliability. This statelessness is a core constraint of the REST architectural style, as defined by Roy Fielding in his doctoral dissertation.
What should I do if I get this FC0-U61 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
Last reviewed: Jul 4, 2026
This FC0-U61 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-U61 exam.
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.
Sign in to join the discussion.