AKTU MBA 3rd Sem Database Management System PYQs

Database Management System is an important Information Technology specialization subject in AKTU MBA 3rd Semester. The subject focuses on how data is stored, organised, managed, retrieved, secured, and used efficiently through database systems.

Practicing AKTU MBA 3rd Sem Database Management System PYQs helps students understand how database concepts, relational models, keys, normalization, SQL, transactions, concurrency, security, and database design topics are framed in university examinations. Since the subject combines conceptual understanding with practical database logic, previous-year papers are useful for improving both theory and application-based preparation.

Students can explore AKTU MBA previous-year question papers and related academic resources on NotesGallery. For official university notices, examination announcements, academic circulars, and authoritative information, students should refer to the AKTU Official Website.

AKTU MBA 3rd Semester Subject Details

The subject details are:

Subject Code	Subject Name	Specialization
BMB IT 03	Database Management System	Information Technology

Database Management System is part of the Information Technology specialization in MBA Semester 3.

The other Information Technology specialization subjects shown alongside it are:

Code	Subject
BMB IT 01	Software Engineering and Management
BMB IT 02	Emerging Technologies for Business

MBA 3rd Semester also includes the core subject Strategic Management (BMB301) along with specialization electives from Marketing, Human Resource Management, Financial Management, Operation Management, International Business, and Cooperative Management.

About Database Management System

A Database Management System (DBMS) is software used to create, store, organise, retrieve, update, and manage data in a structured manner.

Examples of data that organisations may store include:

• customer details
• employee records
• sales transactions
• inventory information
• financial records
• student records
• supplier information

A DBMS helps organisations manage large amounts of data more efficiently than simple files.

Meaning of Database

A database is an organised collection of related data.

For example, a company database may contain information about:

• customers
• products
• orders
• employees
• payments

The purpose of a database is to store information in a way that makes it easy to access, update, and analyse.

Meaning of DBMS

A Database Management System is software that acts as an interface between users, applications, and stored data.

A simple representation is:

User/Application → DBMS → Database

The DBMS controls how data is:

• stored
• accessed
• modified
• protected

Need for DBMS

Organisations use DBMS because traditional file systems can create problems such as:

• duplicate data
• inconsistent data
• difficulty in searching
• weak security
• poor data sharing
• lack of backup control

A DBMS provides a more structured approach.

Advantages of DBMS

Important advantages may include:

• reduced data redundancy
• improved consistency
• better security
• easier data sharing
• improved data integrity
• backup and recovery
• centralised management
• faster retrieval

Limitations of DBMS

Possible limitations may include:

• implementation cost
• software complexity
• need for skilled personnel
• hardware requirements
• maintenance cost

Despite these limitations, DBMS is essential for many modern organisations.

File System vs DBMS

File System	DBMS
Data stored in separate files	Data managed through database software
More duplication possible	Better control of redundancy
Limited data sharing	Easier data sharing
Security may be difficult to manage	Better access control
Weak consistency control	Better integrity mechanisms
Limited query capability	Powerful query support

Components of DBMS

A DBMS environment may include:

• hardware
• software
• data
• procedures
• users

All these components work together to manage information.

Hardware

Hardware may include:

• servers
• storage devices
• computers
• networks

The database software operates on this physical infrastructure.

Software

Software includes:

• DBMS software
• operating system
• application software
• database utilities

Data

Data is the most important resource managed by the DBMS.

Examples include:

• names
• numbers
• transactions
• dates
• product information

Procedures

Procedures define how databases are:

• used
• maintained
• backed up
• secured

Database Users

Database users may include:

• database administrators
• developers
• managers
• employees
• customers

Different users may have different access rights.

Database Administrator

A Database Administrator (DBA) is responsible for managing the database system.

Responsibilities may include:

• database installation
• access control
• backup
• recovery
• performance monitoring
• security
• maintenance

Database Developer

A database developer may:

