2025 question paper

Web Technology

26 questions

Q1a. Which markup language is the foundation for defining other markup languages like HTML and XML (i) SGML (ii) CSS (iii) XSL (iv) None of this20252m
Module I: Introduction to Web Technologies & Architectures
Which markup language is the foundation for defining other markup languages like HTML and XML

(i) SGML
(ii) CSS
(iii) XSL
(iv) None of this

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (i) SGML

Explanation:

SGML (Standard Generalized Markup Language) is a standard generalized metalanguage (ISO 8879:1986) used to define descriptive markup languages.

Both HTML and XML were developed based on SGML. XML is a simplified subset of SGML designed specifically for the World Wide Web.

CSS is a style sheet language, and XSL is an XML-based stylesheet and transformation language.

Key Points:

Foundation: SGML defines the rules and syntax for document markup.

Derivatives: HTML (application of SGML) and XML (restricted subset of SGML).
Q1b. Which of the following is used to define the structure of an XML document? (i) XSL (ii) DTD (iii) CSS (iv) HTML20252m
Module I: Introduction to Web Technologies & Architectures
Which of the following is used to define the structure of an XML document?

(i) XSL
(ii) DTD
(iii) CSS
(iv) HTML

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (ii) DTD

Explanation:

DTD (Document Type Definition) defines the legal structure, elements, attributes, and data types of an XML document.

It validates the syntax and layout of an XML document to ensure it conforms to the intended schema.

XSL (Extensible Stylesheet Language) is used for transforming and formatting XML documents.

CSS (Cascading Style Sheets) is used for presentation and styling.

HTML is a markup language for web page structure, not XML schema definition.

Example of DTD Declaration:

