PyQdeck LogoPyQdeckSubjectsSyllabusBlog

Web Technology

106609
Back to Web Technology

Module II: Browser and Apache Web Server Architecture

  1. Q1(c). A browser receives an HTML document containing references to images, CSS files and scripts. Which browser subsystem is primarily responsible for interpreting the document and producing the visual representation? (i) Rendering engine (ii) Database engine (iii) Mail server (iv) FTP server20262m

    Module II: Browser and Apache Web Server Architecture

    A browser receives an HTML document containing references to images, CSS files and scripts. Which browser subsystem is primarily responsible for interpreting the document and producing the visual representation?
    (i) Rendering engine
    (ii) Database engine
    (iii) Mail server
    (iv) FTP server

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    Correct answer: (i) Rendering engine. It parses HTML and CSS, computes layout and paints the page's visual representation.

  2. Q1(d). Browser configuration primarily affects (i) Only the physical network topology (ii) The definition of HTML grammar (iii) User and browser behavior such as security, connection and display-related settings (iv) The structure of an XML document20262m

    Module II: Browser and Apache Web Server Architecture

    Browser configuration primarily affects
    (i) Only the physical network topology
    (ii) The definition of HTML grammar
    (iii) User and browser behavior such as security, connection and display-related settings
    (iv) The structure of an XML document

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    Correct answer: (iii) User and browser behavior such as security, connection and display-related settings. Browser configuration includes privacy, proxy, cookies, certificates and display preferences.

  3. Q1(e). Which protocol is specifically associated with transferring files between a client and a server? (i) SMTP (ii) FTP (iii) POP (iv) HTTP only20262m

    Module II: Browser and Apache Web Server Architecture

    Which protocol is specifically associated with transferring files between a client and a server?
    (i) SMTP
    (ii) FTP
    (iii) POP
    (iv) HTTP only

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    Correct answer: (ii) FTP. File Transfer Protocol transfers files between clients and servers. Standard FTP is not encrypted; FTPS and SFTP are secure alternatives, and SFTP uses SSH.

  4. Q4(a). Draw the functional block diagram of a modern web browser and state the primary function of each subsystem.20267m

    Module II: Browser and Apache Web Server Architecture

    Draw the functional block diagram of a modern web browser and state the primary function of each subsystem.

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    Functional Block Diagram of a Modern Web Browser

    A browser retrieves web resources, interprets web technologies and displays interactive pages.

    MermaidDiagram
    Rendering diagram…

    Subsystems

    1. User interface: tabs, address bar, bookmarks and navigation controls.
    2. Browser engine: coordinates UI, rendering and browser services.
    3. Rendering engine: parses HTML/CSS, computes layout and paints the page.
    4. JavaScript engine: executes scripts and interacts with the DOM and browser APIs.
    5. Networking: sends HTTP/HTTPS requests and receives resources.
    6. Graphics/UI backend: draws widgets, text, images and graphical output.
    7. Data storage: maintains cache, cookies, history and local/site storage.

    Working: The browser resolves a URL, requests the document, parses HTML into a DOM and CSS into style rules, computes layout and paints the result. It fetches referenced images, stylesheets and scripts; JavaScript can update the page after loading.

    Modern browsers often isolate tabs or sites into separate processes to improve stability and security.

  5. Q4(b). Compare Netscape Navigator and Internet Explorer in terms of their rendering engines, proprietary feature support, security models and historical impact on cross-browser compatibility and web standards.20267m

    Module II: Browser and Apache Web Server Architecture

    Compare Netscape Navigator and Internet Explorer in terms of their rendering engines, proprietary feature support, security models and historical impact on cross-browser compatibility and web standards.

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    Netscape Navigator vs Internet Explorer

    Basis Netscape Navigator Internet Explorer (IE)
    Rendering engine Early versions used Netscape's own engine; later Mozilla development led to Gecko Major Windows versions used Microsoft's Trident engine
    Proprietary features Included Netscape-specific extensions and early web APIs Supported Microsoft-specific extensions and, in some versions, ActiveX
    Security Security evolved across versions; scripting and plug-ins introduced risks Windows integration and ActiveX expanded capabilities and potential attack surface
    Standards Differences in HTML/CSS/JavaScript behaviour caused compatibility issues Non-standard behaviours and version differences also caused compatibility issues
    Historical impact One of the first widely used graphical browsers Became dominant during the browser wars, partly through Windows integration

    During the browser wars, developers sometimes used browser detection and separate code paths because browsers interpreted HTML, CSS and JavaScript differently. Proprietary APIs and inconsistent standards support meant a page might work in one browser and fail in another.

    Competition helped popularize the Web but also fragmented it. Open standards, browser testing, progressive enhancement and later standardization efforts improved interoperability.

    Conclusion: Both browsers shaped early web development. Their differences demonstrate why standards compliance and cross-browser testing matter. Details varied by version, and both products are now historical.

  6. Q5(a). Describe the architecture and working of a web server with a neat diagram. Discuss the major features of the Apache Web Server.20267m

    Module II: Browser and Apache Web Server Architecture

    Describe the architecture and working of a web server with a neat diagram. Discuss the major features of the Apache Web Server.

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    Web Server Architecture and Apache Features

    A web server receives HTTP/HTTPS requests from clients, locates or generates the requested resource, and returns an HTTP response. It can serve static files directly or pass dynamic requests to application runtimes.

    MermaidDiagram
    Rendering diagram…

    Working: The browser resolves the domain through DNS and opens a connection. For HTTPS, TLS protects the connection. The server parses the request, applies routing and access rules, reads a static resource or invokes application code, then sends a response containing a status code, headers and body.

    Major features of Apache HTTP Server

    1. Open source: widely used and extensible.
    2. Cross-platform: runs on Unix-like systems and Windows.
    3. Virtual hosting: hosts multiple sites on one server.
    4. Modules: functionality can be extended, for example with rewrite, TLS and proxy modules.
    5. Security controls: access control, authentication and TLS support when configured.
    6. URL rewriting and redirects: supports flexible routing and canonical URLs.
    7. Logging and configuration: configurable access/error logs and per-directory settings, including .htaccess where enabled.
    8. Proxying and load balancing: modules can route requests to backend applications.

    Conclusion: A web server is the HTTP entry point for a website. Apache is popular because it is flexible, modular and configurable; secure operation requires updates and careful configuration.

  7. Q5(b). Differentiate between HTTP and FTP based on their purpose, working principles and applications.20267m

    Module II: Browser and Apache Web Server Architecture

    Differentiate between HTTP and FTP based on their purpose, working principles and applications.

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    HTTP vs FTP

    Basis HTTP FTP
    Full form Hypertext Transfer Protocol File Transfer Protocol
    Main purpose Transfer web resources and API data Transfer and manage files
    Typical use Web pages, images, APIs, downloads Uploading/downloading files to a server
    Connections Usually one connection for requests/responses; HTTP/2 and HTTP/3 improve multiplexing Traditionally separate control and data connections
    Operations GET, POST, PUT, DELETE and others Commands such as LIST, RETR and STOR
    Security HTTPS adds TLS encryption and authentication Plain FTP is unencrypted; FTPS adds TLS; SFTP uses SSH and is a different protocol
    Default ports HTTP 80; HTTPS 443 FTP control commonly 21; data behaviour varies by mode

    HTTP working: A client sends a request with a method, path, headers and sometimes a body. The server responds with a status code, headers and content. HTTP is stateless at the protocol level, though cookies and application sessions can preserve state.

    FTP working: A client authenticates to an FTP server and issues commands over a control connection. File data is transferred over a separate data connection, in active or passive mode.

    Applications: HTTP/HTTPS powers websites, web services and APIs. FTP has traditionally been used for file exchange and website publishing, though secure alternatives are preferred today.

    Conclusion: HTTP is optimized for web resource communication, whereas FTP is designed for file transfer and file-management operations.

  8. Q9(b). Write a short note on Configuration of Netscape Navigator. Question 9: attempt any two short notes.20267m

    Module II: Browser and Apache Web Server Architecture

    Write a short note on Configuration of Netscape Navigator. Question 9: attempt any two short notes.

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    Short Note: Configuration of Netscape Navigator

    Netscape Navigator was a historical web browser. Its configuration options let users customize how it connected to websites and handled content.

    Important settings included:

    1. Home page: choose the page opened at startup.
    2. Connection/proxy: configure direct access or proxy settings for an organization's network.
    3. Cache: manage temporary files used to speed up repeat visits.
    4. Cookies and privacy: control site data and privacy-related behaviour, depending on version.
    5. Security: manage certificates and permissions for scripts or other active content where supported.
    6. Appearance: configure fonts, colours and language preferences.
    7. Mail/news integration: configure associated mail or news services in versions that included them.

    Exact menus and features differed by release and operating system. Administrators needed to balance convenience with security and compatibility.

    Conclusion: Browser configuration affects navigation, connectivity, privacy, security and presentation. Netscape is now a historical browser, so its options should be understood in their version-specific context.

  9. Q9(c). Write a short note on Simple Mail Transfer Protocol (SMTP). Question 9: attempt any two short notes.20267m

    Module II: Browser and Apache Web Server Architecture

    Write a short note on Simple Mail Transfer Protocol (SMTP). Question 9: attempt any two short notes.

    View this question on its own page →
    Search GoogleAsk AI
    Worked Solution

    Short Note: Simple Mail Transfer Protocol (SMTP)

    SMTP stands for Simple Mail Transfer Protocol. It is an application-layer protocol used to send email from a mail client to an outgoing mail server and to relay messages between mail servers.

    Working

    1. The sender composes a message in a mail application.
    2. The client submits it to an outgoing mail server, commonly using authenticated submission on port 587 with STARTTLS or implicit TLS on port 465.
    3. The sending server looks up the recipient domain's MX record in DNS.
    4. It relays the message to the recipient's mail server, commonly using port 25 between servers.
    5. The recipient retrieves the message using IMAP or POP; SMTP is primarily for sending and relaying, not mailbox retrieval.

    Basic commands include EHLO/HELO, MAIL FROM, RCPT TO, DATA and QUIT.

    Advantages: standardized mail transfer, store-and-forward delivery, and support for relaying between different providers.

    Limitations: SMTP alone does not guarantee confidentiality or prevent spoofing. TLS, authentication, SPF, DKIM and DMARC help secure transport and improve domain-level anti-spoofing.

    Conclusion: SMTP is the standard protocol for sending and relaying email, while IMAP and POP are commonly used to access received messages.

Previous moduleModule I: Introduction to Web Technologies and ArchitecturesNext moduleModule III: Basics of Web Programming