• design tables
• write queries
• create procedures
• develop database applications

End User

An end user interacts with the database through applications or interfaces.

Examples include:

• employee using an HR system
• customer checking order status
• manager viewing reports

Data Model

A Data Model defines how data is structured and related.

Common models may include:

• hierarchical model
• network model
• relational model

The relational model is widely used in modern business applications.

Hierarchical Model

The hierarchical model organises data in a tree-like structure.

Each child record is generally linked to a parent.

It may be useful where relationships naturally follow a hierarchy.

Network Model

The network model allows records to have multiple relationships.

It provides more flexibility than a strictly hierarchical structure.

Relational Model

The Relational Model stores data in tables.

Each table consists of:

• rows
• columns

Tables can be connected through keys.

This model is commonly used because it is simple and flexible.

Table

A table stores data about an entity or subject.

For example, a Customer table may contain:

Customer_ID	Name	City
101	Rahul	Delhi
102	Priya	Lucknow

Each row represents a record.

Each column represents an attribute.

Row

A row represents one record in a table.

For example, one customer’s complete information forms one row.

Column

A column represents one attribute.

Examples may include:

• customer name
• city
• phone number

Entity

An Entity is a real-world object or concept about which data is stored.

Examples include:

• customer
• employee
• product
• order

Attribute

An attribute describes an entity.

For an Employee entity, attributes may include:

• Employee_ID
• Name
• Department
• Salary

Relationship

A relationship connects entities.

For example:

• Customer places Order
• Employee works in Department
• Supplier provides Product

Entity Relationship Model

The Entity Relationship Model helps represent entities, attributes, and relationships before creating database tables.

It is commonly represented through an ER Diagram.

ER Diagram

An ER Diagram visually represents:

• entities
• attributes
• relationships

It helps database designers understand the structure of information.

Types of Relationships

Common relationship types include:

• one-to-one
• one-to-many
• many-to-many

One-to-One Relationship

In a one-to-one relationship, one record is associated with one other record.

One-to-Many Relationship

In a one-to-many relationship, one record can be associated with several records.

Example:

One Customer → Many Orders

Many-to-Many Relationship

In a many-to-many relationship, multiple records can be associated with multiple records.

Example:

Students ↔ Courses

This relationship is often implemented using an intermediate table.

Keys in DBMS

Keys are attributes used to identify records and establish relationships.

Important types may include:

• Primary Key
• Foreign Key
• Candidate Key
• Composite Key

Primary Key

A Primary Key uniquely identifies each record in a table.

Example:

Customer_ID

A primary key should be unique and should not identify multiple rows with the same value.

Foreign Key

A Foreign Key is an attribute that creates a relationship with another table.

For example:

An Order table may include Customer_ID as a foreign key referring to the Customer table.

Primary Key vs Foreign Key

Primary Key	Foreign Key
Uniquely identifies a row	Connects tables
Defined in its own table	Refers to key in another table
Values are unique	Values may repeat
Supports entity identification	Supports relationships

Candidate Key

A Candidate Key is an attribute or combination of attributes capable of uniquely identifying a record.

One candidate key may be selected as the primary key.

Composite Key

A Composite Key uses more than one attribute together to uniquely identify a record.

It can be useful in relationship tables.

Data Redundancy

Data redundancy means storing the same information unnecessarily in multiple places.

Excessive redundancy may cause:

• wasted storage
• inconsistency
• update problems

DBMS design attempts to reduce unnecessary duplication.

Data Integrity

Data Integrity means maintaining accuracy and consistency of data.

Integrity may be supported through:

• keys
• validation rules
• constraints
• controlled access

Data Consistency

Data consistency means the same information remains logically correct across the database.

For example, customer details should not contain conflicting values in different places.

Database Constraints

Constraints are rules that control what data can be entered.

They may help enforce:

• uniqueness
• valid references
• required values
• acceptable ranges

Normalization

