Discuss Juniper JN0-224 Exam Topic 3 Question 2

Why is a REST API considered stateless?

AThe client requests to the server do not include state information.

BThe REST API is an international API.

CNo client context is stored on the server between requests.

DThe state of the server is not important when making requests.

Suggested Answer: A

Get Premium JN0-224 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

29 comments · newest first

Peggie 5 months ago

I feel C captures the essence of statelessness perfectly.

Fatima 5 months ago

A is too simplistic. C covers the concept better.

Carmen 6 months ago

D sounds off. Server state is important for other things.

Mitsue 6 months ago

C is definitely the best choice. Stateless means no server memory.

Teri 6 months ago

I agree, but C makes sense too. No context stored.

Lai 6 months ago

I think it's A. Clients don't send state info.

Deandrea 6 months ago

B is definitely not true, REST APIs can be used internationally.

Bettina 6 months ago

It's all about the client requests not including state info.

Stefany 7 months ago

Wait, are you sure about that? I thought some state could be maintained.

Naomi 7 months ago

Totally agree, that's a key feature of REST!

Maryln 7 months ago

B) The REST API is an international API. Haha, nice try, but that's not how it works.

Major 8 months ago

D) The state of the server is not important when making requests. Wait, what?

Jade 8 months ago

This question is a piece of cake! C is the correct answer, obviously.

Francesco 8 months ago

A) The client requests to the server do not include state information.

Arlette 8 months ago

C) No client context is stored on the server between requests.

Jacqueline 8 months ago

I remember discussing that statelessness means the server doesn't store anything about the client. So, I'm pretty confident that option C is the correct answer.

Dorethea 9 months ago

I practiced a question similar to this, and I think it was about how each request is independent. That makes me lean towards option C too.

Mickie 9 months ago

I'm a bit unsure about this one. I feel like I studied something about how the client doesn't send state info, but I can't recall if that's the main reason.

Lonna 9 months ago

I think I remember that a REST API is stateless because the server doesn't keep any client context between requests. So, option C seems right.

Fletcher 9 months ago

The international API part in option B is throwing me off a bit. I don't think that's relevant to the stateless nature of REST APIs. I'm leaning towards option C.

Brittni 9 months ago

I'm pretty sure it's about the lack of client context on the server side. The server doesn't keep track of any previous requests or information about the client. That's why it's stateless.

Barrett 9 months ago

Okay, let me think this through. The client requests don't include any state information, so that's why it's considered stateless. I'm going with option A.

Charolette 10 months ago

Hmm, I'm a bit confused. Is it really about the server state not being important? That doesn't seem quite right to me.

Daron 10 months ago

A REST API is stateless because no client context is stored on the server.

Catalina 10 months ago

I think the key here is that the REST API doesn't store any client context between requests. So option C seems like the right answer.

Salome 3 months ago

↳ replying to Catalina

A is true, but C is the main reason for statelessness.

Raelene 3 months ago

↳ replying to Catalina

But what about option A? Isn’t that relevant too?

Iesha 4 months ago

↳ replying to Catalina

Yeah, it’s all about not keeping client info.

Stacey 5 months ago

↳ replying to Catalina

I agree, option C makes the most sense.

Juniper JN0-224 Exam - Topic 3 Question 2 Discussion