{"pinia":{"ui":{"prefs":{"theme":"system","textScale":"md","fontFamily":"sans","reducedMotion":false,"highContrast":false}},"academy":{"universities":[],"universitySummaries":[{"slug":"rtu","name":"RTU","fullName":"Rajasthan Technical University","branches":[{"slug":"first-year-common","name":"First Year (Common)"},{"slug":"computer-science","name":"Computer Science"},{"slug":"mechanical","name":"Mechanical"},{"slug":"civil","name":"Civil"},{"slug":"ai-data-science","name":"AI & Data Science"},{"slug":"ee-ec-eee","name":"EE / EC / EEE"}]},{"slug":"aktu","name":"AKTU","fullName":"Dr. A. P. J. Abdul Kalam Technical University","branches":[{"slug":"first-year-common","name":"First Year (Common)"},{"slug":"computer-science","name":"Computer Science"}]}],"activePapers":[{"id":"cloud-computing-2021","title":"Cloud Computing (2021)","subjectSlug":"cloud-computing","subjectName":"Cloud Computing","universitySlug":"rtu","branchSlug":"computer-science","year":4,"semester":7,"examYear":2021,"paperCode":"7E7031","questions":[{"id":"v2-cloud-computing-2021-pA-q1","number":1,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"Define Cloud Computing."}],"answer":{"summary":"Cloud Computing is the mathematical and architectural abstraction of physical hardware, delivering on-demand computing resources (servers, storage, databases) over the internet with pay-as-you-go pricing.","explanation":[{"type":"paragraph","content":"Cloud Computing fundamentally destroys the need for localized physical servers. It is a massive, highly scalable distributed architecture where computational power, memory, and database storage are mathematically virtualized and delivered instantly over TCP/IP networks, completely eliminating horrific upfront capital expenditures."}]}},{"id":"v2-cloud-computing-2021-pA-q2","number":2,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"What are the essential characteristics of Cloud Computing?"}],"answer":{"summary":"The NIST mathematically defined essential characteristics are On-demand self-service, Broad network access, Massive resource pooling, Rapid elasticity, and strict Measured service.","explanation":[{"type":"paragraph","content":"To be mathematically classified as a \"Cloud\", an architecture MUST provide: 1) On-demand self-service (zero human intervention), 2) Broad network access (accessible via standard protocols), 3) Resource pooling (multi-tenancy), 4) Rapid elasticity (instant infinite scaling), and 5) Measured service (pay-per-byte billing)."}]}},{"id":"v2-cloud-computing-2021-pA-q3","number":3,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"What is Platform as a Service (PaaS)?"}],"answer":{"summary":"PaaS is a cloud service architecture that provides software developers with a complete, pre-configured development and deployment environment, abstracting away underlying OS and server management.","explanation":[{"type":"paragraph","content":"Platform as a Service (PaaS) mathematically isolates developers from infrastructure chaos. The cloud provider automatically provisions the OS, web server (e.g., Apache), and database (e.g., MySQL). Developers solely write application code (e.g., Node.js or Python) and violently deploy it without ever patching a server."}]}},{"id":"v2-cloud-computing-2021-pA-q4","number":4,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"Differentiate between public and private clouds."}],"answer":{"summary":"Public clouds mathematically share massive physical hardware across millions of distinct corporate tenants, whereas Private clouds rigidly dedicate absolute physical hardware to one single corporation.","explanation":[{"type":"paragraph","content":"A Public Cloud (AWS, Azure) utilizes violent multi-tenancy; your database might physically reside on the exact same hard drive as a competitor's database, separated only by hypervisor mathematics. A Private Cloud guarantees absolute physical isolation, built entirely on-premises or on strictly dedicated hardware."}]}},{"id":"v2-cloud-computing-2021-pA-q5","number":5,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"What is a hypervisor?"}],"answer":{"summary":"A hypervisor (Virtual Machine Monitor) is the absolute core software architecture that mathematically slices a single physical server into multiple isolated Virtual Machines (VMs).","explanation":[{"type":"paragraph","content":"The Hypervisor sits directly on top of the physical CPU and RAM. It violently intercepts operating system calls from the VMs and mathematically translates them into physical hardware instructions. It guarantees absolute memory and CPU isolation between competing virtual machines on the same physical motherboard."}]}},{"id":"v2-cloud-computing-2021-pA-q6","number":6,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"Define Grid Computing."}],"answer":{"summary":"Grid Computing is a decentralized mathematical architecture that violently aggregates geographically distributed, heterogeneous computers into a single massive supercomputer to solve horrific computational problems.","explanation":[{"type":"paragraph","content":"Unlike Cloud Computing which is centralized in massive data centers, Grid Computing mathematically harnesses the idle CPU cycles of thousands of disparate, decentralized computers (like home PCs). It violently splits massive scientific problems (like DNA sequencing) into microscopic chunks, processes them globally, and aggregates the results."}]}},{"id":"v2-cloud-computing-2021-pA-q7","number":7,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"What is MapReduce?"}],"answer":{"summary":"MapReduce is a highly aggressive distributed programming model that mathematically splits massive datasets, processes them in parallel (Map), and aggregates the outputs (Reduce).","explanation":[{"type":"paragraph","content":"Engineered by Google, MapReduce completely annihilates the bottleneck of sequential processing. The `Map` function violently chops a 10-Terabyte file into thousands of chunks, distributing them to thousands of CPUs simultaneously. The `Reduce` function mathematically sums the distributed results into a single final output."}]}},{"id":"v2-cloud-computing-2021-pA-q8","number":8,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"Mention any two security challenges in Cloud Computing."}],"answer":{"summary":"Two absolute catastrophic security challenges in Cloud Computing are Data Breach vulnerabilities due to hypervisor failure and massive Distributed Denial of Service (DDoS) resource exhaustion.","explanation":[{"type":"paragraph","content":"Multi-tenancy creates horrific security vectors. If a Hypervisor has a mathematical flaw (like a VM Escape vulnerability), a hacker in VM-A can violently read the RAM of VM-B. Secondly, cloud architectures are massive targets for DDoS attacks designed to mathematically bankrupt a company via auto-scaling costs."}]}},{"id":"v2-cloud-computing-2021-pA-q9","number":9,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"What is Service Level Agreement (SLA) in Cloud Computing?"}],"answer":{"summary":"An SLA is a strict, legally binding mathematical contract between a cloud provider and a client that dictates absolute uptime guarantees and financial penalties.","explanation":[{"type":"paragraph","content":"Service Level Agreements (SLAs) are the absolute backbone of enterprise cloud trust. They mathematically define the exact allowed downtime (e.g., 99.999% uptime guarantees max 5.26 minutes of downtime per year). If the provider violently fails this metric, they must automatically issue strict financial refunds."}]}},{"id":"v2-cloud-computing-2021-pA-q10","number":10,"marks":2,"tags":["Part A"],"text":[{"type":"paragraph","content":"Name any two open-source cloud computing platforms."}],"answer":{"summary":"Two dominant open-source cloud architectures are OpenStack (used for massive IaaS deployments) and Apache CloudStack.","explanation":[{"type":"paragraph","content":"OpenStack is the absolute industry standard for building massive, scalable Private Cloud architectures. It provides mathematical hypervisor management, software-defined networking (Neutron), and block storage (Cinder). Apache CloudStack is a highly competitive, monolithic alternative designed to aggressively manage vast networks of virtual machines."}]}},{"id":"v2-cloud-computing-2021-pB-q1","number":11,"marks":4,"tags":["Part B"],"text":[{"type":"paragraph","content":"Explain the different deployment models in Cloud Computing."}],"answer":{"summary":"A critical architectural breakdown of Cloud Deployment Models. Explains the strict mathematical and physical boundaries defining Public, Private, Hybrid, and Community clouds, detailing their respective financial and security trade-offs.","explanation":[{"type":"heading","content":"Cloud Computing Deployment Models"},{"type":"paragraph","content":"Cloud computing architectures are not physically identical; they are mathematically divided into four absolute deployment models based on physical location, ownership, and strict access controls. Selecting the wrong model can lead to catastrophic financial waste or horrific security breaches."},{"type":"subheading","content":"1. The Public Cloud"},{"type":"list","items":["**Architecture:** Owned and violently operated by massive third-party mega-corporations (AWS, Google, Microsoft). All physical hardware (servers, SANs) sits in their remote data centers.","**Mathematical Execution:** It relies on absolute multi-tenancy. Millions of completely unrelated users share the exact same physical CPU cycles and hard drives, separated purely by Hypervisor mathematics.","**Merits & Demerits:** Infinite instant scalability and zero upfront hardware cost. However, it provides the lowest level of absolute physical security and compliance."]},{"type":"subheading","content":"2. The Private Cloud"},{"type":"list","items":["**Architecture:** The cloud infrastructure is mathematically dedicated to ONE single organization. It can be physically located on-premises or hosted by a third party, but the hardware is NEVER shared.","**Merits & Demerits:** Absolute mathematical security, military-grade data privacy, and strict regulatory compliance. However, it requires catastrophic upfront capital expenditure to purchase the physical servers."]},{"type":"subheading","content":"3. The Hybrid Cloud"},{"type":"list","items":["**Architecture:** A highly complex, violently fused architecture linking a Private Cloud directly to a Public Cloud using mathematically secure VPN tunnels.","**Execution (Cloud Bursting):** A bank stores highly classified customer data strictly on its Private Cloud. During a massive traffic spike (Black Friday), the architecture automatically \"bursts\" the non-sensitive web-server load into the AWS Public Cloud to prevent a catastrophic crash."]},{"type":"subheading","content":"4. The Community Cloud"},{"type":"list","items":["**Architecture:** A specialized cloud mathematically shared by several organizations that have the exact same strict security, privacy, and compliance requirements (e.g., a shared cloud exclusively for 50 different hospitals to store MRI scans)."]}]}},{"id":"v2-cloud-computing-2021-pB-q2","number":12,"marks":4,"tags":["Part B"],"text":[{"type":"paragraph","content":"Discuss the architecture of NIST Cloud Computing model."}],"answer":{"summary":"An architectural exposition of the NIST Cloud Computing Model. Details the absolute rigid definition comprising 5 Essential Characteristics, 3 Service Models (SPI), and 4 Deployment Models.","explanation":[{"type":"heading","content":"The Architecture of the NIST Cloud Computing Model"},{"type":"paragraph","content":"Before 2011, \"Cloud\" was a chaotic marketing buzzword. The National Institute of Standards and Technology (NIST) violently imposed a rigid, mathematically exact architectural definition. If a system does not strictly adhere to this model, it is a fake cloud."},{"type":"heading","content":"The 5 Essential Characteristics (The Core Engine)"},{"type":"list","items":["**1. On-Demand Self-Service:** A human can violently provision 1,000 servers at 3 AM via an API without speaking to a single human system administrator.","**2. Broad Network Access:** The architecture must be accessible via standard TCP/IP over the internet from any device (phone, laptop).","**3. Resource Pooling:** The provider must mathematically pool massive computing resources to serve multiple consumers using a strict multi-tenant model. Physical resources are dynamically violently reassigned.","**4. Rapid Elasticity:** The system must appear mathematically infinite. It must automatically scale out to 10,000 CPUs during a spike, and violently scale back down to 1 CPU when traffic drops.","**5. Measured Service:** The absolute execution of Utility Computing. Every single Megabyte of RAM, CPU cycle, and network packet is mathematically metered, and the client is billed precisely."]},{"type":"heading","content":"The 3 Service Models (The Stack)"},{"type":"list","items":["**SaaS (Software):** The absolute top layer. The consumer uses the application (e.g., Gmail) and manages absolutely nothing.","**PaaS (Platform):** The middle layer. The consumer deploys application code; the provider manages the OS and runtime.","**IaaS (Infrastructure):** The absolute bottom layer. The consumer is given raw virtual hardware (VMs, block storage) and must violently manage the OS and firewall."]},{"type":"paragraph","content":"These are deployed across the 4 Deployment Models (Public, Private, Hybrid, Community), forming the absolute definitive NIST framework."}]}},{"id":"v2-cloud-computing-2021-pB-q3","number":13,"marks":4,"tags":["Part B"],"text":[{"type":"paragraph","content":"Compare and contrast Virtual Machines and Containers."}],"answer":{"summary":"A critical mathematical comparison between Virtual Machines and Docker Containers. Violently contrasts the heavy, hardware-level abstraction of Hypervisors against the ultra-lightweight, OS-level namespace isolation of Container engines.","explanation":[{"type":"heading","content":"Virtual Machines vs. Containers: Architectural Comparison"},{"type":"paragraph","content":"Both VMs and Containers are virtualization architectures designed to mathematically isolate applications. However, they execute this isolation at completely different layers of the technology stack, resulting in massive differences in RAM consumption and boot speed."},{"type":"heading","content":"1. Virtual Machine (VM) Architecture"},{"type":"paragraph","content":"VMs execute **Hardware-Level Virtualization**."},{"type":"list","items":["**The Mechanism:** A Hypervisor (like VMware or ESXi) sits directly on the physical hardware. It mathematically fakes a complete physical motherboard, CPU, and BIOS for every single VM.","**The Guest OS:** Because it fakes hardware, EVERY single VM must violently boot its own complete, heavy Operating System (Guest OS). If you run 10 VMs, you are running 10 complete copies of Windows or Linux.","**Demerit:** Horrific bloat. A VM requires Gigabytes of RAM just to hold the Guest OS, and takes minutes to physically boot. However, it provides absolute, mathematically impenetrable security isolation."]},{"type":"heading","content":"2. Container Architecture (Docker)"},{"type":"paragraph","content":"Containers execute **OS-Level Virtualization**."},{"type":"list","items":["**The Mechanism:** Containers violently abandon the Hypervisor. Instead, they use a Container Engine (like Docker) that sits on top of ONE single Host Operating System.","**Namespace Isolation:** The engine uses mathematical Linux kernel features (`cgroups` and `namespaces`) to isolate processes. Containers DO NOT have a Guest OS. They mathematically share the Host OS kernel.","**Merit:** Absolute explosive efficiency. A container is just an isolated process. It requires only Megabytes of RAM and boots in milliseconds. You can run 1,000 containers on a server that could only hold 10 VMs.","**Demerit:** Weaker security. If a hacker mathematically breaches the shared Host Kernel from inside one container, they violently compromise every single container on the server."]}]}},{"id":"v2-cloud-computing-2021-pB-q4","number":14,"marks":4,"tags":["Part B"],"text":[{"type":"paragraph","content":"Explain the concept of Resource Provisioning in Cloud Computing."}],"answer":{"summary":"An advanced architectural breakdown of Resource Provisioning in Cloud Computing. Explains the strict mathematical algorithms governing Static, Dynamic, and Auto-scaling provisioning to prevent catastrophic under-utilization or server collapse.","explanation":[{"type":"heading","content":"Resource Provisioning Architecture in Cloud Computing"},{"type":"paragraph","content":"Resource Provisioning is the highly complex mathematical process of mapping massive physical hardware resources (CPU cores, RAM, IOPS) to the constantly fluctuating demands of virtual machines and containers. If provisioning is executed poorly, the architecture either suffers catastrophic performance failure (under-provisioning) or horrific financial waste (over-provisioning)."},{"type":"heading","content":"Mathematical Provisioning Strategies"},{"type":"subheading","content":"1. Static Provisioning (Pre-Provisioning)"},{"type":"paragraph","content":"The absolute most primitive architecture. The engineer mathematically calculates the absolute maximum peak load the application will ever experience (e.g., Black Friday) and manually rents 50 servers permanently."},{"type":"list","items":["**Demerit:** Massive financial destruction. For 364 days of the year, 48 servers sit completely idle, burning electricity and capital while doing absolutely zero mathematical computation."]},{"type":"subheading","content":"2. Dynamic Provisioning"},{"type":"paragraph","content":"The provider dynamically allocates resources based on current demand, but it often requires manual triggers or API calls by the system administrator to violently spin up new VMs."},{"type":"subheading","content":"3. Auto-Scaling (The Absolute Standard)"},{"type":"paragraph","content":"The absolute pinnacle of cloud architecture. It utilizes strict algorithmic feedback loops. An agent mathematically monitors the CPU load of the web servers every 10 seconds."},{"type":"list","items":["**Scale-Out (Horizontal):** If average CPU $> 85\\%$ for 2 minutes, the algorithm violently triggers the API to instantly boot 5 brand new VMs and automatically attaches them to the Load Balancer.","**Scale-In:** If average CPU $< 20\\%$ for 10 minutes, the algorithm aggressively terminates 5 VMs, instantly halting the financial billing.","**Vertical Scaling:** Mathematically injecting RAM or CPU cores directly into a live, running VM without rebooting it (highly complex hypervisor mathematics)."]}]}},{"id":"v2-cloud-computing-2021-pB-q5","number":15,"marks":4,"tags":["Part B"],"text":[{"type":"paragraph","content":"Describe the working mechanism of Hadoop Distributed File System (HDFS)."}],"answer":{"summary":"A definitive explanation of the Hadoop Distributed File System (HDFS). Violently details the Master-Slave architecture, the exact mathematical data chunking process, and the absolute replication algorithms that guarantee horrific fault tolerance.","explanation":[{"type":"heading","content":"Architecture and Mechanism of HDFS"},{"type":"paragraph","content":"The Hadoop Distributed File System (HDFS) is a massive, highly fault-tolerant storage architecture designed to mathematically distribute Petabytes of data across thousands of cheap, unreliable commodity hard drives. It violently assumes that physical hard drives will fail daily, and uses mathematical replication to prevent data loss."},{"type":"heading","content":"The Master-Slave Architecture"},{"type":"list","items":["**NameNode (The Master):** The absolute mathematical brain. It does NOT store the actual data. It stores only the Metadata (the directory tree, and exactly which DataNode holds which chunk of a file). It resides completely in RAM for explosive speed.","**DataNodes (The Slaves):** Thousands of dumb physical servers. They literally just store raw blocks of binary data on their hard drives and continuously scream \"I am alive!\" (Heartbeats) to the NameNode every 3 seconds."]},{"type":"heading","content":"The Mathematical Write Mechanism"},{"type":"paragraph","content":"When a user attempts to save a massive 1-Terabyte video file:"},{"type":"list","items":["1. **Block Splitting:** HDFS violently chops the file into strict mathematical chunks, exactly 128 Megabytes each.","2. **Replication (Fault Tolerance):** To survive hardware death, HDFS forces a Replication Factor (default = 3). Every single 128MB block is violently copied perfectly to exactly 3 DIFFERENT DataNodes across 3 different physical server racks.","3. **The Pipeline:** The client writes Block A to DataNode 1. DataNode 1 autonomously forwards the copy to DataNode 2, which forwards it to DataNode 3. This offloads the network bandwidth from the Master.","4. **Catastrophic Failure Recovery:** If DataNode 2 catches fire and dies, its Heartbeat stops. The NameNode instantly mathematically realizes that Block A now only has 2 copies instead of 3. It violently commands DataNode 1 to copy Block A to DataNode 4, instantly restoring absolute mathematical fault tolerance without any human intervention."]}]}},{"id":"v2-cloud-computing-2021-pB-q6","number":16,"marks":4,"tags":["Part B"],"text":[{"type":"paragraph","content":"Explain Identity and Access Management (IAM) in the context of cloud security."}],"answer":{"summary":"A critical analysis of Identity and Access Management (IAM) in Cloud Security. Details how IAM enforces absolute mathematical boundaries through strict Authentication, Granular Authorization Policies, and Multi-Factor security.","explanation":[{"type":"heading","content":"Identity and Access Management (IAM) Architecture"},{"type":"paragraph","content":"In a massive Public Cloud (AWS, Azure), physical security is irrelevant because the servers are remote. The ONLY mathematical barrier preventing a hacker from violently deleting the entire corporate database is the Identity and Access Management (IAM) architecture. IAM strictly dictates exactly WHO can enter the cloud, and exactly WHAT they are mathematically allowed to execute."},{"type":"heading","content":"The Core Mathematical Pillars of IAM"},{"type":"subheading","content":"1. Absolute Authentication (Who are you?)"},{"type":"paragraph","content":"The system must mathematically prove the entity's identity. Passwords are catastrophically weak. IAM strictly enforces Multi-Factor Authentication (MFA), requiring a password AND a cryptographic hardware token (like a YubiKey) or a biometric signature. Furthermore, IAM handles programmatic access via highly secure cryptographic Access Keys."},{"type":"subheading","content":"2. Granular Authorization (What can you do?)"},{"type":"paragraph","content":"Once inside, the user has absolutely zero permissions by default. IAM utilizes strict JSON-based Policy Documents to violently enforce the Principle of Least Privilege."},{"type":"list","items":["A user is assigned a Role (e.g., `Junior_Dev`).","The IAM Policy mathematically dictates: \"This user is explicitly ALLOWED to `read` from Database-A, but explicitly DENIED the ability to `delete` Database-A, and explicitly DENIED access to Database-B.\" Every single API call is aggressively checked against these mathematical policies in milliseconds."]},{"type":"subheading","content":"3. Auditing and Accounting"},{"type":"paragraph","content":"IAM mathematically logs every single API call ever made. If a database is deleted, the IAM CloudTrail instantly proves exactly which user ID executed the command at exactly what millisecond, providing absolute legal non-repudiation."}]}},{"id":"v2-cloud-computing-2021-pB-q7","number":17,"marks":4,"tags":["Part B"],"text":[{"type":"paragraph","content":"Discuss the role of Web Services in Cloud Computing."}],"answer":{"summary":"An architectural review of Web Services in Cloud Computing. Explains how REST and SOAP APIs mathematically decouple massive distributed systems, allowing completely heterogeneous architectures to communicate flawlessly over HTTP.","explanation":[{"type":"heading","content":"The Role of Web Services in Cloud Architecture"},{"type":"paragraph","content":"Cloud Computing is not a monolithic program; it is a massive, chaotic collection of thousands of distributed microservices running on completely different hardware and operating systems. The absolute mathematical glue that violently binds these heterogeneous systems together is the Web Service (API)."},{"type":"heading","content":"Architectural Mechanisms"},{"type":"paragraph","content":"A Web Service is a strictly defined, machine-to-machine communication protocol over standard HTTP."},{"type":"list","items":["**Interoperability:** If an iOS application (written in Swift) needs to query a Cloud Database (running on Linux/Java), they cannot mathematically share memory. The Web Service violently translates the data into a universal mathematical format (like JSON or XML), allowing the two completely alien systems to talk flawlessly.","**REST (Representational State Transfer):** The dominant architectural style for the Cloud. It utilizes the absolute standard HTTP verbs (`GET`, `POST`, `PUT`, `DELETE`). It is completely Stateless—every single request must mathematically contain all the information necessary for the server to process it, allowing the cloud to violently autoscale the backend servers without losing session data.","**SOAP (Simple Object Access Protocol):** An older, highly rigid mathematical protocol using complex XML envelopes. It is heavily utilized in enterprise financial clouds because it mathematically guarantees strict ACID transactions across distributed networks."]},{"type":"paragraph","content":"Without Web Services, the entire fundamental concept of \"Cloud\" mathematically collapses into isolated, unreachable servers."}]}},{"id":"v2-cloud-computing-2021-pC-q1","number":18,"marks":10,"tags":["Part C"],"text":[{"type":"paragraph","content":"Explain the architecture of Cloud Computing in detail. Discuss the various layers and their functionalities."}],"answer":{"summary":"A massive architectural exposition of Cloud Computing. Violently details the layered stack from Physical Infrastructure (Data Centers) through the Hypervisor layer, up to the strict mathematical definitions of IaaS, PaaS, and SaaS.","explanation":[{"type":"heading","content":"The Layered Architecture of Cloud Computing"},{"type":"paragraph","content":"Cloud Computing is not a single technology; it is a massive, violently stratified architectural stack. Each mathematical layer completely abstracts the complexity of the layer beneath it, allowing end-users to interact with high-level software without understanding the horrific physical physics of the underlying data center."},{"type":"heading","content":"1. The Physical Infrastructure Layer (The Hardware)"},{"type":"paragraph","content":"This is the absolute base of the architecture. It consists of the literal physical data centers spread globally."},{"type":"list","items":["**Compute:** Tens of thousands of physical CPU blades mathematically mounted in massive racks.","**Storage:** Petabytes of physical hard drives (HDDs and SSDs) wired into Storage Area Networks (SANs).","**Network:** Massive fiber-optic cables, physical routers, and hardware Load Balancers that aggressively pump Terabits of data per second.","**Facilities:** The horrific power requirements (Megawatts), massive industrial cooling towers (HVAC), and physical perimeter security."]},{"type":"heading","content":"2. The Virtualization Layer (The Hypervisor)"},{"type":"paragraph","content":"Raw hardware is mathematically rigid. The Virtualization Layer (Hypervisor) violently abstracts the physical hardware."},{"type":"list","items":["It mathematically slices a single physical CPU with 64 cores into 128 virtual CPUs (vCPUs).","It aggressively allocates exact chunks of RAM to isolated Virtual Machines.","This layer is the absolute core engine that enables Multi-tenancy (allowing Netflix and a startup to run on the exact same physical motherboard without mathematically colliding)."]},{"type":"heading","content":"3. Infrastructure as a Service (IaaS)"},{"type":"paragraph","content":"This layer exposes the virtualized hardware directly to the consumer via APIs."},{"type":"list","items":["**Functionality:** The consumer rents raw VMs, virtual networks, and block storage (e.g., AWS EC2, Azure VMs).","**Responsibility:** The cloud provider manages the physical data center and hypervisor. The consumer must violently manage the Operating System, security patches, and application runtimes. It provides maximum mathematical flexibility but maximum administrative burden."]},{"type":"heading","content":"4. Platform as a Service (PaaS)"},{"type":"paragraph","content":"This layer mathematically abstracts the Operating System away from the consumer."},{"type":"list","items":["**Functionality:** It provides a complete, pre-configured development environment. The cloud provider automatically boots the OS, configures the Apache web server, installs the Node.js runtime, and wires up the database (e.g., AWS Elastic Beanstalk, Heroku).","**Responsibility:** The consumer ONLY uploads their raw code. The PaaS violently handles load balancing, auto-scaling, and OS security patches autonomously."]},{"type":"heading","content":"5. Software as a Service (SaaS)"},{"type":"paragraph","content":"The absolute top layer of the architecture, built for non-technical human end-users."},{"type":"list","items":["**Functionality:** The consumer accesses a complete, fully functioning application directly through a web browser (e.g., Gmail, Salesforce, Microsoft 365).","**Responsibility:** The consumer manages absolutely nothing except their own account settings. The provider manages the code, the OS, the databases, and the physical hardware."]},{"type":"svg","content":""}]}},{"id":"v2-cloud-computing-2021-pC-q2","number":19,"marks":10,"tags":["Part C"],"text":[{"type":"paragraph","content":"What is Virtualization? Explain the different types of virtualization with suitable examples. Discuss its role in Cloud Computing."}],"answer":{"summary":"An exhaustive theoretical breakdown of Virtualization. Details how Hypervisors mathematically shatter physical hardware into isolated VMs, contrasting Type 1 (Bare-Metal) against Type 2 (Hosted) architectures, and highlighting its absolute foundational role in Cloud Computing.","explanation":[{"type":"heading","content":"Virtualization Architecture in Cloud Computing"},{"type":"paragraph","content":"Virtualization is the absolute mathematical bedrock of the entire Cloud computing industry. Without it, the Cloud literally cannot exist. It is defined as the creation of a software-based (virtual) representation of something physical, such as a server, storage device, or network. It mathematically completely decouples the software from the rigid physical hardware."},{"type":"heading","content":"The Hypervisor (Virtual Machine Monitor)"},{"type":"paragraph","content":"The core engine of virtualization is the Hypervisor. It is a highly aggressive software layer that sits between the physical hardware and the operating systems. Its mathematical job is to violently slice the physical CPU, RAM, and Disk into multiple isolated chunks and present them to the Guest Operating Systems as if they were real, dedicated physical hardware."},{"type":"heading","content":"Types of Virtualization"},{"type":"subheading","content":"1. Type 1 Hypervisor (Bare-Metal)"},{"type":"paragraph","content":"The absolute enterprise standard."},{"type":"list","items":["**Architecture:** The hypervisor software is installed DIRECTLY onto the bare physical motherboard. There is absolutely NO host operating system beneath it.","**Merits:** Explosive performance and absolute security. Because there is no bloated host OS in the middle, the VMs communicate almost directly with the physical CPU via rigorous mathematical translation.","**Examples:** VMware ESXi, Microsoft Hyper-V, Xen Server."]},{"type":"subheading","content":"2. Type 2 Hypervisor (Hosted)"},{"type":"paragraph","content":"Used primarily for desktop development."},{"type":"list","items":["**Architecture:** The server runs a standard Host OS (like Windows 10 or Ubuntu). The Hypervisor is installed as a normal application on top of that OS. The VMs run inside the hypervisor.","**Demerits:** Horrific performance lag. If a VM needs to execute a CPU instruction, the command must pass through the Guest OS, then the Hypervisor, then the Host OS, and finally to the CPU.","**Examples:** Oracle VirtualBox, VMware Workstation."]},{"type":"subheading","content":"3. Containerization (OS-Level Virtualization)"},{"type":"paragraph","content":"A modern, ultra-lightweight alternative to Hypervisors. Instead of faking physical hardware to boot multiple OSs, a Container Engine (like Docker) mathematically isolates individual applications by sharing a SINGLE Host OS kernel using Linux namespaces. It is violently fast and consumes almost zero overhead."},{"type":"heading","content":"The Role of Virtualization in Cloud Computing"},{"type":"paragraph","content":"Virtualization provides the exact mathematical capabilities required for a Cloud:"},{"type":"list","items":["**Multi-Tenancy:** It allows AWS to run a VM for Coca-Cola and a VM for Pepsi on the exact same physical server, guaranteeing absolute mathematical memory isolation so they cannot read each other's data.","**Rapid Elasticity:** You cannot physically build a server in 10 seconds. But you can violently clone a Virtual Machine software file and boot it in 10 seconds, allowing for instant Cloud Auto-scaling.","**Live Migration:** Because a VM is mathematically just a file in RAM, the Hypervisor can freeze a running VM on Server A, blast it across the fiber network to Server B, and unfreeze it with zero downtime, rendering hardware maintenance completely invisible to the user."]},{"type":"svg","content":""}]}},{"id":"v2-cloud-computing-2021-pC-q3","number":20,"marks":10,"tags":["Part C"],"text":[{"type":"paragraph","content":"Describe the MapReduce programming model in detail. How does it handle fault tolerance? Give an example of a MapReduce job."}],"answer":{"summary":"A definitive theoretical breakdown of the MapReduce programming model. Violently details the split of computational logic into Map and Reduce phases, the underlying Shuffle and Sort mechanisms, and the absolute hardware fault tolerance achieved through aggressive task reassignment.","explanation":[{"type":"heading","content":"The Architecture of the MapReduce Programming Model"},{"type":"paragraph","content":"Invented by Google to index the entire internet, MapReduce is a mathematically aggressive programming architecture designed to process Petabytes of data across thousands of commodity servers. It completely abstracts the horrors of parallel processing, network communication, and hardware failure away from the programmer. The programmer only writes two rigid mathematical functions: `Map()` and `Reduce()`."},{"type":"heading","content":"The Sequential Execution Pipeline"},{"type":"list","items":["**1. Input Splitting:** The master node violently chops a massive 1-Terabyte dataset into thousands of independent 128MB chunks.","**2. The Map Phase (Parallel Execution):** The master dispatches the user's `Map()` code to thousands of worker nodes simultaneously. Each worker executes the code on its specific 128MB chunk. \n *Mathematics:* The Map function takes raw text and outputs intermediate Key-Value pairs. \n `Map(String key, String value) -> list(Key, Value)`","**3. Shuffle and Sort (The Network Bottleneck):** The absolute most complex phase. The Hadoop framework takes all millions of intermediate Key-Value pairs from all workers, violently sorts them by Key, and routes all identical Keys to the exact same Reduce worker across the network.","**4. The Reduce Phase (Aggregation):** A Reduce worker receives a specific Key and a massive list of all values associated with that key. It mathematically aggregates them into a single final output. \n `Reduce(String key, list(Values)) -> list(Key, Value)`"]},{"type":"heading","content":"Absolute Fault Tolerance Mechanism"},{"type":"paragraph","content":"MapReduce violently assumes hardware will die during processing. It achieves fault tolerance through Master Surveillance:"},{"type":"list","items":["Every worker node continuously blasts a \"Heartbeat\" signal to the Master Node over the network.","If a worker CPU overheats and dies midway through a massive Map task, the heartbeat stops.","The Master Node mathematically detects the silence, instantly declares the worker dead, and violently reschedules that exact Map task to a brand new, healthy worker node. The programmer is completely unaware this horrific failure even occurred."]},{"type":"heading","content":"Example: The Word Count Execution"},{"type":"paragraph","content":"Goal: Count the occurrences of every word in a 10TB library of books."},{"type":"list","items":["**Input:** `[\"apple banana apple\"]`","**Map Function:** Emits a `1` for every word it sees. \n `(\"apple\", 1), (\"banana\", 1), (\"apple\", 1)`","**Shuffle/Sort:** Routes all \"apple\"s to Reducer A. \n `(\"apple\", [1, 1])`, `(\"banana\", [1])`","**Reduce Function:** Mathematically sums the list. \n `(\"apple\", 2), (\"banana\", 1)`"]}]}},{"id":"v2-cloud-computing-2021-pC-q4","number":21,"marks":10,"tags":["Part C"],"text":[{"type":"paragraph","content":"Discuss the major security and privacy issues in Cloud Computing. Propose a framework to mitigate these risks."}],"answer":{"summary":"A critical analysis of Security and Privacy in Cloud architectures. Analyzes catastrophic vectors like Hypervisor VM Escape and Data Breach multitenancy, and proposes a rigid mathematical framework including AES-256 encryption, strict IAM, and Data Loss Prevention to mitigate them.","explanation":[{"type":"heading","content":"Major Security and Privacy Issues in Cloud Computing"},{"type":"paragraph","content":"When a corporation migrates to a Public Cloud, they mathematically surrender physical control of their servers and hard drives. This creates completely unprecedented, catastrophic security vectors that do not exist in traditional on-premises data centers."},{"type":"heading","content":"The Catastrophic Vulnerabilities"},{"type":"list","items":["**1. Multi-Tenancy & VM Escape:** The most horrific cloud-specific threat. Your VM shares the same physical RAM as a malicious hacker's VM. If the hacker finds a zero-day flaw in the Hypervisor architecture (VM Escape), they can violently punch through the mathematical isolation barrier and read your raw RAM, stealing encryption keys.","**2. Data Breaches via Misconfiguration:** Unlike physical servers, cloud databases (like AWS S3) are internet-facing by default. A single incorrect click in an IAM policy document instantly exposes a Petabyte database containing 100 million credit cards to the public internet.","**3. Insecure APIs:** The entire cloud is controlled by Web APIs. If the API authentications are weak, a hacker can violently issue a command to instantly delete every single server the corporation owns.","**4. Data Privacy & Sovereignty:** If a European company stores data on an AWS server physically located in the US, the US Government can legally seize it (Patriot Act), violating the horrific mathematical fines of the EU GDPR."]},{"type":"heading","content":"Proposed Mathematical Mitigation Framework"},{"type":"paragraph","content":"To survive in the cloud, corporations must implement a rigid, multi-layered security architecture:"},{"type":"list","items":["**Layer 1: Absolute Encryption (Data at Rest and Transit):** All data must be violently encrypted using AES-256 before it ever leaves the corporate building. The cloud provider must NEVER possess the private decryption keys (Customer Managed Keys). If the cloud is breached, the hackers only steal mathematical gibberish.","**Layer 2: Zero Trust Identity and Access Management (IAM):** Implement strict Multi-Factor Authentication (MFA) for every API call. Enforce the Principle of Least Privilege—no human or script gets broad admin rights, only exact mathematical permissions required for the specific task.","**Layer 3: Network Micro-Segmentation:** Do not rely on one massive firewall. Wrap every single VM in its own mathematical Security Group (micro-firewall), strictly blocking all lateral network traffic to prevent a virus from spreading across the cloud.","**Layer 4: Continuous Automated Auditing:** Deploy AI-driven Cloud Security Posture Management (CSPM) tools that mathematically scan the entire cloud architecture every 60 seconds, violently instantly shutting down any database that is accidentally exposed to the public internet."]}]}},{"id":"v2-cloud-computing-2021-pC-q5","number":22,"marks":10,"tags":["Part C"],"text":[{"type":"paragraph","content":"Write detailed notes on: (a) Eucalyptus (b) OpenStack. Compare their features and use cases."}],"answer":{"summary":"A comparative architectural study of Eucalyptus and OpenStack. Details Eucalyptus's historical relevance and rigid AWS compatibility against OpenStack's absolute dominance, massive modular architecture, and extreme deployment flexibility for modern Private Clouds.","explanation":[{"type":"heading","content":"Comparative Analysis: Eucalyptus vs. OpenStack"},{"type":"paragraph","content":"Both Eucalyptus and OpenStack are open-source software architectures designed strictly to build and manage massive Private or Hybrid Cloud infrastructures (Infrastructure as a Service - IaaS). They both take racks of dumb physical servers and violently install a cloud management layer over them."},{"type":"heading","content":"(a) Eucalyptus Architecture"},{"type":"paragraph","content":"Elastic Utility Computing Architecture for Linking Your Programs To Useful Systems (Eucalyptus) was one of the earliest pioneering cloud platforms."},{"type":"list","items":["**Design Philosophy:** It was mathematically engineered from the ground up to be strictly API-compatible with Amazon Web Services (AWS EC2, S3).","**Use Case:** Its absolute primary use case was Hybrid Cloud. A company could build a Private Cloud using Eucalyptus, and because the APIs were mathematically identical to AWS, developers could violently shift workloads between their internal servers and the public AWS cloud without rewriting a single line of code.","**Demerit:** It suffered from rigid, monolithic architecture and eventually lost the massive open-source community war, leading to its decline."]},{"type":"heading","content":"(b) OpenStack Architecture"},{"type":"paragraph","content":"OpenStack is the absolute undisputed king of modern open-source Private Cloud architecture, originally created by NASA and Rackspace. It controls massive data centers for telecom giants and scientific grids."},{"type":"list","items":["**Design Philosophy:** Unlike Eucalyptus, OpenStack is completely modular. It is a massive chaotic collection of independent, specialized mathematical projects communicating via REST APIs.","**Core Components:** \n - **Nova:** The absolute engine that controls the Compute (Virtual Machines).\n - **Neutron:** Handles violently complex Software-Defined Networking (SDN).\n - **Cinder / Swift:** Manages persistent Block and Object storage.\n - **Keystone:** The central mathematical IAM authentication authority.","**Merit:** Infinite flexibility. You can swap out the underlying hypervisor (KVM, Xen) or networking hardware seamlessly. It is backed by a massive global consortium of corporations."]},{"type":"heading","content":"Architectural Comparison and Conclusion"},{"type":"paragraph","content":"Eucalyptus focused heavily on AWS compatibility, locking it into a specific architectural mindset. OpenStack violently focused on extreme modularity and scalability, becoming a massive operating system for data centers. Today, OpenStack is the absolute industry standard for on-premises IaaS, while Eucalyptus is largely historical."}]}}]}],"loading":false,"error":null}}}

Q3Cloud Computing

Question

Answer