Normalization is a database-design process used to organise data and reduce unnecessary redundancy.

Its objectives include:

• reducing duplication
• preventing update problems
• improving consistency
• creating efficient table structures

Need for Normalization

Without normalization, databases may suffer from:

• insertion anomaly
• update anomaly
• deletion anomaly

Normalization helps reduce these problems.

Insertion Anomaly

An insertion anomaly occurs when certain data cannot be added without adding unrelated information.

Update Anomaly

An update anomaly occurs when the same information must be changed in multiple places.

If one copy is not updated, inconsistency may occur.

Deletion Anomaly

A deletion anomaly occurs when deleting one record unintentionally removes other important information.

First Normal Form

First Normal Form (1NF) generally requires that table values be atomic and repeating groups be removed.

Each field should contain a single logical value.

Second Normal Form

Second Normal Form (2NF) generally requires:

• table is already in 1NF
• non-key attributes should depend on the whole relevant key

It helps remove certain partial dependencies.

Third Normal Form

Third Normal Form (3NF) generally requires:

• table is already in 2NF
• non-key attributes should not depend indirectly on other non-key attributes

The objective is better data organisation.

Benefits of Normalization

Normalization can provide:

• reduced redundancy
• improved integrity
• easier updates
• cleaner database design

However, highly complex normalization may sometimes increase the number of table joins required.

Denormalization

Denormalization involves intentionally combining or duplicating some data to improve performance in suitable situations.

It may be useful when:

• faster reading is important
• reporting requires many joins

Denormalization should be used carefully.

Structured Query Language

Structured Query Language (SQL) is used to communicate with relational databases.

SQL may be used to:

• create tables
• insert data
• retrieve data
• update data
• delete data
• manage permissions

Categories of SQL Commands

Broad SQL categories may include:

• DDL
• DML
• DCL
• TCL

Data Definition Language

Data Definition Language (DDL) is used to define database structures.

Typical operations may include:

• CREATE
• ALTER
• DROP

Data Manipulation Language

Data Manipulation Language (DML) is used to work with data.

Typical operations may include:

• INSERT
• UPDATE
• DELETE

Data Query Operations

SQL is also used to retrieve data through queries, commonly using statements such as SELECT.

Queries can filter, sort, combine, and summarise information.

Data Control Language

Data Control Language (DCL) is associated with database permissions and access control.

It helps manage who can perform certain operations.

Transaction Control Language

Transaction Control Language (TCL) is used to control transactions.

It may involve operations such as:

• COMMIT
• ROLLBACK

SQL Query

A SQL query requests information from a database.

For example, a query may be used to:

• display all customers
• find products above a certain price
• calculate total sales
• sort employees by salary

SELECT Statement

SELECT is commonly used to retrieve data.

Conceptually:

SELECT required data FROM table

Additional conditions may be used for filtering.

WHERE Clause

The WHERE clause filters rows according to a condition.

For example, a business may retrieve only customers from a particular city.

ORDER BY

ORDER BY is used to sort query results.

Sorting may be:

• ascending
• descending

GROUP BY

GROUP BY is used to organise rows into groups for summary analysis.

It can be useful for:

• total sales by city
• number of customers by region
• average salary by department

Aggregate Functions

Aggregate functions summarise multiple values.

Common examples include:

• COUNT
• SUM
• AVG
• MIN
• MAX

Join

A Join combines data from related tables.

For example:

Customer table + Order table

can be joined to determine which customer placed each order.

Types of Joins

Common joins may include:

• Inner Join
• Left Join
• Right Join

Students should understand the broad purpose of each.

Inner Join

An Inner Join returns records with matching values in the related tables.

Left Join

A Left Join generally returns all records from the left table and matching records from the right table.

View

A View is a virtual representation of data based on a query.

Views can:

• simplify complex queries
• restrict data access
• present selected information

Index

An Index helps improve the speed of data retrieval.

It works conceptually like an index in a book.

