MCA-223 Cloud Computing Notes from Unnati Educations cover all 4 units of this GGSIPU MCA Semester 3 elective in 106 pages, with 88 solved short-answer questions, 60 long-answer practice questions and 39 labelled figures. They follow the MCA syllabus that applies from academic session 2025-26 onwards and come as a printed book.
Written by Prateek Talwar, Founder, Unnati Educations · Reviewed by Ritik Rawat, B.Tech, Senior Full Stack Developer · Checked against the GGSIPU MCA Scheme of Examination and Detailed Syllabus (BoS 28/07/2025) · Updated 13 October 2026 · Editorial policy
Scheme: MCA (2 years), USIC&T scheme for affiliated institutes | Applies to: academic session 2025-26 onwards | Verified against: MCA Scheme of Examination and Detailed Syllabus, BoS 28/07/2025
MCA-223 Cloud Computing at a glance: GGSIPU MCA Sem 3 credits, units and exam pattern
MCA-223 is one of eleven Core Elective II options in the GGSIPU MCA Semester 3 papers.
| Code and title | MCA-223 Cloud Computing |
|---|---|
| Course and semester | MCA (2 years), Semester 3 |
| Category and credits | Core Elective II; 3 credits (L 3, T/P nil); 10 hours per unit |
| Marks | Out of 100; internal and end-term split not printed in the official PDF |
| End-term pattern | Compulsory Q1 (short or objective parts, whole syllabus) 12 marks, then one of two questions per unit at 12 marks each (12 + 48 = 60 marks) |
| Applies to | Academic session 2025-26 onwards |
| Units | 4 (the official PDF gives topics, not unit titles) |
| Paired lab | MCA-265 Lab based on Core Elective II (Cloud Computing Lab), L 0, T/P 2, 1 credit |
Examinations and results follow GGSIPU Ordinance 11.
MCA-223 Cloud Computing Notes unit-wise: 88 solved short-answer and 60 long-answer questions across 4 units
Each unit of these MCA-223 Cloud Computing IPU notes ends with 15 long-answer questions, 22 solved short answers and a revision table. Unit titles are the notes' own, as the official PDF numbers units only. Other MCA papers sit under GGSIPU MCA notes. The sample PDF in the header shows one page per unit.
MCA-223 Unit 1: Introduction to Cloud Computing and Cloud Computing Architecture
Unit 1 (pages 6 to 33, 8 sections, 10 figures) runs from the NIST definition and the evolution to AWS EC2 (2006) through the five characteristics, IaaS, PaaS and SaaS, and security configuration (CIA plus AAA). Then come architecture, the four deployment models, IDaaS and MapReduce.
| Phase | Output |
|---|---|
| Split | 3 splits, one line each |
| Map | (cloud,1) (data,1) (cloud,1) | (data,1) (map,1) (reduce,1) | (cloud,1) (map,1) |
| Shuffle and sort | (cloud,[1,1,1]) (data,[1,1]) (map,[1,1]) (reduce,[1]) |
| Reduce | (cloud,3) (data,2) (map,2) (reduce,1) |
Quick look: MapReduce word count on three short lines (from page 28)
- Phase
- Split
- Output
- 3 splits, one line each
- Phase
- Map
- Output
- (cloud,1) (data,1) (cloud,1) | (data,1) (map,1) (reduce,1) | (cloud,1) (map,1)
- Phase
- Shuffle and sort
- Output
- (cloud,[1,1,1]) (data,[1,1]) (map,[1,1]) (reduce,[1])
- Phase
- Reduce
- Output
- (cloud,3) (data,2) (map,2) (reduce,1)
MCA-223 Unit 2: Virtualization in Cloud and Security Issues in Cloud Computing
Unit 2 (pages 34 to 59, 12 sections, 17 figures) covers Popek-Goldberg requirements, the VM lifecycle, WINE and vCUDA middleware, full, para and hardware-assisted virtualisation, and live migration. The security half covers VM escape, hyperjacking, the CIA triad, privacy and trust.
| Basis | Virtual machine | Container |
|---|---|---|
| Virtualises | Hardware | Operating system |
| OS | Own full guest OS per VM | Shares the host OS kernel |
| Size and boot | Gigabytes, minutes | Megabytes, seconds |
| Isolation | Strong (hardware level) | Weaker (process level) |
Quick look: virtual machine vs container (from page 46)
- Basis
- Virtualises
- Virtual machine
- Hardware
- Container
- Operating system
- Basis
- OS
- Virtual machine
- Own full guest OS per VM
- Container
- Shares the host OS kernel
- Basis
- Size and boot
- Virtual machine
- Gigabytes, minutes
- Container
- Megabytes, seconds
- Basis
- Isolation
- Virtual machine
- Strong (hardware level)
- Container
- Weaker (process level)
MCA-223 Unit 3: Data Centre Architecture and Technologies and Computing with Titans
Unit 3 (pages 60 to 79, 5 sections, 5 figures) covers data centre components, PUE, building blocks up to PODs, and five phases from consolidation to market. Google, Microsoft, Amazon and IBM share one comparison table; then web APIs and browsers.
| Tier | Availability | Max downtime a year |
|---|---|---|
| Tier I, basic | 99.671% | about 28.8 hours |
| Tier II, redundant components | 99.741% | about 22 hours |
| Tier III, concurrently maintainable | 99.982% | about 1.6 hours |
| Tier IV, fault tolerant | 99.995% | about 26 minutes |
Quick look: Uptime Institute data centre tiers (from page 62)
- Tier
- Tier I, basic
- Availability
- 99.671%
- Max downtime a year
- about 28.8 hours
- Tier
- Tier II, redundant components
- Availability
- 99.741%
- Max downtime a year
- about 22 hours
- Tier
- Tier III, concurrently maintainable
- Availability
- 99.982%
- Max downtime a year
- about 1.6 hours
- Tier
- Tier IV, fault tolerant
- Availability
- 99.995%
- Max downtime a year
- about 26 minutes
MCA-223 Unit 4: Migrating to the Cloud and Implementation of Cloud using a Cloud Platform
Unit 4 (pages 80 to 106, 9 sections, 7 figures) covers the 6 R's, five migration phases, and services for individuals, mid-markets and enterprises. The hands-on half runs on Microsoft Azure: web services, Cloud Shell, Docker and AKS, a VNet, a VM and a load balancer.
Quick look: health probe and load-balancing rule in Azure CLI (from page 101)
az network lb probe create --resource-group UnnatiRG --lb-name UnnatiLB \
--name HealthProbe --protocol Tcp --port 80
az network lb rule create --resource-group UnnatiRG --lb-name UnnatiLB --name HTTPRule \
--protocol Tcp --frontend-port 80 --backend-port 80 \
--frontend-ip-name FrontEnd --backend-pool-name BackEndPool --probe-name HealthProbeThe probe checks port 80; the rule sends traffic only to healthy VMs, so replies alternate between WebVM1 and WebVM2.
Type 1 and Type 2 hypervisors in cloud virtualisation: excerpt from page 37 of the MCA-223 notes
Excerpt from page 37
How virtualisation is implemented
Virtualisation works by placing a software layer, the hypervisor or Virtual Machine Monitor (VMM), between the hardware and the operating systems. The hypervisor catches the requests that each guest OS makes and maps its virtual resources onto real CPU, memory, disk and network.
What a hypervisor is
A hypervisor is a software, firmware or hardware layer that creates and runs virtual machines. It gives each VM its share of CPU, memory, storage and network, schedules the VMs on the physical machine and keeps them isolated from one another.
Functions of a hypervisor
- Creating, starting, pausing, stopping and deleting VMs
- Allocating and scheduling CPU, memory and I/O to each VM
- Keeping VMs isolated from each other
- Handling privileged instructions of a guest OS through trap and emulate
- Supporting snapshots, cloning and live migration
- Monitoring how much each VM uses
Type 1: bare-metal or native hypervisor
A Type 1 hypervisor is installed straight onto the physical hardware with no host OS underneath. It behaves like a lightweight operating system with direct hardware access, which gives high performance and better security, so data centres and public clouds use it.
Examples are VMware ESXi, Microsoft Hyper-V, Xen (used by older AWS EC2), KVM (built into the Linux kernel and used by Google Cloud), the AWS Nitro hypervisor and Citrix XenServer. The stack, from the bottom: physical hardware, the Type 1 hypervisor, then VMs each carrying their own guest OS and apps.
Type 2: hosted hypervisor
A Type 2 hypervisor installs as an ordinary application on an existing host OS such as Windows, macOS or Linux. Every hardware request has to pass through that host OS, so it runs slower, but it is very easy to set up, which makes it the usual choice for desktops, testing and learning.
Examples are Oracle VirtualBox, VMware Workstation, VMware Fusion on Mac, Parallels Desktop and QEMU without KVM.
MCA-223 exam corner: 88 solved short-answer questions and 60 long-answer practice questions by unit
The notes label short answers "2.5 Marks" and long questions "12.5 marks level"; in the 2025-26 pattern every question carries 12 marks, so read those labels as a guide to length.
| Unit | Short-answer (2.5 Marks, solved) | Long-answer (12.5 marks level, practice) | Figures |
|---|---|---|---|
| Unit 1 | 22 | 15 | 10 |
| Unit 2 | 22 | 15 | 17 |
| Unit 3 | 22 | 15 | 5 |
| Unit 4 | 22 | 15 | 7 |
| Total | 88 | 60 | 39 |
MCA-223 questions in the notes, unit by unit
- Unit
- Unit 1
- Short-answer (2.5 Marks, solved)
- 22
- Long-answer (12.5 marks level, practice)
- 15
- Figures
- 10
- Unit
- Unit 2
- Short-answer (2.5 Marks, solved)
- 22
- Long-answer (12.5 marks level, practice)
- 15
- Figures
- 17
- Unit
- Unit 3
- Short-answer (2.5 Marks, solved)
- 22
- Long-answer (12.5 marks level, practice)
- 15
- Figures
- 5
- Unit
- Unit 4
- Short-answer (2.5 Marks, solved)
- 22
- Long-answer (12.5 marks level, practice)
- 15
- Figures
- 7
- Unit
- Total
- Short-answer (2.5 Marks, solved)
- 88
- Long-answer (12.5 marks level, practice)
- 60
- Figures
- 39
The MCA-223 notes solve 88 short-answer questions across 4 units, plus 60 long-answer practice questions.
One question per unit, with answer pointers:
- Unit 1: What is cloud bursting? Pointer (page 31): a private-cloud app spills into a public cloud when demand passes private capacity.
- Unit 2: What is VM escape? Pointer (page 58): code in a guest VM breaks isolation and reaches the hypervisor or other VMs.
- Unit 3: Differentiate region and availability zone. Pointer (page 78): a region is a geographic area such as AWS Mumbai; a zone is an isolated data centre inside it.
- Unit 4: What is "lift and shift"? Pointer (page 103): rehosting an app on cloud VMs without code changes: fastest, but it skips cloud-native benefits.
More practice sits in the MCA-223 important questions.
Who writes and checks the MCA-223 Cloud notes?
- Prateek Talwar, author and editor: Founder, Unnati Educations; Associate Company Secretary (ACS), ICSI, membership no. 58704, since 15 May 2019; B.Com, University of Delhi (School of Open Learning), 2012. Author profile
- Ritik Rawat, subject-expert reviewer, including the Azure CLI walkthroughs in Unit 4: Senior Full Stack Developer, Unnati Educations; B.Tech.
The 2026-27 edition of these GGSIPU MCA Sem 3 Cloud Computing notes is mapped to the MCA scheme for 2025-26 onwards: 4 units, 34 sections, 39 figures. Last updated 13 October 2026, under our editorial policy.
The same team prepares GGSIPU important questions, unit-wise like these cloud questions.
Do the MCA-223 notes cover the full GGSIPU syllabus?
Yes. Every topic in the four official MCA-223 units, from IDaaS to load balancing, has a matching section.
| Official unit | Official topics | Where in the notes | Status |
|---|---|---|---|
| I | Introduction: definition, evolution, service models, issues, applications, security configurations | Sections 1 to 4, pages 7 to 20 | Covered |
| I | Architecture: deployment models, IDaaS, MapReduce | Sections 5 to 8, pages 21 to 29 | Covered |
| II | Virtualization in Cloud: implementation, middleware, techniques, types | Sections 1 to 7, pages 35 to 50 | Covered |
| II | Security Issues: challenges, information security, privacy and trust | Sections 8 to 12, pages 51 to 56 | Covered |
| III | Data Centre Architecture: building blocks, industry direction, 5 phases | Sections 1 to 3, pages 61 to 67 | Covered |
| III | Computing with Titans; accessing the cloud | Sections 4 and 5, pages 68 to 76 | Covered |
| IV | Migrating to the Cloud: individuals, mid-markets, enterprise, best practices, future | Sections 1 to 3, pages 81 to 87 | Covered |
| IV | Implementation on any cloud platform (Azure in the notes): web services to load balancing | Sections 4 to 9, pages 88 to 102 | Covered |
MCA-223 official syllabus mapped to the notes
- Official unit
- I
- Official topics
- Introduction: definition, evolution, service models, issues, applications, security configurations
- Where in the notes
- Sections 1 to 4, pages 7 to 20
- Status
- Covered
- Official unit
- I
- Official topics
- Architecture: deployment models, IDaaS, MapReduce
- Where in the notes
- Sections 5 to 8, pages 21 to 29
- Status
- Covered
- Official unit
- II
- Official topics
- Virtualization in Cloud: implementation, middleware, techniques, types
- Where in the notes
- Sections 1 to 7, pages 35 to 50
- Status
- Covered
- Official unit
- II
- Official topics
- Security Issues: challenges, information security, privacy and trust
- Where in the notes
- Sections 8 to 12, pages 51 to 56
- Status
- Covered
- Official unit
- III
- Official topics
- Data Centre Architecture: building blocks, industry direction, 5 phases
- Where in the notes
- Sections 1 to 3, pages 61 to 67
- Status
- Covered
- Official unit
- III
- Official topics
- Computing with Titans; accessing the cloud
- Where in the notes
- Sections 4 and 5, pages 68 to 76
- Status
- Covered
- Official unit
- IV
- Official topics
- Migrating to the Cloud: individuals, mid-markets, enterprise, best practices, future
- Where in the notes
- Sections 1 to 3, pages 81 to 87
- Status
- Covered
- Official unit
- IV
- Official topics
- Implementation on any cloud platform (Azure in the notes): web services to load balancing
- Where in the notes
- Sections 4 to 9, pages 88 to 102
- Status
- Covered
Official source: GGSIPU MCA Scheme of Examination and Detailed Syllabus (2025-26 onwards).
Every course in GGSIPU notes is mapped to its official PDF the same way.
How to write MCA-223 answers: comparison tables, labelled cloud diagrams and Azure CLI steps
MCA-223 rewards structure more than length. The notes give a figure or table for most long topics, and the long-answer lists ask you to practise the diagrams, tables and commands. Build each 12-mark answer as definition, then diagram or table, then explanation, then one real example.
Comparisons as tables
For IaaS vs PaaS vs SaaS, the notes tell you to draw the "who manages what" table on page 15: nine layers from networking up to applications, with "You" or "Provider" under each model. The four deployment models get the same treatment on page 25.
Lists you can recall
For issues and challenges, the notes use the short form S-A-V-I-C-P-C: Security, Availability, Vendor lock-in, Interoperability, Compliance, Performance, Cost (page 17).
Security configuration
The tip on page 20 asks you to cover the shared responsibility model, IAM, network controls (VPC, security groups), encryption, logging and backup, naming one real tool for each point.
Unit IV commands
Write portal steps as a numbered list and add the matching az command under each, such as az network lb probe create for the health probe. Examiners can follow a numbered list faster than a paragraph.
Worked example: "Which deployment model would you suggest for a bank? Justify."
- Answer with hybrid cloud (page 25): core banking and customer data stay on the private part for security and compliance, while the mobile app front end runs on a public cloud.
- Add a short comparison with public and private, and a two-box diagram joined by a VPN.
- Close with one risk, such as integration across two environments, and how the bank handles it.
The same frame works for a hospital group (community) or a start-up (public).
Practise this answer format on GGSIPU MCA important questions.
MCA-223 and the GGSIPU MCA Sem 3 papers it connects to
Paired lab: MCA-265 Cloud Computing Lab (1 credit), listed in the GGSIPU MCA syllabus; its lab notes are not part of this book. Lab topics map to the theory:
- Virtual cloud platform, storage account and load balancing: Unit IV, pages 90 to 102.
- Security, privacy and trust: Unit II, sections 8 to 12.
- Virtualisation through IaaS: Units I and II.
Core papers alongside it: MCA-201 and MCA-203. MCA-227 Web Intelligence and Big Data builds on the MapReduce part of Unit 1. Pre-requisites: MCA-103 Computer Networks and MCA-105 Operating Systems with Linux.
MCA-223 Cloud notes FAQs
How do I get the full MCA-223 notes?
Message us on WhatsApp at 9899436384 using the "Get Full Notes" button. The full MCA-223 notes are sold only as a printed book of 106 pages; they are not available as a PDF. Delivery takes 5 to 7 days at most, depending on your location. The View Sample PDF button in the header shows seven watermarked pages first.
Is MCA-223 a compulsory paper in GGSIPU MCA Semester 3?
No. MCA-223 is one of eleven Core Elective II options, and you choose one. The scheme says an elective needs at least 20 students for classes; with fewer, it may still be offered, but students complete it through an approved MOOC and still sit the institute's evaluation. Ask your institute which Core Elective II papers it runs this year.
What is the passing mark for MCA-223?
MCA-223 is marked out of 100, and the end-term paper set under the instructions totals 60 marks; the internal and end-term split is not printed in the official PDF. The MCA scheme of examination states pass marks as 40 out of 100 for every paper, which is 40%. For end-term minimums and re-appear rules, see GGSIPU Ordinance 11 on ipu.ac.in.
How is the MCA-223 end-term paper set?
Question 1 is compulsory, covers the whole MCA-223 syllabus with objective or short-answer parts, and carries 12 marks. Each of the 4 units then has two questions; you attempt one per unit, and each carries 12 marks including sub-parts. That adds up to 12 + 48 = 60 marks. Examiners also map every question to the four course outcomes.
Which MCA-223 unit has the most diagrams?
Unit 2, Virtualization in Cloud and Security Issues, has 17 of the 39 figures in the MCA-223 notes. They include Type 1 and Type 2 hypervisor stacks, five levels of virtualisation, x86 privilege rings, binary translation, hypercalls, two-stage memory mapping and pre-copy live migration. Unit 1 follows with 10 figures, mostly architecture, deployment and MapReduce flows.
Are the MCA-223 notes enough for the MCA-265 Cloud Computing Lab?
They cover the theory behind it, but they are not lab notes. MCA-265 has its own objectives: a virtual cloud platform, load balancing, security, a storage account and virtualisation through IaaS. Unit 4 of the MCA-223 notes explains the Azure portal and CLI steps behind most of these, so use it alongside your institute's lab list and your own practical work.
Get the full MCA-223 Cloud Computing Notes on WhatsApp
What the full MCA-223 notes book contains
- Part
- Cover and index
- Pages
- 1 to 5 (5)
- Sections
- -
- Short answers
- -
- Long questions
- -
- Part
- Unit 1
- Pages
- 6 to 33 (28)
- Sections
- 8
- Short answers
- 22
- Long questions
- 15
- Part
- Unit 2
- Pages
- 34 to 59 (26)
- Sections
- 12
- Short answers
- 22
- Long questions
- 15
- Part
- Unit 3
- Pages
- 60 to 79 (20)
- Sections
- 5
- Short answers
- 22
- Long questions
- 15
- Part
- Unit 4
- Pages
- 80 to 106 (27)
- Sections
- 9
- Short answers
- 22
- Long questions
- 15
Format: printed book only, 106 pages of Cloud Computing notes in English; not available as a PDF. Delivery: within 5 to 7 days at most; the exact time may vary with your location.
Unnati Educations is an independent education provider based in Vikaspuri, Delhi. We are not affiliated with, authorised by, or endorsed by Guru Gobind Singh Indraprastha University (GGSIPU). 'GGSIPU' and 'IPU' are used only to describe the syllabus our notes follow. For official information, visit ipu.ac.in.
Ready for the full notes?
Discuss coverage and delivery with our team.