<!DOCTYPE note [ <!ELEMENT note (to,from,heading,body)> <!ELEMENT to (#PCDATA)> <!ELEMENT from (#PCDATA)> <!ELEMENT heading (#PCDATA)> <!ELEMENT body (#PCDATA)> ]>
Q1c. The component of a web browser responsible for displaying content on the screen is (i) Rendering engine (ii) Networking engine (iii) JavaScript engine (iv) UI backend20252m
Module II: Browser & Apache Web Server Architecture; Common Protocols
The component of a web browser responsible for displaying content on the screen is

(i) Rendering engine
(ii) Networking engine
(iii) JavaScript engine
(iv) UI backend

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (i) Rendering engine

Explanation:

The Rendering Engine (also known as layout engine) is responsible for parsing HTML documents, styling information from CSS, and painting the rendered layout onto the user's screen.

Popular rendering engines include Blink (Chrome, Edge), Gecko (Firefox), and WebKit (Safari).

Roles of other Browser Components:

Networking Engine: Handles HTTP/HTTPS requests, network communication, and security certificates.

JavaScript Engine: Parses, compiles, and executes JavaScript code (e.g., V8, SpiderMonkey).

UI Backend: Provides generic drawing widgets like combo boxes and windows.
Q1d. The configuration files of most web browsers are stored in (i) Temporary Internet files (ii) Cache directory (iii) User profile directory (iv) Application directory20252m
Module II: Browser & Apache Web Server Architecture; Common Protocols
The configuration files of most web browsers are stored in

(i) Temporary Internet files
(ii) Cache directory
(iii) User profile directory
(iv) Application directory

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (iii) User profile directory

Explanation:

Modern web browsers store user-specific configuration files, custom preferences, bookmarks, extensions, and session data in the User Profile Directory (e.g., in AppData/Roaming or ~/.config/).

This allows multiple users on the same operating system to maintain independent browser configurations.

Comparison:

Temporary Internet files / Cache directory: Store cached web assets (images, stylesheets, scripts) to speed up subsequent visits, not settings.

Application directory: Contains the executable binaries and system libraries of the browser.
Q1e. Which of the following is an open-source web server software? (i) IIS (ii) Apache (iii) Nginx (iv) Tomcat20252m
Module II: Browser & Apache Web Server Architecture; Common Protocols
Which of the following is an open-source web server software?

(i) IIS
(ii) Apache
(iii) Nginx
(iv) Tomcat

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (ii) Apache (Note: Nginx and Tomcat are also open-source; IIS is proprietary)

Explanation:

Apache HTTP Server is the most widely recognized open-source HTTP web server software developed and maintained by the Apache Software Foundation (ASF) under the Apache 2.0 License.

IIS (Internet Information Services) is a proprietary web server created by Microsoft.

Nginx and Apache Tomcat are also open-source server technologies, but in academic curricula Apache is standardly recognized as the primary open-source web server.

Key Features of Apache HTTP Server:

Modular architecture (DSO - Dynamic Shared Objects).

Highly customizable via .htaccess and httpd.conf.

Broad support for CGI, PHP, Perl, and SSL/TLS.
Q1f. Apache Tomcat is mainly used for (i) Serving static HTML pages (ii) Running Java-based web applications (iii) Hosting FTP servers (iv) Sending emails20252m
Module II: Browser & Apache Web Server Architecture; Common Protocols
Apache Tomcat is mainly used for

(i) Serving static HTML pages
(ii) Running Java-based web applications
(iii) Hosting FTP servers
(iv) Sending emails

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (ii) Running Java-based web applications

Explanation:

Apache Tomcat is an open-source servlet container and application server designed to execute Java Servlets and render JavaServer Pages (JSP).

It implements the official Java Servlet, JSP, Java EL, and WebSocket specifications from the Jakarta EE project.

Comparison:

Serving static HTML pages: Primarily handled by general web servers like Apache HTTP Server or Nginx.

Hosting FTP servers: Handled by FTP daemons (e.g., vsftpd, FileZilla Server).

Sending emails: Handled by SMTP Mail Transfer Agents (e.g., Postfix, Sendmail).
Q1g. Which technology is used for server-side scripting? (i) HTML (ii) CSS (iii) JSP (iv) JavaScript20252m
Module III: Basics of Web Programming
Which technology is used for server-side scripting?

(i) HTML
(ii) CSS
(iii) JSP
(iv) JavaScript

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (iii) JSP

Explanation:

JSP (JavaServer Pages) is a server-side technology that allows developers to insert Java code into HTML templates to generate dynamic web content on the server before sending it to the client.

HTML and CSS are purely client-side markup and styling languages rendered directly by the browser.

JavaScript historically runs as a client-side scripting language in the browser (unless explicitly executed on a runtime like Node.js).

How JSP Works on Server:

Client requests a .jsp file.

The web server translates JSP into a Java Servlet (.java).

The servlet is compiled into bytecode (.class) and executed.

The generated HTML response is sent back to the client.
Q1h. Which of the following is a client-side scripting language? (i) PHP (ii) JavaScript (iii) JSP (iv) Servlet20252m
Module III: Basics of Web Programming
Which of the following is a client-side scripting language?

(i) PHP
(ii) JavaScript
(iii) JSP
(iv) Servlet

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (ii) JavaScript

Explanation:

JavaScript is the standard client-side scripting language executed directly by the web browser's JavaScript engine (e.g., V8, SpiderMonkey).

It enables interactive web pages, dynamic styling, DOM manipulation, form validation, and asynchronous requests (AJAX).

PHP, JSP, and Servlets are all server-side technologies executed on the web/application server.
Q1i. Which protocol is commonly used for secure online transactions? (i) HTTPS (ii) FTP (iii) SMTP (iv) HTTP20252m
Module IV: E-commerce Applications
Which protocol is commonly used for secure online transactions?

(i) HTTPS
(ii) FTP
(iii) SMTP
(iv) HTTP

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (i) HTTPS

Explanation:

HTTPS (HyperText Transfer Protocol Secure) is the secure version of HTTP that encrypts communications using TLS (Transport Layer Security) or SSL (Secure Sockets Layer).

It ensures data confidentiality, data integrity, and authentication for sensitive operations like online banking, credit card transactions, and e-commerce checkouts.

Security Guarantees:

Encryption: Protects transmitted data against eavesdropping (packet sniffing).

Data Integrity: Prevents tampering or alteration of packets during transit.

Authentication: Proves to users that they are connected to the genuine website via digital certificates.
Q1j. The Semantic Web is primarily concerned with (i) Multimedia sharing (ii) Data interlinking and machine understanding (iii) Social networking (iv) Cloud Storage20252m
Module V: Web 3.0 — Semantic Web and Supporting Technologies
The Semantic Web is primarily concerned with

(i) Multimedia sharing
(ii) Data interlinking and machine understanding
(iii) Social networking
(iv) Cloud Storage

View this question on its own page →
Search Google Ask AI
Worked Solution
Correct Answer: (ii) Data interlinking and machine understanding

Explanation:

The Semantic Web (an extension of the World Wide Web championed by Tim Berners-Lee and the W3C) aims to make web data understandable and processable by machines and software agents, rather than only displayable to humans.

It relies on standard frameworks such as RDF (Resource Description Framework), RDFS, OWL (Web Ontology Language), and SPARQL.

Core Objectives:

Meaningful Relationships: Assigning standardized semantics and metadata to data.

Linked Data: Connecting disparate databases and web entities across the internet.

Automated Reasoning: Enabling AI agents to perform intelligent queries, cross-domain data integration, and inference.

Q2a. Compare Client/Server computing with N-tiered architecture using suitable diagrams.20257m

Module I: Introduction to Web Technologies & Architectures

Compare Client/Server computing with N-tiered architecture using suitable diagrams.

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Client/Server Computing vs N-Tiered Architecture

1. Client/Server Computing

Client/Server (C/S) computing is a distributed architecture in which the application is divided mainly into a client and a server. The client requests a service and the server processes the request and returns the result.

+---------+       Request       +---------+
| Client  | ------------------> | Server  |
| (UI)    | <------------------ |         |
+---------+       Response      +---------+

Client

Provides the user interface.
Accepts input from the user.
Sends requests to the server.
Displays the result returned by the server.

Server

Receives client requests.
Processes application/business operations.
Accesses databases or other resources.
Sends the result back to the client.

2. N-Tiered Architecture

N-tier architecture divides an application into multiple logical tiers, with each tier having a specific responsibility. A common example is three-tier architecture.

+-----------------------+
|   Presentation Tier   |
| HTML / CSS / Browser  |
+-----------+-----------+
            |
            v
+-----------------------+
|   Business Tier       |
| Application Logic     |
+-----------+-----------+
            |
            v
+-----------------------+
|      Data Tier        |
| Database / Data Access|
+-----------------------+

Presentation Tier

Handles interaction with the user. Examples include HTML, CSS, JavaScript and the web browser.

Business Logic Tier

Contains application rules and processing such as validation, authentication and calculations.

Data Tier

Handles storing, retrieving and managing data using databases and data-access components.

3. Comparison

Client/Server	N-Tier Architecture
Usually has two major parts: client and server.	Divides the application into multiple logical tiers.
Business logic may be placed in the client or server.	Business logic normally has a dedicated tier.
Simpler architecture.	More structured architecture.
Less suitable for very large applications.	Better suited for large and complex web applications.
Maintenance can become difficult when responsibilities are mixed.	Easier maintenance because responsibilities are separated.
Scaling can be more difficult.	Individual tiers can be scaled independently.

4. Advantages of N-Tier Architecture

Separation of concerns: Each tier performs a specific responsibility.
Maintainability: Changes in one tier have less impact on other tiers.
Scalability: Individual tiers can be scaled according to demand.
Security: Sensitive data and database access can be isolated in lower tiers.
Reusability: Business and data-access components can be reused by different clients.

Conclusion

Client/Server computing provides a simple distributed model in which clients communicate directly with servers. N-tier architecture extends this idea by separating presentation, business logic and data management into independent tiers. Therefore, N-tier architecture provides better scalability, maintainability, security and flexibility for modern web applications.

Q2b. What is SGML? Explain how HTML, XML, and XSL are related to SGML and used in web development.20257m

Module I: Introduction to Web Technologies & Architectures

What is SGML? Explain how HTML, XML, and XSL are related to SGML and used in web development.

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: SGML and Its Relationship with HTML, XML, and XSL

1. What is SGML?

SGML (Standard Generalized Markup Language) is an international standard (ISO 8879:1986) metalanguage used to define descriptive markup languages for electronic documents.

SGML separates document structure, content, and presentation.
It provides rules for creating custom tags, attributes, and structural rules through a Document Type Definition (DTD).
Although powerful and highly flexible, SGML is complex and heavy, making direct interpretation in lightweight web browsers difficult.

                           +------------------------+
                           |         SGML           |
                           | (ISO 8879 Metalanguage)|
                           +-----------+------------+
                                       |
                     +-----------------+-----------------+
                     |                                   |
         (Application of SGML)                 (Subset of SGML)
                     v                                   v
             +---------------+                   +---------------+
             |     HTML      |                   |      XML      |
             | (Fixed Tags)  |                   | (Custom Tags) |
             +---------------+                   +-------+-------+
                                                         |
                                                 (Stylesheet for XML)
                                                         v
                                                 +---------------+
                                                 |      XSL      |
                                                 |  (XSLT/XSL-FO)|
                                                 +---------------+

2. Relationship with HTML, XML, and XSL

A. HTML (HyperText Markup Language)

Relationship: HTML is an application of SGML. It is defined by a predefined SGML DTD.
Characteristics:
- Has a fixed, predefined set of tags (<h1>, <p>, <a>, <table>).
- Primarily designed for displaying data and formatting user interfaces in web browsers.
- More lenient syntax (e.g., closing tags were optional in earlier HTML versions).
Role in Web Development: Acts as the standard structural language for all web pages delivered across the internet.

B. XML (eXtensible Markup Language)

Relationship: XML is a simplified, strict subset of SGML designed by the W3C specifically for the World Wide Web.
Characteristics:
- Has no predefined tags; developers create domain-specific tags describing data semantics.
- Strict syntax rules: all tags must close, case-sensitive, proper nesting, and root element required.
- Focuses on storing and transporting data, completely independent of presentation.
Role in Web Development: Used for data exchange between heterogeneous platforms, web services (REST/SOAP), configuration files, and feeds (RSS).

C. XSL (eXtensible Stylesheet Language)

Relationship: XSL is a family of recommendations written in XML to transform and style XML documents.
Major Components:
1. XSLT (XSL Transformations): Transforms XML documents into HTML, plain text, or another XML structure.
2. XPath (XML Path Language): Navigates elements and attributes in XML documents.
3. XSL-FO (XSL Formatting Objects): Formats XML data for output media such as PDF or print.
Role in Web Development: Converts raw server-side XML data into styled HTML pages for display in browsers or transforms data between distinct API schemas.

3. Comparison Table

Feature	SGML	HTML	XML	XSL
Type	Metalanguage	Markup Language	Simplified Metalanguage / Data format	Stylesheet & Transformation language
Origin	ISO 8879 (1986)	SGML Application	SGML Subset (W3C 1998)	XML Application (W3C)
Tags	User-defined via DTD	Fixed & Predefined	User-defined	Predefined XSL elements
Primary Goal	Document definition standard	Web page presentation	Data storage & transport	XML transformation & styling
Syntax Strictness	Highly complex	Relaxed / Lenient	Very strict (Well-formed)	Very strict (Well-formed XML)

Conclusion

SGML provided the foundational theory of structured markup. HTML applied SGML for web presentation, while XML simplified SGML for structured data exchange. XSL complements XML by providing the presentation and transformation rules needed to render XML data in modern web environments.

Q3a. Describe the architecture of a web browser and explain its major components.20257m
Module II: Browser & Apache Web Server Architecture; Common Protocols
Describe the architecture of a web browser and explain its major components.

View this question on its own page →
Search Google Ask AI
Worked Solution
Answer: Web Browser Architecture and Major Components

1. Introduction

A web browser is a software application designed to retrieve, present, and navigate resources on the World Wide Web. Its internal architecture is modular, dividing tasks such as network communication, parsing, script execution, rendering, and persistence across distinct interacting subsystems.

+-------------------------------------------------------------+ | User Interface | +-------------------------------------------------------------+ | +-----------------------------v-------------------------------+ | Browser Engine | +-----------------------------+-------------------------------+ | +-----------------------------v-------------------------------+ | Rendering Engine | | +--------------------+ +-------------------------------+ | | | HTML Parser | | CSS Parser | | | +---------+----------+ +---------------+---------------+ | | | | | | +-------------> Render Tree <-+ | | | | | v | | Layout & Painting | +---------+------------------------+------------------+-------+ | | | +---------v----------+ +----------v---------+ +-----v-------+ | Networking Layer | | JavaScript Engine | | UI Backend | | (HTTP/HTTPS/DNS) | | (V8, SpiderMonkey) | | (Widgets) | +--------------------+ +--------------------+ +-------------+ | +----------------------------------v--------------------------+ | Data Persistence | | (Cookies, LocalStorage, IndexedDB, Cache) | +-------------------------------------------------------------+

2. Major Components of a Browser

1. User Interface (UI)

Includes all visible parts of the browser window except the main webpage viewport.

Elements: Address bar (Omnibox), Back/Forward/Reload buttons, Bookmarks menu, Tabs, and Settings.

2. Browser Engine

Acts as an intermediary bridge between the User Interface and the Rendering Engine.

Manages high-level actions like navigation queries, history management, and loading progress indicators.

3. Rendering Engine

The core component that parses HTML, XML, CSS, and embedded media, constructing the visual layout painted on screen.

Prominent Engines:

Blink: Google Chrome, Microsoft Edge, Opera, Brave

Gecko: Mozilla Firefox

WebKit: Apple Safari

4. Networking Layer

Handles network communications, DNS lookups, TLS/SSL encryption, HTTP/HTTPS request-response cycles, and connection pooling.

Manages network caches, redirects, and proxy configurations.

5. JavaScript Engine (Interpreter)

Parses, compiles (via JIT - Just-In-Time compilation), and executes JavaScript code.

Manages the execution stack, heap memory allocation, and garbage collection.

Examples: V8 (Chrome, Edge, Node.js), SpiderMonkey (Firefox), JavaScriptCore (Safari).

6. UI Backend

Draws standard basic user interface widgets like combo boxes, input fields, checkboxes, and system alert windows.

Interfaces with the underlying Operating System’s graphic subsystem.

7. Data Persistence (Storage Layer)

Stores persistent client-side data locally on the user's hard drive.

Supported Mechanisms:

Cookies: Small state tokens sent with HTTP requests.

Web Storage: localStorage (persistent) and sessionStorage (tab lifecycle).

IndexedDB: NoSQL client-side database for large structured datasets.

HTTP Cache: Stores downloaded static resources (scripts, images, CSS) to minimize latency.

3. Basic Rendering Flow Pipeline

HTML ---> DOM Tree ------+ +---> Render Tree ---> Layout ---> Paint ---> Screen CSS ---> CSSOM Tree ----+

Constructing DOM Tree: HTML tokens are parsed into Document Object Model nodes.

Constructing CSSOM: CSS rules are parsed into the CSS Object Model.

Render Tree Creation: Visible DOM nodes are merged with computed styles from CSSOM.

Layout (Reflow): Browser calculates exact geometric coordinates and sizes for every visible element.

Painting (Rasterization): Pixels are drawn and composited onto the screen display.

Q3b. Explain how a web browser interacts with a web server using the HTTP request-response model.20257m

Module II: Browser & Apache Web Server Architecture; Common Protocols

Explain how a web browser interacts with a web server using the HTTP request-response model.

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Browser-Server Interaction via the HTTP Request-Response Model

1. Overview

The HTTP (HyperText Transfer Protocol) request-response model is a client-server communication protocol where the web browser (client) initiates a request, and the web server processes the request and returns an appropriate response over a reliable TCP/IP connection.

+--------------+                                      +--------------+
| Web Browser  |                                      |  Web Server  |
|   (Client)   |                                      |   (Apache)   |
+-------+------+                                      +-------+------+
        |                                                     |
        |  1. DNS Resolution (Domain -> IP Address)           |
        |---------------------------------------------------->|
        |                                                     |
        |  2. TCP 3-Way Handshake (SYN, SYN-ACK, ACK)         |
        |====================================================>|
        |                                                     |
        |  3. TLS/SSL Handshake (For HTTPS connections)       |
        |====================================================>|
        |                                                     |
        |  4. HTTP Request (GET /index.html HTTP/1.1)         |
        |---------------------------------------------------->|
        |                                                     |
        |                   [Server Processes Request & DB]   |
        |                                                     |
        |  5. HTTP Response (200 OK + HTML Body)              |
        |<----------------------------------------------------|
        |                                                     |
        |  6. Sub-resource Requests (CSS, JS, Images)         |
        |<===================================================>|
        |                                                     |
        v                                                     v

2. Step-by-Step Interaction Lifecycle

Step 1: URL Parsing and DNS Lookup

The user types a URL (e.g., https://www.example.com/index.html).
The browser checks local caches (browser cache, OS cache, router cache).
If not found, it queries DNS servers to resolve the domain name into an IP address (e.g., 93.184.216.34).

Step 2: Establishing TCP Connection

The browser opens a connection to the server on port 80 (HTTP) or port 443 (HTTPS) using the TCP 3-Way Handshake:
1. SYN: Client sends synchronization packet.
2. SYN-ACK: Server acknowledges and responds with SYN.
3. ACK: Client acknowledges back.

Step 3: TLS/SSL Handshake (For HTTPS)

Client and server negotiate cipher suites, authenticate digital certificates, and establish a symmetric session key for encrypted communication.

Step 4: Browser Sends HTTP Request

The browser crafts and sends a formatted HTTP request message.

GET /index.html HTTP/1.1
Host: www.example.com
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64)
Accept: text/html,application/xhtml+xml
Accept-Language: en-US,en;q=0.9
Connection: keep-alive

Step 5: Server Processing and HTTP Response

The web server (e.g., Apache, Nginx) parses the request, executes server-side scripts (PHP/JSP/Servlets), queries databases if necessary, and returns an HTTP response message.

HTTP/1.1 200 OK
Date: Mon, 20 Aug 2026 12:00:00 GMT
Server: Apache/2.4.52
Content-Type: text/html; charset=UTF-8
Content-Length: 1024
Connection: keep-alive

<!DOCTYPE html>
<html>
  <head><title>Example</title></head>
  <body><h1>Welcome to Example!</h1></body>
</html>

Step 6: Rendering and Additional Asset Requests

The browser parses the received HTML. As it encounters linked assets (<link rel="stylesheet">, <script src="...">, <img src="...">), it sends parallel HTTP requests over persistent connections (HTTP Keep-Alive / HTTP/2 multiplexing) until the entire page is rendered.

3. Key Components of HTTP Messages

Component	Request Message	Response Message
Initial Line	Request Line (`METHOD URL VERSION`)	Status Line (`VERSION STATUS_CODE REASON`)
Headers	`Host`, `User-Agent`, `Accept`, `Cookie`	`Content-Type`, `Content-Length`, `Set-Cookie`
Empty Line	`\r
` separator	`\r
` separator
Body (Payload)	Form data, JSON payload (for POST/PUT)	HTML, CSS, JSON data, or binary image

4. Common HTTP Status Codes

200 OK: Request succeeded.
301 Moved Permanently: Resource redirected to a new URL.
400 Bad Request: Server could not parse the client request.
404 Not Found: Requested URL does not exist.
500 Internal Server Error: Server encountered an unexpected failure.

Q4a. What are the features and configuration steps of the Apache Tomcat server?20257m

Module II: Browser & Apache Web Server Architecture; Common Protocols

What are the features and configuration steps of the Apache Tomcat server?

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Features and Configuration Steps of Apache Tomcat Server

1. Overview of Apache Tomcat

Apache Tomcat is an open-source web server and Java Servlet container developed by the Apache Software Foundation (ASF). It provides a pure Java HTTP web server environment in which Java code can run, implementing the Jakarta Servlet, Jakarta Server Pages (JSP), Jakarta Expression Language (EL), and WebSocket technologies.

2. Key Features of Apache Tomcat

Servlet & JSP Container: Implements modern Servlet and JSP specifications through its internal engines:
- Catalina: The core Servlet engine.
- Jasper: The JSP engine that compiles JSPs into Servlets.
- Coyote: The HTTP connector supporting HTTP/1.1, HTTP/2, and AJP protocols.
Lightweight & Fast: Highly optimized for Java enterprise web applications with low resource overhead.
Cross-Platform: Pure Java implementation that runs seamlessly on Windows, Linux, macOS, and Unix.
JNDI Resource Management: Supports enterprise connection pooling (e.g., MySQL, Oracle database DataSources).
Clustering & Session Replication: Supports high availability and load balancing across multiple Tomcat instances.
Embeddable: Can be embedded directly inside Java applications (commonly used in Spring Boot).

3. Directory Structure of Tomcat

Directory	Description
`/bin`	Startup, shutdown, and control scripts (`startup.bat`/`startup.sh`, `catalina.sh`).
`/conf`	Core XML configuration files (`server.xml`, `web.xml`, `tomcat-users.xml`, `context.xml`).
`/lib`	Shared JAR libraries and JDBC drivers.
`/logs`	Server log files (`catalina.out`, `localhost_access_log`).
`/webapps`	Directory where web applications (`.war` files or unpacked directories) are deployed.
`/work`	Temporary work directory where compiled JSP servlets and temporary files are stored.

4. Configuration Steps for Apache Tomcat

Step 1: Install Prerequisites & Set Environment Variables

Tomcat requires Java Development Kit (JDK 8+). Set environment variables in the OS:

JAVA_HOME: Path to JDK directory (e.g., C:\Program Files\Java\jdk-17 or /usr/lib/jvm/java-17-openjdk).
CATALINA_HOME: Path to the root Tomcat installation directory.
Add %CATALINA_HOME%\bin (or $CATALINA_HOME/bin) to the system PATH.

Step 2: Configuring Server Ports (`conf/server.xml`)

To change the default HTTP port (from 8080 to 80 or custom port):

<!-- conf/server.xml -->
<Connector port="8080" protocol="HTTP/1.1"
           connectionTimeout="20000"
           redirectPort="8443"
           maxThreads="200" />

Step 3: Configuring Admin Users and Roles (`conf/tomcat-users.xml`)

To grant access to the Tomcat Web Application Manager GUI (http://localhost:8080/manager/html):

<!-- conf/tomcat-users.xml -->
<tomcat-users>
    <role rolename="manager-gui"/>
    <role rolename="admin-gui"/>
    <user username="admin" password="SecretPassword123" roles="manager-gui,admin-gui"/>
</tomcat-users>

Step 4: Global Web Application Settings (`conf/web.xml`)

Configures default MIME types, default welcome files (index.html, index.jsp), and global session timeouts:

<!-- conf/web.xml -->
<session-config>
    <session-timeout>30</session-timeout> <!-- In minutes -->
</session-config>

<welcome-file-list>
    <welcome-file>index.html</welcome-file>
    <welcome-file>index.jsp</welcome-file>
</welcome-file-list>

Step 5: Application Deployment & Server Management

Deploying Applications:
- Copy your .war archive (e.g., myapp.war) directly into the $CATALINA_HOME/webapps/ folder.
- Tomcat automatically unpacks and deploys the application.
Starting the Server:
- On Windows: Run bin\startup.bat
- On Linux/macOS: Run bin/startup.sh
Verifying Installation:
- Open browser at http://localhost:8080.
Stopping the Server:
- Run bin\shutdown.bat or bin/shutdown.sh.

Q4b. Compare and contrast HTTP, FTP, SMTP, and POP protocols in terms of their purpose and functionality.20257m

Module II: Browser & Apache Web Server Architecture; Common Protocols

Compare and contrast HTTP, FTP, SMTP, and POP protocols in terms of their purpose and functionality.

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Comparison of HTTP, FTP, SMTP, and POP Protocols

1. Introduction

HTTP, FTP, SMTP, and POP are fundamental Application Layer protocols in the TCP/IP suite. While they all rely on TCP for reliable, end-to-end data delivery, they are optimized for distinct purposes: web browsing, file management, email transmission, and email retrieval.

                        +---------------------------+
                        |  APPLICATION LAYER (TCP)  |
                        +-------------+-------------+
                                      |
         +----------------+-----------+-----------+----------------+
         |                |                       |                |
         v                v                       v                v
      +----+           +----+                  +----+           +----+
      |HTTP|           |FTP |                  |SMTP|           |POP3|
      +----+           +----+                  +----+           +----+
     (Web Pages)    (File Transfer)          (Send Mail)     (Receive Mail)

2. Overview of Each Protocol

1. HTTP (HyperText Transfer Protocol)

Purpose: Distributed, collaborative hypermedia information retrieval for the World Wide Web.
Port: Port 80 (HTTP), Port 443 (HTTPS with TLS).
Mechanism: Request-Response model between clients (browsers) and web servers.
Characteristics: Stateless (does not retain client context across requests without cookies/sessions); supports caching and content negotiation.

2. FTP (File Transfer Protocol)

Purpose: Uploading, downloading, and managing files between a client and a remote server.
Port: Port 21 (Control Connection) and Port 20 (Data Connection in active mode).
Mechanism: Dual-channel architecture:
- Control Connection: Sends authentication commands (USER, PASS, LIST).
- Data Connection: Transfers raw file data.
Characteristics: Stateful session requiring explicit login authentication and directory navigation.

3. SMTP (Simple Mail Transfer Protocol)

Purpose: Push-based email transmission from email client to mail server, and between intermediate Mail Transfer Agents (MTAs).
Port: Port 25 (Server-to-server relay), Port 587 (Client submission with STARTTLS), Port 465 (SMTPS).
Mechanism: Text-based command/response stream (HELO/EHLO, MAIL FROM, RCPT TO, DATA, QUIT).
Characteristics: Unidirectional push protocol; cannot retrieve emails from a server mailbox.

4. POP3 (Post Office Protocol version 3)

Purpose: Pull-based email retrieval protocol allowing email clients (e.g., Outlook, Thunderbird) to download messages from a remote mail server.
Port: Port 110 (Plain POP3), Port 995 (POP3S over SSL/TLS).
Mechanism: Client authenticates (USER, PASS), lists messages (LIST), downloads message bodies (RETR), and marks messages for deletion (DELE).
Characteristics: Typically downloads emails to local storage and removes them from the server mailbox (unlike IMAP, which synchronizes in-place).

3. Comprehensive Comparison Matrix

Parameter	HTTP	FTP	SMTP	POP3
Full Name	HyperText Transfer Protocol	File Transfer Protocol	Simple Mail Transfer Protocol	Post Office Protocol v3
Primary Function	Transferring web pages & APIs	Uploading/downloading files	Sending & relaying emails	Downloading/retrieving emails
Default Ports	`80` (HTTP), `443` (HTTPS)	`21` (Control), `20` (Data)	`25` (Relay), `587` (Submission)	`110` (Plain), `995` (SSL)
Transport Protocol	TCP	TCP	TCP	TCP
Architecture	Client-Server Request/Response	Dual-channel Client-Server	Push (Client->Server, Server->Server)	Pull (Client <- Server)
Connection Model	Single connection per request	Two separate connections	Single persistent TCP stream	Single session per transaction
Session State	Stateless	Stateful	Stateful (during mail transaction)	Stateful (during mailbox lock)
Data Types Handled	HTML, JSON, Images, Video	Binary files, text files	Plain text, MIME encoded email	MIME encoded email messages
Secure Variant	HTTPS	FTPS / SFTP	SMTPS (TLS)	POP3S (TLS)

Conclusion

Each protocol serves a targeted domain: HTTP delivers interactive web content, FTP enables robust bulk file synchronization, SMTP pushes outgoing emails across networks, and POP3 retrieves and downloads stored mailboxes to client machines.

Q5a. Discuss the importance of search engine optimization (SEO) in e-commerce. What practices can improve a website's visibility in search results?20257m
Module IV: E-commerce Applications
Discuss the importance of search engine optimization (SEO) in e-commerce. What practices can improve a website's visibility in search results?

View this question on its own page →
Search Google Ask AI
Worked Solution
Answer: Importance of Search Engine Optimization (SEO) in E-Commerce

1. What is E-Commerce SEO?

Search Engine Optimization (SEO) in e-commerce is the practice of optimizing an online store's web pages, product listings, category taxonomy, and technical architecture so they rank higher in unpaid (organic) search engine results pages (SERPs) like Google and Bing.

2. Importance of SEO in E-Commerce

+-----------------------+ +-----------------------+ +-----------------------+ | High-Intent Traffic | --> | Lower Customer Cost | --> | Sustainable Revenue | | (Ready-to-Buy Users) | | (No Cost-per-Click) | | & Brand Authority | +-----------------------+ +-----------------------+ +-----------------------+

High Purchase Intent: Users searching for specific queries (e.g., "buy noise cancelling wireless headphones") are often in the decision-making phase of the buyer journey, resulting in higher conversion rates.

Cost-Effective Customer Acquisition (CAC): Unlike paid advertising (PPC) where traffic stops once the budget is exhausted, organic SEO delivers continuous long-term traffic with no direct click cost.

Credibility and Trust: Users inherently trust top organic rankings more than sponsored ads.

Competitive Advantage: Outranking competitor storefronts on high-volume commercial keywords directly captures market share.

Mobile & Local Discovery: Essential for capturing mobile shoppers and location-based store queries.

3. Best Practices to Improve E-Commerce Search Visibility

A. On-Page SEO Optimization

Keyword-Optimized Product Titles & Headers: Use clear, search-friendly titles including brand, model, color, and size (e.g., Brand + Model + Product Category).

Unique, Descriptive Content: Avoid manufacturer-provided default descriptions; write unique copy highlighting features, specifications, and benefits to avoid duplicate content penalties.

Optimized Meta Tags: Craft compelling meta titles (under 60 characters) and meta descriptions (under 160 characters) with clear Calls to Action (CTAs).

Image Optimization:

Use descriptive file names (e.g., sony-wh1000xm5-black.webp).

Add informative alt text for screen readers and Google Image search.

Compress images using modern formats (WebP/AVIF).

B. Technical SEO

Structured Data Markup (Schema.org): Implement JSON-LD structured data for Product, Offer, AggregateRating, Price, and Availability to qualify for rich snippets in Google search results.

{ "@context": "https://schema.org/", "@type": "Product", "name": "Wireless Bluetooth Headphones", "image": "https://example.com/photos/1x1/photo.jpg", "offers": { "@type": "Offer", "priceCurrency": "INR", "price": "4999", "availability": "https://schema.org/InStock" } }

Core Web Vitals & Fast Page Loading: Optimize Largest Contentful Paint (LCP) and Cumulative Layout Shift (CLS); fast websites rank higher and retain buyers.

Mobile-First Responsiveness: Ensure the store provides seamless checkout and navigation on smartphones.

Canonical Tags (rel="canonical"): E-commerce stores often create multiple URLs for the same product via filters/sorting (e.g., ?color=red&sort=price_asc). Canonical tags specify the master URL to avoid duplicate content penalties.

HTTPS Security: SSL certificates are mandatory for search ranking and payment security.

C. Site Architecture & Navigation

Shallow Hierarchy (3-Click Rule): Ensure any product is reachable within 3 clicks from the homepage:
Home -> Category -> Subcategory -> Product Page.

Breadcrumb Navigation: Provides contextual internal linking for search engine crawlers and users.

Clean URL Structures: Use clean slugs (e.g., /products/wireless-headphones) instead of dynamic parameter strings (/?prod_id=8923&cat=12).

D. Off-Page SEO & Content Strategy

E-commerce Blogging & Buying Guides: Publish comparison articles, gift guides, and troubleshooting tutorials linking to relevant catalog items.

Customer Reviews & UGC: Customer reviews regularly refresh on-page content with long-tail keyword variations.

High-Quality Backlinks: Gain backlinks through product reviews on tech blogs, influencer partnerships, and industry publications.

Q5b. Discuss the role and functions of rendering engines in modern browsers.20257m

Module II: Browser & Apache Web Server Architecture; Common Protocols

Discuss the role and functions of rendering engines in modern browsers.

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Role and Functions of Rendering Engines in Modern Browsers

1. What is a Rendering Engine?

A rendering engine (also known as a layout engine) is the primary software component of a web browser responsible for interpreting HTML, XML, CSS, and embedded media assets, and translating that structured code into visual pixels painted onto the user's screen.

               +---------------------------------------------+
               |             RENDERING ENGINE                |
               |                                             |
HTML Source -> | [HTML Parser]  -->  DOM Tree  \             |
               |                                 -> Render   | -> Layout -> Paint -> Screen
CSS Source  -> | [CSS Parser]   -->  CSSOM Tree /    Tree    |  (Reflow)  (Raster)
               +---------------------------------------------+

2. Major Modern Rendering Engines

Engine	Developed By	Used in Browsers
Blink	Google (Fork of WebKit)	Google Chrome, Microsoft Edge, Brave, Opera, Vivaldi
Gecko	Mozilla Foundation	Mozilla Firefox
WebKit	Apple	Apple Safari, all iOS web browsers

3. Core Functions of a Rendering Engine

1. Document Parsing & Tree Construction

HTML Parsing & DOM Tree: Converts raw HTML byte streams into tokens, which are turned into nodes forming the hierarchical Document Object Model (DOM) tree.
CSS Parsing & CSSOM Tree: Parses CSS stylesheets (inline, external, and embedded) to construct the CSS Object Model (CSSOM) tree representing styling rules.

2. Render Tree Construction (Frame Tree)

Merges the DOM tree and CSSOM tree into a Render Tree.
The Render Tree only includes nodes that are actually visible (e.g., <head>, <script>, and elements with display: none are omitted; elements with visibility: hidden are included).
Calculates computed styles (font sizes, colors, margins) for every visible element.

3. Layout (Reflow) Process

Traverses the Render Tree to calculate the exact geometric coordinates, position ( $X, Y$ ), and dimensions (width, height) of every node relative to the viewport.
Handles box model metrics: margins, borders, padding, floats, flexbox, and CSS grid layouts.

4. Painting (Rasterization)

Converts visual layout boxes into actual pixel data in memory.
Draws backgrounds, borders, text, colors, shadows, and images.
Elements are split into separate graphical layers (e.g., video, canvas, 3D transforms).

5. Compositing (GPU Acceleration)

Modern rendering engines send individual graphical layers to the GPU (Graphics Processing Unit) for hardware-accelerated compositing.
The GPU composites layers in the correct stacking order ( $z\text{-index}$ ) and displays the final raster image onto the physical screen without needing to re-layout the whole page.

4. Key Performance Optimizations in Modern Engines

Incremental / Asynchronous Rendering: Modern engines do not wait for the entire HTML document to download; they parse and display partial content incrementally to minimize First Contentful Paint (FCP).
Minimizing Reflow & Repaint:
- Reflow: Re-calculating geometric layout (expensive).
- Repaint: Re-drawing color/visibility changes without altering geometry (lighter).
Speculative Pre-parsing: While scripts are executing, a secondary scanner looks ahead in HTML to discover and prefetch external resources (CSS, JS, images).
Hardware Acceleration: Offloads computationally heavy tasks (CSS animations, smooth scrolling, video playback) to dedicated graphics hardware.

Q6a. Describe the architecture and components of a Java Servlet.20257m
Module III: Basics of Web Programming
Describe the architecture and components of a Java Servlet.

View this question on its own page →
Search Google Ask AI
Worked Solution
Answer: Architecture, Life Cycle, and Components of a Java Servlet

1. What is a Java Servlet?

A Java Servlet is a server-side Java program running inside a Servlet Container (e.g., Apache Tomcat, Jetty, WildFly). It intercepts client requests, executes business logic, interacts with databases, and dynamically generates web responses (HTML, JSON, XML).

+-------------------+ 1. HTTP Request (GET/POST) +---------------------+ | Web Browser | --------------------------------------> | Web Server | | (Client) | <-------------------------------------- | (Apache Tomcat) | +-------------------+ 4. HTTP Response (HTML/JSON) +----------+----------+ | +---------------------v---------------------+ | SERVLET CONTAINER | | | | +-----------------------------------+ | | | Servlet Instance | | | | | | | | - init(ServletConfig config) | | | | - service(req, res) | | | | -> doGet() / doPost() | | | | - destroy() | | | +-----------------------------------+ | +-------------------------------------------+

2. Servlet Life Cycle Methods

The servlet life cycle is entirely managed by the servlet container through three fundamental methods:

[Load & Instantiate] ---> [init()] ---> [service() (doGet / doPost)] ---> [destroy()]

Initialization (init(ServletConfig config)):

Invoked once when the servlet is first loaded into memory.

Used for one-time initialization tasks (opening database connections, reading configuration parameters).

Execution (service(ServletRequest req, ServletResponse res)):

Invoked for every client request in a separate worker thread.

For HttpServlet, the service() method dispatches the request to doGet(), doPost(), doPut(), or doDelete() based on the HTTP method.

Destruction (destroy()):

Invoked once before the container takes the servlet instance out of service.

Used to release resources, close database connections, and save state.

3. Major Components of the Servlet Architecture

1. Servlet Interface (jakarta.servlet.Servlet)

The central root interface of all Java servlets. Declares life cycle methods (init, service, destroy, getServletConfig, getServletInfo).

2. HttpServlet Abstract Class (jakarta.servlet.http.HttpServlet)

Provides an HTTP-specific implementation. Subclassed by developers to handle standard HTTP verbs:

doGet(HttpServletRequest request, HttpServletResponse response)

doPost(HttpServletRequest request, HttpServletResponse response)

3. ServletConfig

Holds initialization parameters and configuration information specific to a single servlet instance defined in web.xml or via @WebServlet(initParams={...}).

4. ServletContext

Represents the broader web application context shared by all servlets in the application.

Used to store global application-level attributes, communicate between servlets, and access server logs.

5. HttpServletRequest & HttpServletResponse

HttpServletRequest: Encapsulates incoming request data (parameters, headers, cookies, form data, session).

HttpServletResponse: Provides methods to set response headers, status codes, cookies, and obtain an output stream (PrintWriter or ServletOutputStream) to write content back to the client.

6. HttpSession

Provides stateful session tracking across multiple HTTP requests for an individual user (e.g., maintaining user login or shopping cart data).

4. Example: Simple HttpServlet Implementation

import java.io.IOException; import java.io.PrintWriter; import jakarta.servlet.ServletException; import jakarta.servlet.annotation.WebServlet; import jakarta.servlet.http.HttpServlet; import jakarta.servlet.http.HttpServletRequest; import jakarta.servlet.http.HttpServletResponse; @WebServlet("/welcome") public class WelcomeServlet extends HttpServlet { @Override protected void doGet(HttpServletRequest request, HttpServletResponse response) throws ServletException, IOException { response.setContentType("text/html;charset=UTF-8"); PrintWriter out = response.getWriter(); String username = request.getParameter("name"); out.println("<!DOCTYPE html><html><body>"); out.println("<h2>Hello, " + (username != null ? username : "Guest") + "!</h2>"); out.println("</body></html>"); } }

Q6b. What are Distributed Object Models? Compare CORBA, DCOM, and EJB.20257m

Module III: Basics of Web Programming

What are Distributed Object Models? Compare CORBA, DCOM, and EJB.

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Distributed Object Models — Comparison of CORBA, DCOM, and EJB

1. What is a Distributed Object Model?

A Distributed Object Model (DOM) is an architectural paradigm in distributed computing where software objects located on different physical machines across a network can communicate and invoke methods on one another as if they were residing in the same local memory space.

+-----------------------+                            +-----------------------+
|     Client System     |                            |     Server System     |
|                       |                            |                       |
|   [Client Program]    |                            |   [Remote Object]     |
|          |            |                            |          ^            |
|          v            |                            |          |            |
|     [Stub/Proxy]      |                            |   [Skeleton/Adapter]  |
|          |            |                            |          ^            |
|          v            |                            |          |            |
|    [ORB / Runtime]    | === Network Communication => |    [ORB / Runtime]    |
+-----------------------+       (IIOP / RPC / RMI)   +-----------------------+

Core Mechanisms:

Stub (Client Proxy): Marshals method parameters and serializes calls across the network.
Skeleton / Dispatcher: Unmarshals parameters on the remote server, invokes the actual method, and serializes the return value back.

2. Overview of CORBA, DCOM, and EJB

A. CORBA (Common Object Request Broker Architecture)

Specification: Defined by the Object Management Group (OMG) as an open vendor-neutral standard.
Key Feature: Truly platform-independent and language-independent. Interfaces are defined using OMG IDL (Interface Definition Language).
Communication: Uses an ORB (Object Request Broker) and communication protocol IIOP (Internet Inter-ORB Protocol).

B. DCOM (Distributed Component Object Model)

Specification: Developed by Microsoft as a network extension of COM (Component Object Model).
Key Feature: Deeply integrated into Windows OS; uses Microsoft RPC (Object RPC).
Limitation: Windows-centric and proprietary, with limited cross-platform interoperability.

C. EJB (Enterprise JavaBeans)

Specification: Developed by Sun Microsystems / Oracle (now part of Jakarta EE).
Key Feature: Pure Java-centric server-side component architecture for building transactional, secure, scalable enterprise business logic.
Container Architecture: Runs inside an EJB Container that automatically handles transactions, security, concurrency, connection pooling, and lifecycle.

3. Detailed Comparison Matrix

Parameter	CORBA	DCOM	EJB
Governing Body	Object Management Group (OMG)	Microsoft	Sun / Oracle / Jakarta EE
Platform Support	Platform Independent (Unix, Linux, Windows)	Windows Centric (Limited Unix support)	Cross-Platform (Any Java-supported OS)
Language Support	Multi-language (C++, Java, Python, Ada, COBOL)	Multi-language on Windows (C++, VB, C#)	Java Only
Interface Definition	OMG IDL (Interface Definition Language)	Microsoft IDL (MIDL)	Java Interfaces (Local / Remote)
Underlying Protocol	IIOP (Internet Inter-ORB Protocol)	ORPC (Object Remote Procedure Call)	RMI / IIOP
Enterprise Services	Basic CORBA services (Naming, Event, Security)	Microsoft MTS / COM+	Full Container Services (JTA, JPA, Security, Pooling)
Architecture Model	Client-Server with ORB middleware	Binary COM components over network	Component-Container model
Primary Strength	Universal vendor & language interoperability	High performance on Windows enterprise environments	Rapid enterprise development with built-in declarative services
Weakness	Steep learning curve, complex configuration	Windows lock-in, poor firewall traversal	Restricted to Java ecosystem

Conclusion

CORBA is ideal for heterogeneous legacy integration across multiple programming languages and OS platforms.
DCOM provided high performance in pure Microsoft Windows environments before modern Web APIs.
EJB remains the enterprise standard for pure Java distributed systems, offering automated transactional and container-managed persistence capabilities.

Q7a. Explain various E-business models with suitable examples.20257m

Module IV: E-commerce Applications

Explain various E-business models with suitable examples.

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Classification and Analysis of E-Business Models

1. What is an E-Business Model?

An E-business (Electronic Business) model defines the structured method by which a commercial organization utilizes digital technologies, the internet, and electronic platforms to conduct business transactions, deliver value to customers, generate revenue, and sustain competitive advantage.

2. Major E-Business Models (By Market Participants)

                  +-----------------------------------+
                  |       E-BUSINESS MODELS           |
                  +-----------------+-----------------+
                                    |
     +--------------+---------------+---------------+--------------+
     |              |                               |              |
     v              v                               v              v
+---------+    +---------+                     +---------+    +---------+
|   B2C   |    |   B2B   |                     |   C2C   |    |   C2B   |
+---------+    +---------+                     +---------+    +---------+
 (Amazon)       (Alibaba)                        (OLX)         (Upwork)

1. B2C (Business-to-Consumer)

Description: Businesses sell products, services, or digital content directly to individual end consumers over the internet.
Characteristics: High transaction volume, lower average order value, heavy reliance on digital marketing, recommendation algorithms, and streamlined checkout.
Examples:
- E-commerce Retail: Amazon, Flipkart, Nike.com.
- Digital Streaming Services: Netflix, Spotify.
- Online Food Delivery: Zomato, Swiggy, DoorDash.

2. B2B (Business-to-Business)

Description: Electronic commerce transactions conducted between two or more business enterprises (e.g., manufacturer to wholesaler, wholesaler to retailer).
Characteristics: Bulk ordering, customized negotiation, credit-based payments, complex supply chains, and automated EDI (Electronic Data Interchange).
Examples:
- Alibaba.com: Global wholesale trade portal connecting suppliers and global buyers.
- IndiaMART: B2B matchmaking directory for industrial equipment and raw materials.
- Enterprise Cloud/SaaS: Salesforce, Amazon Web Services (AWS), SAP.

3. C2C (Consumer-to-Consumer)

Description: Individual consumers trade, sell, or rent goods and services directly to other consumers through an intermediary digital platform.
Characteristics: Platform provides escrow payment protection, buyer/seller rating systems, search categorization, and dispute resolution.
Examples:
- OLX & Quikr: Peer-to-peer classifieds for used cars, electronics, and furniture.
- eBay: Global online consumer auction and marketplace.
- Airbnb: Homeowners renting rooms directly to travelers.

4. C2B (Consumer-to-Business)

Description: Individual consumers offer products, services, freelance labor, or intellectual property to commercial businesses.
Characteristics: Consumers specify terms, prices, or bids, and businesses accept or purchase.
Examples:
- Freelance Marketplaces: Upwork, Fiverr (freelancers selling design/programming services to enterprises).
- Stock Photography: Shutterstock, Getty Images (photographers selling photo licenses to companies).
- Influencer Marketing: Content creators selling brand endorsements to corporations.

5. Government-Centric Models (B2G, G2B, G2C)

B2G (Business-to-Government): Businesses selling goods/services to government entities via e-procurement (e.g., GeM - Government e-Marketplace in India).
G2C (Government-to-Citizen): Governments delivering public services electronically (e.g., passport portals, tax filing via IncomeTax.gov.in).

3. Major Revenue & Monetization Models

Model	Revenue Mechanism	Example
Direct Sales (E-Tailer)	Sells physical/digital inventory with profit margin	Apple Store, Dell.com
Marketplace (Commission)	Takes percentage fee per transaction between third-party sellers & buyers	Amazon Marketplace, Uber
Subscription Model	Charges periodic recurring fees (monthly/annual) for service access	Netflix, Microsoft 365
Advertising Model	Free service monetized by displaying targeted ads to massive audiences	Google Search, Meta/Facebook
Freemium Model	Basic features free; advanced enterprise features behind paid tier	Canva, GitHub, Spotify
Affiliate Model	Earns referral commission when visitors buy from partner merchants	Wirecutter, CashKaro

Conclusion

Modern digital enterprises frequently employ hybrid e-business models (e.g., Amazon functions as both a B2C direct e-tailer, a B2B cloud vendor via AWS, and a marketplace broker). Selecting the right model depends on target audience, operational costs, logistics, and revenue strategy.

Q7b. What are the key elements in designing an effective e-commerce website?20257m

Module IV: E-commerce Applications

What are the key elements in designing an effective e-commerce website?

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Key Elements in Designing an Effective E-Commerce Website

1. Introduction

Designing an effective e-commerce website requires a harmonious combination of visual aesthetics, intuitive usability (UX), technical performance, frictionless checkout, and security trust. The primary goal is to guide visitors effortlessly from product discovery to a completed purchase while maximizing customer retention.

+-----------------------------------------------------------------------+
|                    EFFECTIVE E-COMMERCE DESIGN                        |
+-------------------+-------------------+---------------+---------------+
| 1. User Interface | 2. Product Search | 3. Checkout   | 4. Security   |
|    & Visual UX    |    & Discovery    |    Experience |    & Trust    |
| - Mobile-First    | - Faceted Filter  | - Guest Mode  | - SSL/TLS     |
| - Clear CTAs      | - High-Res Media  | - 1-Click Pay | - Reviews/UGC |
+-------------------+-------------------+---------------+---------------+

2. Key Design Elements

1. Intuitive Navigation & Search

Prominent Search Bar: Positioned centrally in the header with intelligent autocomplete, typo-tolerance, and instant product previews.
Structured Category Taxonomy: Logical mega-menus and breadcrumbs (Home > Electronics > Audio > Headphones) ensuring users find items within 3 clicks.
Faceted Filtering & Sorting: Multi-attribute filtering by price range, brand, color, size, ratings, and stock status.

2. High-Converting Product Detail Pages (PDP)

High-Quality Visual Media: Multiple high-resolution images, 360-degree interactive viewers, and product demo videos.
Clear Value & Pricing: Visible retail price, discounted price, percentage saved, and estimated delivery dates.
Prominent Call-to-Action (CTA): High-contrast, sticky "Add to Cart" and "Buy Now" buttons.
Detailed Specifications & Descriptions: Bulleted product highlights, dimensions, compatibility, and care instructions.

3. Mobile-First Responsiveness & Speed

Over 70% of e-commerce traffic originates on smartphones. Design touch-friendly buttons (minimum 44x44px), swipeable product galleries, and bottom navigation bars.
Fast Page Load Times: Optimize Core Web Vitals (sub-2 second load times) using modern image formats (WebP/AVIF), CDNs, and code-splitting. Every 1-second delay reduces conversions by ~7%.

4. Frictionless Checkout Process

Guest Checkout Option: Never force mandatory account creation before purchase; allow guest checkout with just an email and phone number.
Simplified Form Design: Single-page or multi-step accordion checkout with clear progress bars and address autofill.
Transparent Pricing: Disclose shipping fees, taxes, and handling costs upfront to prevent cart abandonment.

5. Multi-Payment Integration & Security Trust

Diverse Payment Gateways: Support local and international payment methods:
- UPI (Google Pay, PhonePe, Paytm)
- Credit/Debit Cards (Visa, Mastercard, RuPay)
- Net Banking & Digital Wallets
- Cash on Delivery (COD) & Pay Later (BNPL)
Security Badges: Display SSL lock icons, PCI-DSS compliance badges, and secure payment processor logos.

6. Social Proof & Customer Reviews

Verified buyer reviews with user-submitted photos and star ratings.
Transparent return policy, warranty terms, and money-back guarantee prominently displayed near the "Buy" button.
Customer Q&A section to resolve common pre-purchase doubts.

7. Customer Support & Post-Purchase Experience

24/7 Live Chat or AI conversational support for instant assistance.
Clear order confirmation with SMS/Email notifications.
Self-service real-time shipment tracking portal.

3. Design Checklist Summary

Design Dimension	Critical Implementation
Header	Logo, Global Search, Wishlist, Cart with item counter badge
Catalog	Grid/List toggle, price filter, quick-view preview modal
Product Page	Clear title, dynamic pricing, zoomable photos, stock availability
Cart / Checkout	Order summary with item thumbnails, promo code input, one-click checkout
Footer	Contact info, privacy policy, terms of service, payment icons, social links

Q8a. Explain the process of search engine and directory registration in the context of e-commerce marketing.20257m

Module IV: E-commerce Applications

Explain the process of search engine and directory registration in the context of e-commerce marketing.

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Search Engine and Directory Registration in E-Commerce Marketing

1. Introduction

In e-commerce marketing, Search Engine and Directory Registration is the systematic process of submitting and indexing an online store with major search engines (e.g., Google, Bing) and curated web/trade directories (e.g., Google Business Profile, Yelp, IndiaMART, YellowPages). It is a foundational step in establishing online presence, driving organic traffic, and building domain authority.

+------------------------------------------------------------------------+
|                      E-COMMERCE SITE REGISTRATION                      |
+------------------------------------+-----------------------------------+
|     SEARCH ENGINE REGISTRATION     |      WEB DIRECTORY REGISTRATION   |
| (Google, Bing, Yahoo)              | (Local & Trade Directories)       |
| - Automated Crawler Discovery      | - Human / Editorial Categorization|
| - XML Sitemap Submission           | - NAP (Name, Address, Phone) Data |
| - Search Console Verification      | - Backlink & Referral Traffic     |
+------------------------------------+-----------------------------------+

2. Process of Search Engine Registration

Search engines rely on automated crawlers (bots/spiders) to index web pages. The registration process ensures crawlers discover, crawl, and correctly index all e-commerce catalog URLs:

Step 1: Webmaster Account Creation & Verification

Register with search console platforms:
- Google Search Console (GSC)
- Bing Webmaster Tools
Verify domain ownership through one of the following methods:
- Adding a DNS TXT record at the domain registrar (recommended).
- Uploading a verification HTML file to the web server root.
- Inserting a <meta name="google-site-verification" content="..."> tag in the homepage <head>.

Step 2: Generation and Submission of XML Sitemaps

Generate a dynamic XML Sitemap containing all public URLs, product pages, category pages, images, and modification timestamps (lastmod).
Submit the sitemap URL (e.g., https://www.example.com/sitemap.xml) directly in Google Search Console and Bing Webmaster Tools.

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/products/laptop</loc>
    <lastmod>2026-08-20</lastmod>
    <changefreq>weekly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Step 3: Configuring Crawler Instructions (`robots.txt`)

Create a robots.txt file at the root of the server to guide search engine spiders, specifying paths to crawl and paths to ignore (e.g., checkout pages, user cart, admin dashboard).

User-agent: *
Disallow: /checkout/
Disallow: /cart/
Disallow: /admin/
Sitemap: https://www.example.com/sitemap.xml

Step 4: Indexing Request & Monitoring

Use the URL Inspection Tool to request manual indexing for new high-priority product launches.
Monitor crawl errors (404s, 500s), indexing status, mobile usability issues, and Core Web Vitals reports.

3. Process of Web Directory Registration

Web directories organize business listings into structured hierarchical categories (e.g., Business > Retail > Electronics).

Step 1: Directory Selection & Classification

Identify reputable, authoritative directories:
- Local Business Directories: Google Business Profile, Bing Places, Apple Maps.
- Niche/Trade Directories: IndiaMART, TradeIndia, ThomasNet (for B2B e-commerce).
- Review & Consumer Portals: Trustpilot, Sitejabber, Better Business Bureau (BBB).

Step 2: Ensuring NAP Consistency

Ensure NAP (Name, Address, Phone Number) and business website URL are 100% consistent across all directory listings to maximize local and organic SEO trust signals.

Step 3: Profile Submission

Choose the exact relevant industry category.
Submit business description, product catalog keywords, brand logo, working hours, and physical store/warehouse address.
Complete email or postal PIN verification required by directory editors.

4. Comparison: Search Engines vs. Web Directories

Parameter	Search Engines	Web Directories
Discovery Mechanism	Automated crawlers (Googlebot, Bingbot)	Human editors / structured submission forms
Organization	Algorithmic ranking based on relevance & links	Hierarchical subject categories
Update Frequency	Continuous / Automated re-crawling	Periodic / Static manual updates
Primary Value	Massive search query volume & conversions	High-authority citation backlinks & referral trust

5. Marketing Benefits for E-Commerce

Faster Indexation: Search engines discover new e-commerce stores faster when linked from established directories and search consoles.
Quality Backlinks: Authoritative directory listings pass link equity (Domain Authority) to the e-commerce store.
Local Customer Acquisition: Enables "Near Me" search visibility for stores offering local pickups or regional deliveries.

Q8b. What is Web 3.0? How does it differ from Web 2.0?20257m

Module V: Web 3.0 — Semantic Web and Supporting Technologies

What is Web 3.0? How does it differ from Web 2.0?

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Web 3.0 and Its Comparison with Web 2.0

1. Evolution of the World Wide Web

+-------------------+        +--------------------+        +---------------------+
|      Web 1.0      |        |      Web 2.0       |        |       Web 3.0       |
|  (1990s - 2004)   | -----> |  (2004 - Present)  | -----> |    (Emerging Era)   |
|   "Read-Only"     |        |  "Read-Write /     |        |    "Read-Write-Own  |
| (Static Web Pages)|        |   Social Web"      |        |  / Semantic Web"    |
+-------------------+        +--------------------+        +---------------------+

2. What is Web 3.0?

Web 3.0 (often referred to as the Semantic Web or the Decentralized Web) represents the next generation of internet architecture. It combines machine-understandable metadata (semantics), Artificial Intelligence (AI), and Decentralized Ledger Technology (Blockchain) to create an open, trustless, permissionless, and intelligent internet where users own their data and digital identities.

3. Core Pillars of Web 3.0

Semantic Web & Linked Data: Information is categorized and structured using standard semantic ontologies (RDF, OWL, SPARQL) so machines can understand the contextual meaning of queries rather than relying solely on keyword matching.
Decentralization & Edge Computing: Data and services are distributed across peer-to-peer networks (e.g., IPFS, blockchain nodes) rather than centralized corporate server farms (AWS, Google Cloud).
Artificial Intelligence & Natural Language Processing (NLP): Intelligent agents and LLMs interpret complex user queries, automate decision-making, and generate personalized experiences.
User Ownership & Digital Sovereignty: Users retain control of their data, assets, and identity using cryptographic wallets (e.g., Ethereum, Solana, DIDs) rather than proprietary corporate logins (Google/Facebook OAuth).
Smart Contracts: Programmable, self-executing agreements that execute transparently on distributed networks without intermediaries.

4. Comprehensive Comparison: Web 2.0 vs. Web 3.0

Feature	Web 2.0 (Social & Interactive Web)	Web 3.0 (Semantic & Decentralized Web)
Core Philosophy	Read-Write (User-generated content)	Read-Write-Own (Decentralized & Intelligent)
Data Control	Centralized in big tech corporations (Meta, Google, Amazon)	Distributed across decentralized networks; owned by users
Architecture	Client-Server (Centralized databases like MySQL/Oracle)	Peer-to-Peer (P2P), Blockchains, IPFS, Edge Computing
Search Paradigm	Keyword-based text indexing	Contextual, Semantic & AI-driven understanding
User Identity	Corporate-controlled accounts (Email/Password, OAuth)	Self-Sovereign Identity (Cryptographic public/private keys)
Trust Model	Trust required in centralized intermediaries/banks	Trustless & Permissionless (Cryptographic proof & Smart Contracts)
Monetization Model	Targeted digital advertising based on personal data tracking	Token economics, micro-payments, smart contract fees
Key Technologies	AJAX, HTML5, CSS3, REST APIs, JavaScript frameworks	RDF, OWL, Blockchain, Smart Contracts, AI/ML, IPFS
Prominent Examples	Facebook, YouTube, Twitter, Instagram, Wikipedia	Uniswap, IPFS, Brave Browser, Ethereum, Solid Project

Conclusion

While Web 2.0 democratized content creation and brought dynamic social collaboration at the cost of data centralization and privacy, Web 3.0 shifts the internet toward machine intelligence, semantic interoperability, and user-owned decentralized ecosystems.

Q9a. Explain the concept of the Semantic Web and its significance in intelligent web applications.20257m
Module V: Web 3.0 — Semantic Web and Supporting Technologies
Explain the concept of the Semantic Web and its significance in intelligent web applications.

View this question on its own page →
Search Google Ask AI
Worked Solution
Answer: Concept and Significance of the Semantic Web

1. Concept of the Semantic Web

The Semantic Web is an extension of the current World Wide Web, conceptualized by web inventor Tim Berners-Lee, in which web information is given well-defined meaning (semantics), enabling computers and software agents to automatically understand, process, infer, and integrate data from disparate sources.

While the traditional web is a "Web of Documents" designed for human reading, the Semantic Web creates a "Web of Linked Data" designed for direct machine interpretation.

+---------------------------------------------+ | User Interface & Trust | +---------------------------------------------+ | Proof & Cryptographic Verification | +---------------------------------------------+ | Rules (RIF / SWRL) & Logic Engine | +---------------------------------------------+ | Ontology Vocabulary (OWL / RDFS) | +---------------------------------------------+ | Query Language (SPARQL) | +---------------------------------------------+ | Data Interchange (RDF / Triples) | +---------------------------------------------+ | XML / XML Schema | +---------------------------------------------+ | URI (Universal Identifiers) / IRI | +---------------------------------------------+

2. Core Building Blocks of Semantic Web Architecture

1. Uniform Resource Identifiers (URI / IRI)

Provide globally unique, unambiguous identifiers for real-world entities, concepts, and relationships across the globe (e.g., http://dbpedia.org/resource/Albert_Einstein).

2. Resource Description Framework (RDF)

Standard data model representing information as a graph of Triples:
$\text{Subject} \xrightarrow{\quad \text{Predicate} \quad} \text{Object}$

Example:

Subject: http://example.org/Book123

Predicate: http://purl.org/dc/elements/1.1/creator

Object: "James Gosling"

3. Web Ontology Language (OWL) & RDF Schema (RDFS)

Defines rich formal vocabularies and domain ontologies, including classes, subclasses, inverse properties, and cardinality restrictions.

Enables logical reasoning (e.g., if class Professor is a subclass of Person, and Dr. Smith is a Professor, the system infers that Dr. Smith is a Person).

4. SPARQL Protocol and RDF Query Language

The standard SQL-like declarative query language used to search and extract data across distributed RDF graph databases (triplestores).

3. Significance in Intelligent Web Applications

1. Contextual Search & Knowledge Graphs

Powers modern search engines (like the Google Knowledge Graph) to answer direct factual questions (e.g., "What is the capital of France?") instead of just returning links to text pages containing matching keywords.

2. Cross-Domain Data Integration (Linked Open Data)

Unifies heterogeneous databases across multiple organizations without requiring rigid centralized database schemas (e.g., linking DBpedia, Wikidata, and government statistical portals).

3. Automated Decision-Making & AI Agents

Autonomous software agents can negotiate, query across flight schedules, hotel databases, and payment APIs to plan complete travel itineraries autonomously.

4. Healthcare & Biomedical Research

Clinical ontologies like SNOMED CT and Gene Ontology allow AI systems to correlate patient symptoms, genetic markers, and medical drug databases for personalized diagnosis and automated drug interaction warnings.

5. Semantic E-Commerce & Smart Recommendation

Search engines parse Schema.org microdata to display rich product badges (price, stock status, ratings) and generate contextually relevant product recommendations.

Q9b. What are the main configuration settings required for browsers such as Netscape and Internet Explorer (IE)?20257m

Module II: Browser & Apache Web Server Architecture; Common Protocols

What are the main configuration settings required for browsers such as Netscape and Internet Explorer (IE)?

View this question on its own page →

Search Google Ask AI

Worked Solution

Answer: Configuration Settings in Classic Browsers (Netscape and Internet Explorer)

1. Overview

Web browsers such as Netscape Navigator / Communicator and Microsoft Internet Explorer (IE) established the foundational configuration architectures for client-side web navigation, network proxies, security zones, and MIME content handling.

2. Main Configuration Categories

+-----------------------------------------------------------------------+
|                    BROWSER CONFIGURATION SUBSYSTEMS                   |
+-------------------+-------------------+---------------+---------------+
| 1. Network/Proxy  | 2. Security Zones | 3. Content    | 4. Cache &    |
|    Settings       |    & SSL/TLS      |    & MIME     |    Privacy    |
| - HTTP/FTP Proxy  | - Active Scripting| - Helper Apps | - Cookie Rules|
| - Port Mapping    | - ActiveX Controls| - Java/Plugins| - Disk Quota  |
+-------------------+-------------------+---------------+---------------+

1. Network & Proxy Connection Settings

Direct vs. Proxy Connections: Configuring proxy servers for HTTP, Secure (HTTPS), FTP, and SOCKS connections to route internet traffic through institutional firewalls or cache gateways.
Automatic Configuration (PAC): Configuring an Automatic Proxy Configuration Script URL (wpad.dat / .pac file) or WPAD (Web Proxy Auto-Discovery Protocol).
Proxy Exceptions: Specifying local IP ranges and intranet domains (localhost, *.internal.net) to bypass proxy routing.

2. Security Zones and Scripting Permissions

Security Zones (Distinct in Internet Explorer):
- Internet Zone: Default restricted sandbox for untrusted public websites.
- Local Intranet Zone: Lower security settings for internal enterprise networks.
- Trusted Sites Zone: Elevated privileges for verified partner portals.
- Restricted Sites Zone: Maximum security restrictions for unsafe sites.
Active Scripting & Controls:
- Toggling JavaScript / VBScript execution.
- Enabling or prompting for signed/unsigned ActiveX Controls (in IE) and Java Applets.
Cryptographic Protocols: Enabling SSL 2.0/3.0 and modern TLS protocols for secure HTTPS transactions.

3. Content Handlers and MIME Type Associations

Helper Applications (Major feature in Netscape): Mapping specific MIME types (e.g., application/pdf, audio/x-wav, video/quicktime) to external standalone viewer applications or internal browser plug-ins.
File Download Handling: Defining automated actions when downloading file extensions (Prompt user, Save to disk, or Launch helper app).

4. Cache and Temporary Internet Files Management

Disk Cache Allocation: Allocating disk storage limits (e.g., 50MB to 500MB) to store cached web assets (HTML, stylesheets, images).
Page Verification Frequency: Setting when the browser checks the server for newer page versions:
- Every visit to the page
- Every time the browser is started
- Automatically
- Never (offline mode)
Cache Purging: Options to clear history, form autofill, and temporary internet files on browser exit.

5. Privacy, Cookies, and Identity

Cookie Management: Granular policies for accepting, prompting, or blocking First-Party and Third-Party tracking cookies.
Personal Certificate Management: Importing and managing client-side X.509 digital certificates for secure client authentication.

3. Netscape vs. Internet Explorer Configuration Architecture

Feature	Netscape Navigator	Microsoft Internet Explorer
Storage Mechanism	Plaintext JavaScript configuration file (`prefs.js` / `all.js`)	Windows Registry (`HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings`)
Configuration GUI	Edit > Preferences Menu	Tools > Internet Options (Control Panel)
Security Architecture	Java Permissions & Security Capabilities API	Security Zones (Internet, Intranet, Trusted, Restricted)
Extensibility Model	Netscape Plugin API (NPAPI)	ActiveX Controls, COM components, BHOs
Enterprise Policy	Centralized `netscape.cfg` deployment	Group Policy Objects (GPO) via Active Directory

Previous year2020

Web Technology

Correct Answer: (i) SGML

Explanation:

Key Points:

Correct Answer: (ii) DTD

Explanation:

Example of DTD Declaration:

Correct Answer: (i) Rendering engine

Explanation:

Roles of other Browser Components:

Correct Answer: (iii) User profile directory

Explanation:

Comparison:

Correct Answer: (ii) Apache (Note: Nginx and Tomcat are also open-source; IIS is proprietary)

Explanation:

Key Features of Apache HTTP Server:

Correct Answer: (ii) Running Java-based web applications

Explanation:

Comparison:

Correct Answer: (iii) JSP

Explanation:

How JSP Works on Server:

Correct Answer: (ii) JavaScript

Explanation:

Correct Answer: (i) HTTPS

Explanation:

Security Guarantees:

Correct Answer: (ii) Data interlinking and machine understanding

Explanation:

Core Objectives:

Answer: Client/Server Computing vs N-Tiered Architecture

1. Client/Server Computing

Client

Server

2. N-Tiered Architecture

Presentation Tier

Business Logic Tier

Data Tier

3. Comparison

4. Advantages of N-Tier Architecture

Conclusion

Answer: SGML and Its Relationship with HTML, XML, and XSL

1. What is SGML?

2. Relationship with HTML, XML, and XSL

A. HTML (HyperText Markup Language)

B. XML (eXtensible Markup Language)

C. XSL (eXtensible Stylesheet Language)

3. Comparison Table

Conclusion

Answer: Web Browser Architecture and Major Components

1. Introduction

2. Major Components of a Browser

1. User Interface (UI)

2. Browser Engine

3. Rendering Engine

4. Networking Layer

5. JavaScript Engine (Interpreter)

6. UI Backend

7. Data Persistence (Storage Layer)

3. Basic Rendering Flow Pipeline

Answer: Browser-Server Interaction via the HTTP Request-Response Model

1. Overview

2. Step-by-Step Interaction Lifecycle

Step 1: URL Parsing and DNS Lookup

Step 2: Establishing TCP Connection

Step 3: TLS/SSL Handshake (For HTTPS)

Step 4: Browser Sends HTTP Request

Step 5: Server Processing and HTTP Response

Step 6: Rendering and Additional Asset Requests

3. Key Components of HTTP Messages

4. Common HTTP Status Codes

Answer: Features and Configuration Steps of Apache Tomcat Server

1. Overview of Apache Tomcat

2. Key Features of Apache Tomcat

3. Directory Structure of Tomcat

4. Configuration Steps for Apache Tomcat

Step 1: Install Prerequisites & Set Environment Variables

Step 2: Configuring Server Ports (conf/server.xml)

Step 3: Configuring Admin Users and Roles (conf/tomcat-users.xml)

Step 4: Global Web Application Settings (conf/web.xml)

Step 2: Configuring Server Ports (`conf/server.xml`)

Step 3: Configuring Admin Users and Roles (`conf/tomcat-users.xml`)

Step 4: Global Web Application Settings (`conf/web.xml`)

1. `Servlet` Interface (`jakarta.servlet.Servlet`)

2. `HttpServlet` Abstract Class (`jakarta.servlet.http.HttpServlet`)

3. `ServletConfig`

4. `ServletContext`

5. `HttpServletRequest` & `HttpServletResponse`

6. `HttpSession`