However, indexes also require storage and can affect update performance.

Database Transaction

A Transaction is a logical unit of database work.

Examples may include:

• bank transfer
• placing an order
• recording a payment

A transaction may involve several database operations that should be treated as one unit.

ACID Properties

Database transactions are commonly associated with ACID properties:

• Atomicity
• Consistency
• Isolation
• Durability

Atomicity

Atomicity means a transaction should be completed fully or not completed at all.

For example, in a money transfer, one account should not be debited without the corresponding credit operation completing correctly.

Consistency

Consistency means a transaction should move the database from one valid state to another valid state.

Isolation

Isolation means simultaneous transactions should not interfere with each other in a way that creates incorrect results.

Durability

Durability means committed transaction results should remain stored even after a system failure.

Importance of ACID Properties

ACID properties are important for:

• banking
• payments
• inventory
• financial records

They help maintain reliable transaction processing.

Concurrency Control

Concurrency Control manages simultaneous access to database data.

Multiple users may attempt to:

• read
• update
• delete

the same information at the same time.

Concurrency control helps maintain consistency.

Concurrency Problems

Without proper control, problems may include:

• lost updates
• inconsistent reads
• incorrect transaction results

Locking

Locking is one method used to control concurrent access.

A transaction may temporarily restrict other transactions from changing certain data.

Deadlock

A Deadlock can occur when transactions wait for each other indefinitely.

For example:

• Transaction A waits for a resource held by B
• Transaction B waits for a resource held by A

Database systems use techniques to detect or prevent deadlocks.

Database Recovery

Database recovery restores the database after problems such as:

• system failure
• software failure
• power failure
• transaction failure

Recovery mechanisms help protect business data.

Backup

A Backup is a copy of database data kept for recovery purposes.

Backups may be:

• full
• incremental
• differential

depending on the database strategy.

Full Backup

A full backup contains a complete copy of selected database data.

It can simplify restoration but may require more storage and time.

Incremental Backup

An incremental backup generally stores changes made since the previous backup.

It can reduce backup size.

Differential Backup

A differential backup generally stores changes made since the last full backup.

Backup vs Recovery

Backup	Recovery
Creates copies of data	Restores data after failure
Preventive preparation	Used after a problem occurs
Supports disaster readiness	Supports return to normal operation

Database Security

Database security protects data against:

• unauthorised access
• modification
• disclosure
• destruction

Security is critical because databases often contain sensitive business information.

Authentication

Authentication verifies the identity of a user.

Examples may include:

• passwords
• multi-factor authentication

Authorization

Authorization determines what an authenticated user is allowed to do.

For example:

• read data
• update data
• delete data

Authentication vs Authorization

Authentication	Authorization
Verifies identity	Determines permissions
Asks “Who are you?”	Asks “What can you access?”
Happens before permission checks	Happens after identity is established

Access Control

Access control limits database access according to user roles and responsibilities.

For example:

• employee may view limited records
• manager may view reports
• administrator may manage database settings

Role-Based Access Control

Role-Based Access Control assigns permissions based on roles.

Examples may include:

• administrator
• manager
• analyst
• employee

This simplifies permission management.

Encryption

Encryption converts readable data into protected form.

It may be used for:

• stored data
• transmitted data

Encryption helps reduce exposure if data is accessed without permission.

Database Audit

A database audit records or reviews database activity.

It may help identify:

• unauthorised access
• suspicious changes
• policy violations

Data Privacy

Database systems often store personal information.

Organisations should manage data responsibly by considering:

• access
• retention
• consent
• security
• authorised use

Database Design

Database design involves planning the structure of data before implementation.

A general process may include:

1. Identify requirements
2. Identify entities
3. Identify attributes
4. Define relationships
5. Choose keys
6. Normalize tables
7. Implement database

Good database design reduces future problems.

Conceptual Database Design

Conceptual design focuses on the overall structure of data without considering detailed implementation.

