Which of the following statements is/are true with respect to the interaction of a web browser with a web server using HTTP 1.1?

Question

A database has 25,000 fixed-length records of 100 bytes (primary key 15 bytes). The data file is block-aligned so each record is fully contained within a block. The file is indexed by a primary index file, also block-aligned and ordered. Block size is 1024 bytes and a block pointer is 5 bytes. Each index entry stores the block’s anchor key (15 bytes) and a pointer (5 bytes). Binary search on an index file of \(b\) blocks needs \(\lceil \log_2 b \rceil\) block accesses in the worst case. Given a key, the number of block accesses required to identify the data file block that may contain the record, in the worst case, is ____________.

Answer 1

A clean way to answer this is to separate two ideas that HTTP 1.1 bundles together: connection persistence (keep-alive) and pipelining, and then test each statement against exactly one server-client TCP link.

What one TCP connection can span: A TCP connection always connects exactly one client endpoint to exactly one server endpoint. It cannot jump between two different servers no matter what version of HTTP is used on top of it.
Statement A (same server, multiple objects): Since HTTP 1.1 keeps a connection open instead of closing it after each response, and all the objects here sit on one server, the browser reuses that single open connection to pull every object in turn. True.
Statement B (different servers): This asks for one TCP connection to reach two different servers, which contradicts the very definition of a TCP connection as a fixed pair of endpoints. Each server needs its own connection. False.
Statement C (pipelining): HTTP 1.1 explicitly supports pipelining requests, meaning the client is allowed to fire off the next request as soon as it has sent the previous one, rather than sitting idle until the previous object finishes downloading. The server still replies in request order, but the client is not blocked waiting. True.
Statement D (multiple pages, same server): Persistence is not limited to objects belonging to a single page. As long as the destination server stays the same, the browser can keep using the same open connection to fetch an entirely different page requested afterward. True.
Putting it together: The only statement that breaks is the one demanding a single connection reach across two servers. Everything that stays within one server, whether it is objects of one page, back-to-back requests without waiting, or separate pages over time, is enabled by HTTP 1.1's persistent and pipelined connections.

\[ \boxed{A, C, D} \]

Answer 2

A clean way to answer this is to separate two ideas that HTTP 1.1 bundles together: connection persistence (keep-alive) and pipelining, and then test each statement against exactly one server-client TCP link.

What one TCP connection can span: A TCP connection always connects exactly one client endpoint to exactly one server endpoint. It cannot jump between two different servers no matter what version of HTTP is used on top of it.
Statement A (same server, multiple objects): Since HTTP 1.1 keeps a connection open instead of closing it after each response, and all the objects here sit on one server, the browser reuses that single open connection to pull every object in turn. True.
Statement B (different servers): This asks for one TCP connection to reach two different servers, which contradicts the very definition of a TCP connection as a fixed pair of endpoints. Each server needs its own connection. False.
Statement C (pipelining): HTTP 1.1 explicitly supports pipelining requests, meaning the client is allowed to fire off the next request as soon as it has sent the previous one, rather than sitting idle until the previous object finishes downloading. The server still replies in request order, but the client is not blocked waiting. True.
Statement D (multiple pages, same server): Persistence is not limited to objects belonging to a single page. As long as the destination server stays the same, the browser can keep using the same open connection to fetch an entirely different page requested afterward. True.
Putting it together: The only statement that breaks is the one demanding a single connection reach across two servers. Everything that stays within one server, whether it is objects of one page, back-to-back requests without waiting, or separate pages over time, is enabled by HTTP 1.1's persistent and pipelined connections.

\[ \boxed{A, C, D} \]

Which of the following statements is/are true with respect to the interaction of a web browser with a web server using HTTP 1.1?

Show Hint

The Correct Option is A, C, D

Solution and Explanation

Questions Asked in GATE CS exam