QUESTIONS FOR WEB |COMPLETE STUDY GUIDE WITH
100% ACCURATE QUESTIONS & ANSWERS | ACE EVERY
TEST | GUARANTEED EXCELLENCE.
1. What kind of protocol is TCP? Answer: Correct idea:
TCP is connection-oriented
Why?
Because before TCP sends real data, it first creates a logical connection between sender and
receiver.
That does not mean a physical wire is reserved.
It means both sides agree:
"I am ready"
"I know your sequence numbers"
"I can track what data arrived"
"I can acknowledge what I received"
So TCP behaves like a careful conversation.
Client-server model Answer: Step 1: the client asks for something
The client is usually the browser, app, or device making the request.
Step 2: the server receives the request
The server stores or manages the resource.
Step 3: the server sends back a representation
The server responds with the resource in some format.
The slides also note that clients may use caches to reuse previously retrieved representations
when allowed.
Proxy: Answer: The slides define a proxy as an intermediary server between a client and a
destination server. It routes requests and may process or cache responses.
Step by step
Normal case without proxy
APPHIA – Crafted with Care and Precision for Academic Excellence.
1
,Client → Server
With proxy
Client → Proxy → Server
The proxy acts like a middle helper.
Why use a proxy?
According to the slides:
privacy
security
performance
grouping organisation HTTP requests through one intermediary
Gateway/reverse: Answer: The slides say a gateway (also called a reverse proxy) acts as the
server for the outbound connection, then forwards the request to another server or servers.
Step by step
What the client sees
The client thinks it is talking to one server.
What really happens
That "server" is actually a gateway in front of other backend servers.
Then
The gateway passes the request inward to the real server.
So:
Client → Gateway → Backend server
REST: Answer: The REST slides say REST means Representational State Transfer, and
describe it as a resource-centric architectural style developed by Fielding.
This sounds scary, but it is actually not too bad.
Simple meaning
REST is a way of designing web systems where:
everything is treated as a resource
each resource has an identifier, usually a URL
APPHIA – Crafted with Care and Precision for Academic Excellence.
2
,clients use HTTP methods like GET, POST, PUT, DELETE
the server sends back representations of resources
Proxy: Answer: A proxy sits in front of the client. The client sends the request to the proxy,
and the proxy sends it on to the real server. The slides define it as an intermediary server
between a client and a destination server, and say it can route, process, or cache responses.
Gateway: Answer: A gateway sits in front of the server.The client thinks it is talking directly
to the server, but really it is talking to the gateway, which forwards the request to one or more
backend servers. The slides describe a gateway as an intermediary that acts as the server for the
outbound connection and forwards requests inward to another server or servers.
REST Answer: REST is a resource-oriented architectural style where resources are identified
by URLs and manipulated using HTTP methods such as GET, POST, PUT, and DELETE.
Communication occurs through representations of resources, and messages are self-
descriptive. REST systems are stateless, meaning each request contains all necessary
information, and may include hypermedia links (HATEOAS) to guide client interactions.
Identifier: Answer: What is an identifier?
An identifier is how we point to a resource.
In REST, this is mainly done with a URL. The slides explicitly say resource identification is
mainly by URL.
representation: Answer: What is a representation?
A representation is the form in which the resource is sent over HTTP.
The slides say a resource representation is information:
intended to reflect the state of the resource
in a format that can be communicated via HTTP
And the REST slides say REST components communicate by transferring a representation of a
resource.
server- driven negotiation: Answer: ents can express their preferences using specific http
header fields. • Accept • Accept-Charset • Accept-Encoding • Accept-Language In response,
servers select a representation among those that are available. A client cannot rely on
APPHIA – Crafted with Care and Precision for Academic Excellence.
3
, negotiation preferences being consistently honored, since the server might: • not support
negotiation for the requested resource or • decide that sending a response that doesn't conform
to the client's preferences is better than sending a 406 (Not Acceptable) response.
Disadvantages of Server-Driven negotiation: Answer: It is impossible for the server to
accurately determine what might be "best" for any given user, since that would require
complete knowledge of both the capabilities of the user agent and the intended use for the
response (e.g., does the user want to view it on screen or print it on paper?); • Having the user
agent describe its capabilities in every request can be both very inefficient (given that only a
small percentage of responses have multiple representations) and a potential risk to the user's
privacy; • It complicates the implementation of an origin server and the algorithms for
generating responses to a request; and, • It limits the reusability of responses for shared
caching
Server-driven negotiation: Answer: There is one header per feature used in the negotiation. • If
you want to use screen size, resolution or other dimensions, a new HTTP header must be
created. • Sending of the headers must be done on every request. • This is not too problematic
with few headers, but with the eventual multiplications of them, the message size would lead
to a decrease in performance. • The more precise headers are sent, the more entropy is sent,
allowing for more HTTP fingerprinting and corresponding privacy concern.
🟢 1. What is Agent-Driven Negotiation? Answer: 👉 Definition:
Agent-driven negotiation (also called reactive negotiation) is when:
👉 the SERVER does NOT choose the representation 👉 the CLIENT chooses it instead
From your slides:
server sends back a page with alternative resources
client selects which one to use
caches: Answer: ✅ Question 2
"Caches can be deployed with any component of the web architecture..."
🧠 Step-by-step thinking
APPHIA – Crafted with Care and Precision for Academic Excellence.
4
100% ACCURATE QUESTIONS & ANSWERS | ACE EVERY
TEST | GUARANTEED EXCELLENCE.
1. What kind of protocol is TCP? Answer: Correct idea:
TCP is connection-oriented
Why?
Because before TCP sends real data, it first creates a logical connection between sender and
receiver.
That does not mean a physical wire is reserved.
It means both sides agree:
"I am ready"
"I know your sequence numbers"
"I can track what data arrived"
"I can acknowledge what I received"
So TCP behaves like a careful conversation.
Client-server model Answer: Step 1: the client asks for something
The client is usually the browser, app, or device making the request.
Step 2: the server receives the request
The server stores or manages the resource.
Step 3: the server sends back a representation
The server responds with the resource in some format.
The slides also note that clients may use caches to reuse previously retrieved representations
when allowed.
Proxy: Answer: The slides define a proxy as an intermediary server between a client and a
destination server. It routes requests and may process or cache responses.
Step by step
Normal case without proxy
APPHIA – Crafted with Care and Precision for Academic Excellence.
1
,Client → Server
With proxy
Client → Proxy → Server
The proxy acts like a middle helper.
Why use a proxy?
According to the slides:
privacy
security
performance
grouping organisation HTTP requests through one intermediary
Gateway/reverse: Answer: The slides say a gateway (also called a reverse proxy) acts as the
server for the outbound connection, then forwards the request to another server or servers.
Step by step
What the client sees
The client thinks it is talking to one server.
What really happens
That "server" is actually a gateway in front of other backend servers.
Then
The gateway passes the request inward to the real server.
So:
Client → Gateway → Backend server
REST: Answer: The REST slides say REST means Representational State Transfer, and
describe it as a resource-centric architectural style developed by Fielding.
This sounds scary, but it is actually not too bad.
Simple meaning
REST is a way of designing web systems where:
everything is treated as a resource
each resource has an identifier, usually a URL
APPHIA – Crafted with Care and Precision for Academic Excellence.
2
,clients use HTTP methods like GET, POST, PUT, DELETE
the server sends back representations of resources
Proxy: Answer: A proxy sits in front of the client. The client sends the request to the proxy,
and the proxy sends it on to the real server. The slides define it as an intermediary server
between a client and a destination server, and say it can route, process, or cache responses.
Gateway: Answer: A gateway sits in front of the server.The client thinks it is talking directly
to the server, but really it is talking to the gateway, which forwards the request to one or more
backend servers. The slides describe a gateway as an intermediary that acts as the server for the
outbound connection and forwards requests inward to another server or servers.
REST Answer: REST is a resource-oriented architectural style where resources are identified
by URLs and manipulated using HTTP methods such as GET, POST, PUT, and DELETE.
Communication occurs through representations of resources, and messages are self-
descriptive. REST systems are stateless, meaning each request contains all necessary
information, and may include hypermedia links (HATEOAS) to guide client interactions.
Identifier: Answer: What is an identifier?
An identifier is how we point to a resource.
In REST, this is mainly done with a URL. The slides explicitly say resource identification is
mainly by URL.
representation: Answer: What is a representation?
A representation is the form in which the resource is sent over HTTP.
The slides say a resource representation is information:
intended to reflect the state of the resource
in a format that can be communicated via HTTP
And the REST slides say REST components communicate by transferring a representation of a
resource.
server- driven negotiation: Answer: ents can express their preferences using specific http
header fields. • Accept • Accept-Charset • Accept-Encoding • Accept-Language In response,
servers select a representation among those that are available. A client cannot rely on
APPHIA – Crafted with Care and Precision for Academic Excellence.
3
, negotiation preferences being consistently honored, since the server might: • not support
negotiation for the requested resource or • decide that sending a response that doesn't conform
to the client's preferences is better than sending a 406 (Not Acceptable) response.
Disadvantages of Server-Driven negotiation: Answer: It is impossible for the server to
accurately determine what might be "best" for any given user, since that would require
complete knowledge of both the capabilities of the user agent and the intended use for the
response (e.g., does the user want to view it on screen or print it on paper?); • Having the user
agent describe its capabilities in every request can be both very inefficient (given that only a
small percentage of responses have multiple representations) and a potential risk to the user's
privacy; • It complicates the implementation of an origin server and the algorithms for
generating responses to a request; and, • It limits the reusability of responses for shared
caching
Server-driven negotiation: Answer: There is one header per feature used in the negotiation. • If
you want to use screen size, resolution or other dimensions, a new HTTP header must be
created. • Sending of the headers must be done on every request. • This is not too problematic
with few headers, but with the eventual multiplications of them, the message size would lead
to a decrease in performance. • The more precise headers are sent, the more entropy is sent,
allowing for more HTTP fingerprinting and corresponding privacy concern.
🟢 1. What is Agent-Driven Negotiation? Answer: 👉 Definition:
Agent-driven negotiation (also called reactive negotiation) is when:
👉 the SERVER does NOT choose the representation 👉 the CLIENT chooses it instead
From your slides:
server sends back a page with alternative resources
client selects which one to use
caches: Answer: ✅ Question 2
"Caches can be deployed with any component of the web architecture..."
🧠 Step-by-step thinking
APPHIA – Crafted with Care and Precision for Academic Excellence.
4