ER modelling is commonly used at this stage.

Logical Database Design

Logical design converts conceptual models into structures suitable for a database model.

For relational databases, this may involve:

• tables
• keys
• relationships

Physical Database Design

Physical design focuses on how data is actually stored and accessed.

It may involve:

• indexes
• storage
• performance considerations

Schema

A Database Schema defines the logical structure of the database.

It may specify:

• tables
• fields
• relationships
• constraints

Metadata

Metadata is data that describes other data.

For example, metadata may describe:

• field name
• data type
• size
• relationship

Data Dictionary

A Data Dictionary stores information about database elements.

It may contain:

• table names
• column names
• data types
• constraints

It helps administrators and developers understand database structure.

Centralized Database

A centralized database stores and manages data primarily from one central location.

Potential advantages include:

• easier control
• simpler administration
• consistent data

Possible limitations include dependence on the central system.

Distributed Database

A Distributed Database stores data across multiple locations while operating as part of an integrated system.

Potential benefits may include:

• local availability
• scalability
• resilience

Challenges may include:

• coordination
• consistency
• network dependency

Centralized vs Distributed Database

Centralized Database	Distributed Database
Data mainly controlled from one location	Data stored across multiple locations
Easier administration	Greater coordination complexity
Central failure can create major impact	Can provide better local availability
Simpler consistency management	Requires distributed consistency mechanisms

Relational Database Management System

An RDBMS is a DBMS based on the relational model.

It stores data in connected tables.

Important features may include:

• tables
• keys
• SQL
• constraints
• relationships

DBMS vs RDBMS

DBMS	RDBMS
General database-management concept	DBMS based on relational model
May use different data models	Primarily uses tables
Relationship support depends on model	Strong relationship support through keys

NoSQL Databases

NoSQL refers broadly to database approaches designed for data structures that may not fit traditional relational models.

They may support:

• large-scale data
• flexible schemas
• distributed systems

Common categories may include:

• document databases
• key-value databases
• graph databases
• column-oriented databases

SQL vs NoSQL

SQL Databases	NoSQL Databases
Usually relational	Often non-relational
Structured tables	Flexible data structures
Commonly use SQL	Query methods may differ
Strong schema structure	May support flexible schemas

The appropriate choice depends on application requirements.

Data Warehouse

A Data Warehouse stores integrated historical data for reporting and analysis.

It is commonly used for:

• management reporting
• business intelligence
• trend analysis
• decision-making

Operational Database vs Data Warehouse

Operational Database	Data Warehouse
Supports daily transactions	Supports analysis and reporting
Frequently updated	Often stores historical data
Optimised for operational work	Optimised for analytical queries

Data Mart

A Data Mart is a smaller analytical data store focused on a particular business area.

Examples may include:

• sales data mart
• finance data mart
• marketing data mart

Data Mining

Data Mining refers to discovering useful patterns and relationships from large datasets.

It may support:

• customer segmentation
• fraud detection
• sales analysis
• forecasting

Database and Business Intelligence

Databases provide the underlying data needed for Business Intelligence.

A common flow may be:

Business Data → Database → Analysis → Dashboard → Managerial Decision

Without reliable data, business intelligence may produce poor conclusions.

Database and Customer Relationship Management

CRM systems depend on databases to store:

• customer profiles
• interactions
• purchases
• support history

This helps organisations improve customer service and marketing.

Database and Enterprise Resource Planning

ERP systems rely heavily on integrated databases.

They may connect data from:

• finance
• HR
• inventory
• purchasing
• sales

A shared database can reduce duplication across departments.

Database and E-Commerce

E-commerce platforms may use databases for:

• customer accounts
• product catalogues
• orders
• payments
• inventory

Database performance directly affects customer experience.

Database and Banking

Banking systems rely on databases for:

• accounts
• balances
• transactions
• loans
• customer details

Transaction accuracy and security are especially important.

Database and Human Resource Management

HR databases may contain:

• employee details
• payroll
• attendance
• performance
• recruitment information

Database and Supply Chain Management

Supply-chain databases may store:

• supplier data
• inventory
• orders
• shipment details
• warehouse information

Accurate data helps improve planning and coordination.

Cloud Databases

A Cloud Database is hosted or managed using cloud infrastructure.

Potential advantages may include:

• scalability
• remote access
• flexible capacity
• managed services

Challenges may include:

• security
• compliance
• vendor dependence
• connectivity

Database as a Service

Database as a Service provides database capabilities through a managed cloud service.

The provider may manage:

• infrastructure
• maintenance
• backup
• updates

This can reduce administrative effort.

Big Data and Database Management

Traditional databases may not always be sufficient for extremely large or complex datasets.

Big-data environments may use:

• distributed storage
• NoSQL systems
• specialised analytics platforms

Managers should understand that database technology depends on business requirements.

Data Governance

Data Governance defines responsibilities and policies for managing organisational data.

It may include:

• ownership
• quality
• security
• access
• compliance

Good governance improves trust in business data.

Data Quality

High-quality data should generally be:

• accurate
• complete
• consistent
• timely
• relevant

Poor data quality can lead to poor business decisions.

Master Data Management

Master Data Management focuses on maintaining consistent core business information.

Examples may include:

• customer master
• product master
• supplier master

It helps reduce duplicate or conflicting records.

Database Performance

Database performance refers to how efficiently a database handles:

• queries
• updates
• transactions
• concurrent users

Performance may be influenced by:

• indexing
• hardware
• database design
• query structure

Database Scalability

Scalability is the ability of a database system to handle growing amounts of:

• data
• users
• transactions

Scalability is important for growing digital businesses.

Database Availability

Availability refers to whether the database remains accessible when users need it.

High availability is important for:

• banking
• e-commerce
• online services

Database Reliability

Reliability refers to the ability of a database system to operate correctly and preserve data.

Backup, recovery, replication, and monitoring may support reliability.

Database Replication

Replication involves maintaining copies of data across multiple systems or locations.

Potential benefits may include:

• availability
• disaster recovery
• read performance

However, replication requires careful consistency management.

Database Migration

Database migration involves moving data from one database environment to another.

It may occur because of:

• technology change
• cloud adoption
• system replacement
• business expansion

Migration requires careful planning to avoid data loss.

Database Integration

Database integration connects data from multiple systems.

It can support:

• central reporting
• better decision-making
• reduced duplication

Integration can be challenging when systems use different formats.

Data Security Risks

Database security risks may include:

• stolen credentials
• unauthorised access
• malware
• weak permissions
• data leakage

Security requires both technical and managerial controls.

Database Management and Business Decision-Making

Databases provide the information foundation for managerial decisions.

Managers may use database information to analyse:

• sales
• customers
• employees
• operations
• finance

Reliable data improves decision quality.

Relationship With Software Engineering And Management

Database Management System connects directly with Software Engineering And Management (BMB IT 01).

Most software applications require databases to:

• store information
• retrieve records
• process transactions
• generate reports

Database design therefore forms an important part of software-system design.

Relationship With Emerging Technologies For Business

It also connects with Emerging Technologies For Business (BMB IT 02).

Technologies such as:

• Artificial Intelligence
• Big Data
• Cloud Computing
• Internet of Things
• Business Analytics

depend heavily on reliable and well-managed data.

DBMS therefore provides an important foundation for many emerging technologies.

Relationship With Strategic Management

The core subject Strategic Management (BMB301) connects with database management because data can support:

• strategic planning
• customer analysis
• performance measurement
• market analysis
• decision-making

Organisations with better data management may make more informed strategic decisions.

Why Solve AKTU MBA Database Management System PYQs?

Understand the Examination Pattern

Previous-year papers can help students identify whether topics are asked as:

• definitions
• short notes
• database-design questions
• ER-model questions
• normalization questions
• SQL concepts
• transaction questions
• security questions

Improve Conceptual Clarity

Important distinctions include:

• DBMS vs File System
• Primary Key vs Foreign Key
• SQL vs NoSQL
• Authentication vs Authorization
• Backup vs Recovery

Improve Database Design Understanding

Students should practice:

• identifying entities
• choosing attributes
• establishing relationships
• identifying keys
• normalization

Improve Application-Based Thinking

Students should connect DBMS concepts with real systems such as:

• banking
• e-commerce
• HR
• CRM
• ERP

Important Topics for Exam Preparation

While practicing AKTU MBA 3rd Sem Database Management System PYQs, students should pay particular attention to:

• database
• DBMS
• advantages of DBMS
• File System vs DBMS
• database users
• DBA
• data models
• relational model
• entities and attributes
• relationships
• ER Diagram
• Primary Key
• Foreign Key
• Candidate Key
• Composite Key
• data redundancy
• data integrity
• normalization
• 1NF
• 2NF
• 3NF
• insertion anomaly
• update anomaly
• deletion anomaly
• SQL
• DDL
• DML
• DCL
• TCL
• queries
• joins
• views
• indexes
• transactions
• ACID properties
• concurrency control
• locking
• deadlock
• backup and recovery
• database security
• authentication
• authorization
• database design
• schema
• data dictionary
• distributed database
• RDBMS
• NoSQL
• data warehouse
• data mining
• cloud databases
• data governance
• data quality

Students should still prepare the complete prescribed syllabus rather than relying only on repeated PYQ topics.

How to Practice Database Management System PYQs

Step 1: Understand Basic Database Concepts

Start with:

• database
• DBMS
• table
• row
• column
• keys

Step 2: Learn ER Modelling

Practice identifying:

• entities
• attributes
• relationships

Step 3: Practice Normalization

Understand why normalization is performed rather than only memorising definitions.

Step 4: Learn SQL Concepts

Prepare:

• DDL
• DML
• queries
• joins
• aggregate functions

Step 5: Study Transactions

Understand:

• ACID
• concurrency
• locking
• deadlock

Step 6: Prepare Comparison Tables

Prepare common comparisons such as:

• DBMS vs File System
• Primary Key vs Foreign Key
• DBMS vs RDBMS
• SQL vs NoSQL
• Backup vs Recovery

Step 7: Attempt Related PYQs

Write answers without referring to notes.

Step 8: Solve a Complete Paper

After syllabus revision, attempt a full previous-year paper within a fixed time.

This improves:

• recall
• database terminology
• design understanding
• answer structure
• time management

Quick Revision Strategy

For final revision, divide the subject into four broad areas.

Database Fundamentals

Revise:

• DBMS
• database models
• relational model
• entities
• attributes
• relationships
• keys

Database Design

Revise:

• ER Diagram
• normalization
• 1NF
• 2NF
• 3NF
• anomalies
• schema

SQL and Transactions

Revise:

• SQL
• DDL
• DML
• joins
• views
• indexes
• transactions
• ACID
• concurrency

Security and Modern Database Concepts

Revise:

• authentication
• authorization
• backup
• recovery
• distributed databases
• NoSQL
• data warehouses
• cloud databases
• data governance

After revision, attempt selected PYQs without referring to your notes.

Useful Resources for AKTU MBA Students

Students can explore AKTU MBA previous-year question papers, notes, and related academic resources through NotesGallery.

For official university notices, examination announcements, academic circulars, and authoritative information, students should refer to the AKTU Official Website.

NotesGallery is an independent educational resource platform and should not be considered the official website of Dr. A.P.J. Abdul Kalam Technical University.

Related MBA Third Semester Study Materials

MBA 3rd Semester All Subject PYQs
→


MBA 3rd Semester All Subject Notes
→


MBA 3rd Semester All Subject Syllabus
→

Frequently Asked Questions