191cs721 Cloud Computing QB With Answers PDF

VEL TECH MULTI TECH Dr.RANGARAJAN Dr.
SAKUNTHALA ENGINEERING COLLEGE

(An Autonomous Institution, Affiliated to Anna University, Chennai)
Seventh Semester
Degree/Branch: BE/AIDS
Subject code: 191CS721 Subject Name: Cloud Computing
Question Bank
UNIT-I
Introduction to Cloud Computing, Definition of Cloud, Evolution of Cloud Computing -Fundamental Cloud
Architectures – Advanced Cloud Architectures - Specialized Cloud Architecture- Underlying Principles of
Parallel and Distributed Computing , Cloud Characteristics- Elasticity in Cloud -On demand provisioning
Sl.no Part A UNIT CL

1 ________________ is a paradigm of distributed computing to provide the CO1.1 CL1
customers on-demand, utility based computing service.
a) Remote Sensing
b) Remote Invocation
c) Cloud Computing
d) Private Computing
2 Which of the following is not a cloud stakeholder? CO1.1 CL1
a) Cloud providers
b) Clients
c) End users
d) Cloud users
3 What type of computing technology refers to services and applications that CO1.1 CL1
typically run on a distributed network through virtualized resources?
a) Distributed Computing
b) Cloud Computing
c) Soft Computing
d) Parallel Computing
4 --------- is the type of cloud, which consists of multiple internal or external clouds. CO1.1 CL1
a) Private
b) Public
c) Protected
d) Hybrid
5 Which one among the following is odd one? CO1.2 CL1
a) Private
b) Public
c) Protected
d) Hybrid
6 These cloud services are of the form of utility computing i.e. the _________ uses CO1.2 CL1
these services pay-as-you-go model.
a) Cloud providers
b) Clients
c) End users
d) Cloud users
7 Cloud can be considered the following option? CO1.2 CL1
a. Hadoop
b. Intranet
c. Web Applications
d. All of the mentioned
8 Cloud computing is a kind of abstraction which is based on the notion of CO1.2 CL1
combining physical resources and represents them as _______resources to users.
a. Real
b. Cloud
c. Virtual
d. none of the mentioned
9 Which of the following has many features of that is now known as cloud CO1.3 CL1
computing?
a) Web Service
b) Software
c) All of the mentioned
d) Internet
10 The ------------------- concepts is related to sharing and pooling the resources. CO1.3 CL1
a. Polymorphism
b. Virtualization
c. Abstraction
d. None of the mentioned
11 Which one of the following statements is not true? CO1.3 CL1

a. The popularization of the Internet actually enabled most cloud
computing systems.
b. Cloud computing makes the long-held dream of utility as a payment
possible for you, with an infinitely scalable, universally available
system, pay what you use.
c. Soft computing addresses a real paradigm in the way in which the
system is deployed.
12 ------------------ can be considered as a utility is a dream that dates from the CO1.3 CL1
beginning of the computing industry itself.
a. Computing
b. Model
c. Software
13 An essential concept related to Cloud is CO1.4 CL1
a. Reliability
b. Abstraction
c. Productivity
14 The Cloud Platform by Amazon is CO1.4 CL1
a. Azure
b. AWS
c. Cloudera
15 Which of the following statement is not true? CO1.4 CL1

a. Through cloud computing, one can begin with very small and become
big in a rapid manner.
b. All applications benefit from deployment in the Cloud.
c. Cloud computing is revolutionary, even though the technology it is built
on is evolutionary.
d. None of the mentioned
16 In the Planning Phase, Which of the following is the correct step for performing CO1.5 CL1
the analysis?
a. Cloud Computing Value Proposition
b. Cloud Computing Strategy Planning
c. Both A and B
d. Business Architecture Development
17 What is Business Architecture Development? CO1.5 CL1
a. We recognize the risks that might be caused by cloud computing
application from a business perspective.
b. We identify the applications that support the business processes and the
technologies required to support enterprise applications and data
systems.
c. We formulate all kinds of plans that are required to transform the current
business to cloud computing modes.
d. None of the above
18 The ----------------- refers to the non-functional requirements like disaster CO1.5 CL1
recovery, security, reliability, etc.
a. Service Development
b. Quality of service
c. Plan Development
d. Technical Service
19 The Deployment process phase is ----------------------. CO1.5 CL1
a. Selecting Cloud Computing Provider

b. IT Architecture Development
c. Business Architecture Development
d. Transformation Plan Development
20 How many phases are present in Cloud Computing Planning? CO1.6 CL1
a. 2
b. 3
c. 4
d. 5
21 Cloud computing architecture is a combination of? CO1.6 CL1
a. service-oriented architecture and grid computing

b. Utility computing and event-driven architecture.
c. Service-orrientedarchitectue and event-driven architecture.
d. Virtualization and event-driven architecture.
22 Which one of the following refers to the user's part of the Cloud Computing CO1.6 CL1
system?
a. back End
b. Management
c. Infrastructure
d. Front End
23 Through which, the backend and front-end are connected with each other? CO1.7 CL1
a. Browser
b. Database
c. Network
d. Both A and B
24 The back end’s built-in components of cloud computing is --------------- CO1.7 CL1
a. Security
b. Application
c. Storage
d. Service
25 The GUI for interaction with the cloud is? CO1.7 CL1
a. Client
b. Client Infrastructure
c. Application
d. Server
26 Which technology works behind the cloud computing platform? CO1.8 CL1
a. Virtualization
b. SOA
c. Grid Computing
d. All of the above
27 Which one of the following is a kind of technique that allows sharing the single CO1.8 CL1
physical instance of an application or the resources among multiple
organizations/customers?
a. Virtualization
b. Service-Oriented Architecture
c. Grid Computing
d. Utility Computing
28 Both the CISC and RISC architectures have been developed to reduce the______. CO1.8 CL1
a) cost
b) time delay
c) semantic gap
d) all of the above
29 Significant characteristics of Distributed systems have of CO1.8 CL1

a. 5 types
b. 2 types
c. 3 types
d. 4 types
30 Virtualization that creates one single address space architecture that of, is called CO1.9 CL1
A. Loosely coupled
B. Peer-to-Peer
C. Space-based
D. Tightly coupled
31 Uniprocessor computing devices is called__________. CO1.9 CL1
a. Grid computing
b. Centralized computing
c. Parallel computing
d. Distributed computing
32 Data centers and centralized computing covers many and CO1.9 CL1
a. Microcomputers
b. Minicomputers
c. Mainframe computers
d. Supercomputers
33 Which one is true for Grid Computing? CO1.9 CL1
a. Pieces combine small tasks into complex tasks
b. The subscription tier plays an important role in grid computing.
c. Breaks complex tasks into small operations
d. Both A and C
S.No PART B CO CL
1. How does computing power enable tasks to be performed without the need for CO 1.1 CL2
physical hardware, and what are two technologies that exemplify this concept of
remote computing?
Remote Computing technologies are cluster, grid, and now, cloud computing.
Cluster computing refers that many of the homogenous computers connected on a
network and they perform like a single entity. Cluster computing offers solutions to
solve complicated problems by providing faster computational speed, and enhanced
data integrity. The connected computers execute operations all together thus
creating the impression like a single system (virtual machine).
Grid computing is a commoditized hardware and massively parallel processing. It
enables aggregation of distributed resources and transparently access to them.
Machines can be homogenous or heterogeneous.
2. Advancement of several technologies leads to cloud computing. Justify your answer CL2
CO 1.3
with necessary supporting points with diagram
Cloud computingisreally anadvancement of several technologies, especially in
hardware, Internet technologies, distributed computing, and systems
management.That is shown in figure below.
3. Imagine that you are using high computing power technology, based on your CO 1.3 CL3
experience outline the characteristics of your technology.
Characteristics ofhigh computing power technology are

 Empowerment
 On Demand Self-services
 Agility (Quickness )
 API
 Device and location independence
 Visualization
 Cost
 Multi-tenancy
 Reliability
 Scalability and Elasticity
 Security
 Maintenance
4. Each cloud computing layer offers services to different segments of the market. CO 1.3 CL3
Justify your answer and discuss the different layers that define the cloud
architecture?
Cloud computing is a business model and not technology. Rather it consists of well-
known technologies and concepts, put together in a new way. These technologies
are known as layers. By adding them all together that leads the package that enables
cloud. The figure shows the stack of layers.
The 4 layers of Cloud
5. Instead of using serial computing, what are the reasons why parallel computing is CO 1.4 CL3
often favored?
Parallel computing is often favored because the following reasons.

Save time and money: More resources at a task will shorten it’s time for completion,
with potential cost savings.
Provide concurrency: Single computing resources can only do one task at a time.
Serial computing limits: Transmission speeds depend directly upon hardware.
 Parallel program consists of multiple processes (tasks) simultaneously
solving a given problem.
 Divide-and-Conquer technique is used.
6. Design a distributed system with all necessary components. Justify it. CO1.4 CL2
A distributed system is the interaction of several components that pass through the
entire computing stack from hardware to software. A layered view of a distributed
system is shown in figure.
7. In distributed system classify the logical arrangement of Software Styles according CO 1.4 CL2
to Garlan and Shaw’s definition.
The logical arrangements of Software Styles areclassified as shown in Table below.

Category Most Common Architectural Styles
Data-centered · Repository
· Blackboard
Data flow · Pipe and filter

· Batch sequential
Virtual machine · Rule-based system

· Interpreter
Call and return · Top down systems

· Object oriented systems
· Layered systems
Independent ·Communicating processes
components · Event system
8. In the domain of parallel computing, what sets apart UMA (Uniform Memory CO 1.4 CL2
Access) and NUMA (Non-Uniform Memory Access) shared memory architectures
from each other?
UMA and NUMA are two different shared memory architectures in the domain of
parallel computing.
UMA (Uniform Memory Access): UMA architecture, also known as CC-NUMA
(Cache-Coherent Non-Uniform Memory Access), provides a symmetric memory
access time for all processors. In other words, each processor can access any
memory location in the system with approximately the same latency. This is
achieved through a shared memory bus or an interconnect that connects all
processors and memory modules. The memory is physically distributed but appears
as a single global address space to all processors. To maintain cache coherence, a
protocol is used to ensure that all processors see consistent data when accessing
shared memory.
NUMA (Non-Uniform Memory Access): NUMA architecture acknowledges the
fact that memory access time can vary based on the physical location of the memory
module relative to the accessing processor. In a NUMA system, processors are
grouped together, and each group has its own local memory. Processors within a
group can access their local memory with lower latency compared to accessing
remote memory in another group.
NUMA systems typically use an interconnect that connects processor groups, and
while memory can be physically distributed, the memory address space is still
globally visible to all processors. However, memory access time varies depending
on whether the memory being accessed is local or remote. Remote memory access
usually incurs higher latency due to the need to traverse the interconnect.
9. Address the features and challenges of a more flexible hybrid distributed shared CO 1.4 CL1
memory systems approach for parallel computing?
Features:
Memory Abstraction: Hybrid DSM architectures aim to provide a unified view of
memory across a distributed system, abstracting the complexities of memory
distribution and management. This abstraction makes programming easier, as
developers can write code as if they were targeting a single shared memory system.
Scalability: Distributed memory systems excel at scalability, as they can efficiently
handle large-scale parallel computations by distributing data across multiple nodes.
Hybrid DSM architectures can leverage this scalability by combining local memory
in each node with distributed memory across nodes.
Flexibility: Hybrid DSM systems offer a balance between the programming
simplicity of shared memory models and the scalability of distributed memory
models. This flexibility allows developers to choose the most suitable memory
model for different parts of their application, optimizing performance.
Data Sharing: In a hybrid DSM architecture, data sharing between processes or
threads can be more efficient compared to pure distributed memory systems. This
can lead to reduced communication overhead and improved performance for
applications that require frequent data sharing.
Weaknesses:
Complexity: Hybrid DSM architectures introduce additional complexity compared
to pure shared or distributed memory systems. Developers need to manage data
placement, synchronization, and communication explicitly, which can increase the
risk of programming errors and require more sophisticated programming models.
Synchronization Overhead: While hybrid DSM architectures aim to provide a
shared memory abstraction, managing consistency and synchronization across
distributed nodes can introduce overhead.
Performance Trade-offs: Hybrid DSM architectures might not provide optimal
performance for all types of applications. Some applications might be better suited
for pure shared or distributed memory models, and attempting to fit them into a
hybrid architecture could result in suboptimal performance.
Programming Complexity: Developing software for a hybrid DSM architecture can
be more challenging than for traditional shared or distributed memory systems.
Programmers need to understand both shared and distributed memory programming
paradigms, as well as the intricacies of the hybrid approach.
Resource Management: Managing the allocation and de-allocation of resources
across a hybrid DSM architecture can be complex. Balancing the allocation of
memory and processing power across local and distributed components requires
careful consideration to avoid resource contention and performance bottlenecks.
10. Using some important metrics, differentiate parallel computing with distributed CO 1.4 CL3
Computing.
Parallel computing and distributed computing are two different approaches to handling
computational tasks that involve breaking down a large problem into smaller parts.
Metrics and Parallel computing is a Distributed computing is a
Computation type computation type in which computation type in which
multiple processors execute networked computers
multiple tasks simultaneously. communicate and coordinate
the work through message
passing to achieve a common
goal.
Number of Parallel computing occurs on one Distributed computing occurs

Computers computer. between multiple computers.
Required
Processing In parallel computing multiple In distributed computing,

Mechanism processors perform processing. computers rely on message
passing.
Synchronization All processors share a single There is no global clock in

master clock for synchronization. distributed computing, it uses
synchronization algorithms.
Memory In Parallel computing, computers In Distributed computing,

can have shared memory or each computer has its own
distributed memory. memory.
Usage Parallel computing is used to Distributed computing is used

increase performance and for to share resources and to
scientific computing increase scalability.
11. In the cloud, how the ability to grow or shrink based on work load is created. Justify CO 1.6 CL1
it.
The ability of cloud resources to grow or shrink based on workload is a fundamental

characteristic of cloud computing and is known as "elasticity." This elasticity is
achieved through various technological and architectural mechanisms provided by
cloud service providers. Here's a justification of how this ability is created:
Virtualization: Cloud providers use virtualization technology to abstract physical
hardware resources (such as servers, storage, and networking) into virtual instances.
These instances can be quickly created or destroyed, allowing for dynamic resource
allocation based on demand. Virtualization decouples the logical resources from the
underlying physical infrastructure, making it easier to allocate, scale, and manage
resources as needed.
Resource Pooling: Cloud providers maintain large pools of resources, including
compute instances, storage, and networking components. These resources are shared
among multiple users and applications. This pooling enables the cloud to allocate
resources on-demand, effectively scaling up or down to accommodate varying
workloads.
Auto-scaling: Cloud platforms offer auto-scaling mechanisms that allow
applications to automatically adjust the number of resources allocated based on
predefined criteria. For example, an application's auto-scaling policy might trigger
the creation of additional virtual instances when CPU utilization exceeds a certain
threshold. Conversely, it can also scale down resources during periods of low
demand.
Orchestration and Management Tools: Cloud environments provide management
and orchestration tools that allow users to define and automate complex workflows.
These tools can be used to set up policies and rules for scaling resources in response
to changes in workload. For instance, an application might be configured to add
more instances during peak hours and reduce them during off-peak times.
Monitoring and Metrics: Cloud platforms provide monitoring and metrics services
that allow users to gather data on the performance and utilization of their resources.
This data is crucial for making informed decisions about when and how to scale
resources. Automated triggers can be set up to initiate scaling actions based on
specific metrics like CPU utilization, memory usage, network traffic, etc.
12. How does cloud computing enable the ability to increase or decrease computing CO 1.6 CL3
resources dynamically, providing the flexibility to scale up or down as needed?
Cloud computing enables the ability to increase or decrease computing resources

dynamically through the use of virtualization and resource management
technologies. This flexibility to scale up or down is a key feature of cloud
computing and provides several benefits to organizations, including cost savings,
improved performance, and enhanced resource utilization. Here's how it works:
Virtualization: Cloud providers use virtualization technologies to create virtual
instances of servers, storage, and networking resources. These virtual instances are
not tied to physical hardware but are managed by the cloud provider's infrastructure.
Elasticity: Cloud platforms offer the concept of elasticity, which allows users to
easily adjust the amount of resources allocated to their applications or workloads in
response to changing demands. This can be done manually or automatically based
on predefined rules and policies.
Auto-scaling: Many cloud platforms offer auto-scaling capabilities. With auto-
scaling, you can set up rules that define when to increase or decrease resources
based on factors like CPU utilization, memory usage, or incoming network traffic.
When predefined thresholds are reached, the cloud platform automatically adds or
removes resources to match the workload.
On-Demand Provisioning: Cloud services provide a self-service portal that allows
users to provision and deprovision resources as needed. This means you can quickly
spin up new virtual machines, storage, or other resources when demand increases,
and release them when demand decreases.
Pay-as-You-Go Model: Cloud computing often follows a pay-as-you-go model,
where you are billed based on the resources you actually consume. This aligns with
the dynamic scaling concept, as you can scale up when needed, pay for the
increased resources during that time, and then scale down when the demand
decreases to save costs.
Resource Pools: Cloud providers maintain large pools of resources that can be
allocated to different users and applications as required. This enables efficient
sharing of resources and eliminates the need to overprovision hardware to
accommodate peak loads.
Virtual Networks: Cloud platforms also offer virtual networking capabilities that
allow you to create and manage complex network architectures. This includes load
balancers that distribute incoming traffic across multiple instances, ensuring even
resource utilization and improved performance.
APIs and Automation: Cloud providers offer APIs (Application Programming
Interfaces) that allow developers to programmatically control and manage
resources. This enables automation of resource scaling based on specific conditions
or events, reducing the need for manual intervention.
Global Availability: Many cloud providers operate data centers in multiple
geographic regions. This global presence enables you to scale resources
geographically, serving users from locations that are closer to them for reduced
latency and improved performance.
PART C
1. The cloud computing paradigm is a model for delivering various computing CO 1.1 CL2
resources and services over the internet. Justify your answer with evidences.
Cloud computing is a paradigm that involves delivering various computing services
over the internet, allowing users to access and utilize resources like computing
power, storage, and applications without the need to own or manage physical
infrastructure.
 Service Models
 IaaS
 PaaS
 SaaS
 Deployment Models
 Public cloud
 Private cloud
 Hybrid cloud
 Essential Characteristics
 Empowerment
 On Demand Self-services
 Agility (Quickness)
 API
 Device and location independence
 Visualization
2 Have you felt the practical cloud in your life, based on your experience outline the CO 1.1 CL4
pros and cons of the technology?
However, I can certainly provides comprehensive overview of the pros and cons of
cloud computing based on the knowledge available.
Pros of Cloud Computing:
 Lower-Cost Computers for users
 Improved performance
 Lower IT Infrastructure Costs Fewer Maintenance Issues
 Lower Software Costs
 Instant Software Updates
 Increased Computing Power
 Unlimited Storage Capacity
 Increased Data Safety
 Improved Compatibility between Operating Systems
 Improved Document Format Compatibility
 Easier Group Collaboration
 Universal Access to Documents
 Latest Version Availability
 Removes the Tether to Specific Devices
Cons of Cloud Computing:
 Requires a Constant Internet Connection
 Does not Work Well, with Low-Speed Connections
 Can be slow
 Features might be limited
 Stored data might not be Secure
 If the Cloud loses the data, it is Screwed (No physical or local backup)
3 From its inception to the current state, what are the major milestones and CO 1.2 CL3
technological advancements that have shaped the evolutionary journey of cloud
computing, leading to its development and widespread adoption as a technology and
service?
 Cloud Computing has evolved from the Distributed system (1950s) to the
current technology. In the evolution five technologies played a vital role
they are distributed systems and its peripherals, virtualization, web 2.0,
service orientation, and utility computing.
 Evaluation diagram and explanation.
4 List out the key elements or components involved in parallel computing, and how CO 1.4 CL3
do these elements work together to execute tasks simultaneously and improve the
overall performance and efficiency of computing systems?
Parallel computing involves the simultaneous execution of multiple tasks or parts of

a task to improve performance and efficiency in computing systems.
The key elements or components involved in parallel computing are:
 Task Decomposition
 Concurrency
 Parallelism
 Parallel Hardware
 Shared Memory vs. Distributed Memory
 Threads and Processes
 Task Scheduling
 Data Parallelism
 Task Parallelism
 Communication
 Scalability
 Load Balancing:
To Improve the overall performance and efficiency of computing systems are
 Decomposition
 Parallelism:
 Synchronization:
 Communication:
 Scalability:
 Load Balancing:
5 How storage maintenance phenomena are easily handled by the multinational CO 1.4 CL3
companies using specialized architecture. Justify your answer with necessary
diagrams.
 Storage Maintenance Window Architecture diagram

 Explanation
6 How do shared and distributed memory architectures differ in parallel computing? CO 1.4 CL3
Please provide a diagram for each architecture and highlight the advantages of each
approach.
 Shared Memory Architecture
 Distributed Memory Architecture
 Explanation
 Advantages of each approach.
7. How does cloud computing differ from traditional computing models in terms of CO 1.5 CL3
distinct attributes? How do these attributes influence the capabilities and nature of
cloud-based services and infrastructure? Can you provide a relevant diagram to
illustrate these differences?
 On-Demand Self-Service
 Broad Network Access
 Resource Pooling
 Rapid Elasticity
 Measured Service
8. In the cloud, how the ability to grow or shrink based on work load is created and CO 1.6 CL2
how the ability to scale up or down based on computing resources is created. Make
it clear.
 Workload Distribution Architecture
 Explanation
UNIT – 2
CLOUD ENABLING TECHNOLOGIES
Service Oriented Architecture , REST and Systems of Systems , Web Services, Publish Subscribe Model ,
Basics of Virtualization , Types of Virtualization, Implementation Levels of Virtualization, Virtualization
Structures, Tools and Mechanisms , Virtualization of CPU, Memory, I/O Devices-Disaster Recovery-Mobile
Platform Virtualization
1 1) A message-passing taxonomy for a component-based architecture is --------------. CO2.1 CL1
a) SOA
b) EBS
c) GEC
d) All of the mentioned
2 Pickup the correct one? CO2.1 CL1
a) Service Oriented Architecture (SOA) describes a standard method for requesting
services from distributed components and managing the results
b) SOA provides the translation and management layer in an architecture that removes
the barrier for a client obtaining desired services
c) With SOA, clients and components can be written in different languages and can use
multiple messaging protocols
3 In a business process, which one is a repeatable task? CO2.1 CL1
a) service
b) bus
c) methods
d) all of the mentioned
4 Which of the following module of SOA is shown in the following figure? CO2.1 CL1
a) Description
b) Messaging
c) Business Process
d) QOS
5 Point out the wrong statement. CO2.1 CL1
a) SOA provides the standards that transport the messages and makes the infrastructure
to support it possible
b) SOA provides access to reusable Web services over an SMTP network
c) SOA offers access to ready-made, modular, highly optimized, and widely shareable
components that can minimize developer and infrastructure costs
d) None of the mentioned
6 The ------------- algorithm is used by Google to determine the importance of a particular CO2.2 CL1
page.
a) SVD
b) PageRank
c) FastMap
7 Which of the following protocol lets a Web site list in XML file information? CO2.2 CL1
a) Sitemaps
b) Mashups
c) Hashups
8 Google product sends a periodic email alerts based on the search term. CO2.2 CL1
a) Alerts
b) Blogger
c) Calendar
9 Which of the following is a payment processing system by Google? CO2.2 CL1
a) Paytm
b) Checkout
c) Code
10 ------------- type of virtualization is also the characteristic of cloud computing. CO2.3 CL1
a) Storage
b) Application
c) CPU
a) Abstraction enables the key benefit of cloud computing: shared, ubiquitous access
b) Virtualization assigns a logical name for a physical resource and then provides a
pointer to that physical resource when a request is made
c) All cloud computing applications combine their resources into pools that can be
assigned on demand to users
12 The technology used to distribute service requests to resources is referred to as CO2.3 CL1
_____________
a) load performing
b) load scheduling
c) load balancing
13 Another name for the system virtual machine is CO2.4 CL1

a) hardware virtual machine
b) software virtual machine
c) real machine
d) none of the mentioned
14 Which of the following provide system resource access to virtual machines? CO2.4 CL1
a) VMM
b) VMC
c) VNM
15 Point out the correct statement. CO2.4 CL1
a) A virtual machine is a computer that is walled off from the physical computer that the
virtual machine
is running on
b) Virtual machines provide the capability of running multiple machine instances, each
with their own operating system
c) The downside of virtual machine technologies is that having resources indirectly
addressed means there is some level of overhead
16 An operating system running on a Type ______ VM is full virtualization. CO2.5 CL1
a) 1
b) 2
c) 3
17 Type 2 VM is -------------. CO2.5 CL1
a) VirtualLogix VLX
b) VMware ESX
c) Xen
d) LynxSecure
18 ------------------- should be placed in second lowermost layer for the following figure. CO2.5 CL1
a) Host Operating System
b) Software
c) VM
19 which of the following allows a virtual machine to run on two or more CO2.6 CL1
physical processors at the same time ?
A. virtual smp
B. distributed resource scheduler
C. network distributed switch
D. storage vmotion
hich of the following allows a virtual machine to run on two or more
physical processors at the same time ?
A. virtual smp
B. distributed resource scheduler
C. vnetwork distributed switch
D. storage vmotion
If virtualization occurs at application level, OS level and hardware level, then such
service in cloud is
a) Iaas
b) Saas
c) Paas
d) No such service
20 Order of virtual Machine Life Cycle i) Release Msii)IT Service Request iii)VM in CO2.6 CL1
operationiv) VM provision
a) ii,i,iii,iv
b) i,ii,iii,iv
c) ii,iii,iv,i
d) ii,iv,iii,i
21 Where a VM can be moved from one physical machine to another even as it continues to CO2.6 CL1
execute
a) load balancing
b) migration
c) live migration
d) None of the mentioned.
22 Which of the following type of virtualization is found in hyper such as Microsoft;s CO2.7 CL1
Hyper V ?
a) Para Virtualization
b) Full virtualization
c) Emulation
d) None of the above mentioned.
23 The -----------------operating system supports virtualization. CO2.7 CL1
a) Windows NT
b) Sun Solaris
c) Windows Xp
d) Compliance
24 Which of the following allows a virtual machine to run on two or more physical CO2.8 CL1
processor at the same time?
a) Virtual smp
b) Distributed resource scheduler
c) Vnetwork distributed switch
d) Storage V motion
25 VMM facilitates sharing OF CO2.8 CL1
a) Memory & i/o
b) Cpu, memory &i/o
c) Cpu& memory
d) i/o &cpu
26 Which one is generally NOT changed after virtualization? CO2.8 CL1
a) Virtual machines can be provisioned to any system
b) Hardware- independence of operating system and applications
c) Can manage os application as a single unit by encapsulating them into virtual
machine
d) Software and hardware tightly coupled
27 The BEST way to define virtualization in cloud computing is CO2.9 CL1
a) Virtualization enables simulating compute , network, and storage service
platforms from underlying virtual hardware
b) Virtualization enables abstracting compute, network and storage services
platforms from underlying physical hardware
c) Virtualization enables realization of compute , network , and storage service
platforms from under virtual hardware
d) Virtualization enables enables emulating compute , network and storage service
platforms from under virtual hardware
28 Which of the following correctly represents different types of mobile patterns? CO2.10 CL1
e) All of the mentioned

Ans :a
29 A ______ is a combination load balancer and application server that is a server placed CO2.10 CL1
between a firewall or router.
a) ABC
b) ACD
c) ADC
30 Which of the following network resources can be load balanced? CO2.10 CL1
a) Connections through intelligent switches
b) DNS
c) Storage resources
S.No PART-B CO CL
1. Could you explain the find-bind-execute paradigm architecture and provide a CO 2.1 CL2
diagram that outlines its key elements?
2. Which constraint of RESTful APIs limits the scope of network optimization, and CO 2.2 CL2
what is the rationale behind this constraint? provide a detailed explanation to
understand its impact on network optimization.
The constraint of "statelessness" in RESTful APIs limits the scope of network

optimization, and its rationale lies in the design philosophy of REST and the
principles of scalability, simplicity, and reliability. Let's delve into a detailed
explanation of this constraint and its impact on network optimization.
Statelessness in RESTful APIs:
Statelessness means that each client request to a server must contain all the
information necessary to understand and process the request. The server should
not rely on any information from previous requests to understand the current one.
In other words, the server does not maintain any "state" about the client's
interactions.
3. What are the various HTTP verbs that are used to indicate actions, and can you CO 2.3 CL3
provide an explanation of how each of these verbs is used in the context of HTTP
requests
A web application should be organized into resources like users and then uses
HTTP verbs like – GET, PUT, POST, DELETE to modify those resources.
In order to use PUT and DELETE you will need to install method override. You
can do this by following below code:
npm install method-override --save
This simply require this package in your code by writing :
var methodOverride = require("method-override");
Now you can easily use PUT and DELETE routes :
app.use(methodOverride("_method"));
4. What are the fundamental principles that underpin the pub/sub paradigm of CO 2.3 CL2
event-driven architecture? Please provide an outline to understand the key
principles of this approach
 Scalability. Event-Driven Architectures(EDAs) allow for great
horizontal scalability as one event may trigger responses from multiple
systems with different needs and providing different results.
 Loose coupling. There is an intermediary that receives events, processes
them, and sends them to the systems interested in specific events. This
allows for loose coupling of services and facilitates their modifying,
testing, and deployment. And unlike point-to-point system integrations,
components can be easily added to or removed from a system..
5. Using which technology, you will share a single physical instance of a resource CO 2.5 CL2
among multiple tenants? Briefly outline that technology
One technology that allows sharing a single physical instance of a resource
among multiple tenants is Virtualization.
Virtualization involves creating virtual instances of computing resources, such as
servers, storage, or networks, on a single physical machine. These virtual
instances, often called virtual machines (VMs), can run multiple operating
systems and applications simultaneously, isolated from each other.
6. Could you list and describe the key features of Virtualization? An outline of these CO 2.5 CL3
principles will help in understanding the core concepts of this approach.
 Abstraction:
 Isolation
 Resource Pooling
 Hardware Independence:
 Benefits of Virtualization
7. In which different categories can virtualization types be classified? Please CO 2.6 CL1
mention the categories that encompass various types of virtualization
8. Analyze the different aspects of I/O virtualization to understand its significance CO 2.7 CL3
in virtualized environments.
There are three ways to implement I /O virtualization: full device emulation,
para-virtualization, and direct I /O.
• I/O virtualization. Generally, this approach emulates well-known, real-
world devices. All the functions of a device or bus infrastructure, such as
device enumeration, identification, interrupts, and DMA, are replicated
in software. This software is located in the VMM and acts as a virtual
device.
• The para-virtualization method of I /O virtualization is typically used in
Xen. It is also known as the split driver model consisting of a frontend
driver and a backend driver. It achieves beer device performance than
full device emulation, it comes with a higher CPU overhead
• Direct I /O virtualization lets the VM access devices directly. It can
achieve close-to native performance without high CPU costs.
9. How do modern operating systems offer virtual memory support, and could you CO 2.8 CL1
explain the concept in detail?
• Memory virtualization is similar to the virtual memory support provided
by modern operating systems. In a traditional execution environment,
the operating system maintains mappings of virtual memory to machine
memory using page tables, which is a one-stage mapping from virtual
memory to machine memory.
• However, in a virtual execution environment, virtual memory
virtualization involves sharing the physical system memory in RAM and
dynamically allocating it to the physical memory of the VMs.
• That means a two-stage mapping process should be maintained by the
guest OS and the VMM, respectively: virtual memory to physical
memory and physical memory to machine memory.
10. What are the advantages of virtualization at different implementation levels? CO 2.9 CL 2
Provide a list of the merits associated with virtualization in various contexts.
Common virtualization layers include

1. Instruction Set Architecture (ISA) level.
2. Hardware Abstraction Layer (HAL) level.
3. Operating System level.
4. Library Support level and
5. Application level.
11. What is the role of para-virtualization in the implementation of virtualization, and CO 2.10 CL2
how does this concept contribute to the virtualization of computing systems?
• Involves explicitly modifying guest operating system (e.g. SUSE Linux
Enterprise Server 11) so that it is aware of being virtualized to allow
near native performance.
• Improves performance.
• Lower overhead.
• E.g.: Xen supports both Hardware Assisted Virtualization (HVM) and
Para-Virtualization (PV).
12. Could you list and analyze the various types of hypervisors that are considered CO 2.11 CL1
essential components of hardware virtualization?
• A hypervisor is a hardware virtualization technique allowing multiple
operating systems, called guests to run on a host machine. This is also
called the Virtual Machine Monitor (VMM). Both perform the same
virtualization operations.
• Depending on the position of the virtualization layer, there are two
different structure of virtualization, namely Bare Metal Virtualization
and Hosted Virtualization.
13. How does the implementation of virtualization play a role in enhancing disaster CO 2.12 CL1
recovery efforts? Please explain how virtualization technology contributes to
disaster recovery and its benefits in such scenarios.
 Virtual disaster recovery is a type of Disaster Recovery (DR) that
typically involves replication and enables a user to fail over to
virtualized workloads.
 Disaster recovery is an organization’s method of regaining access and
functionality to its IT infrastructure after events like a natural disaster
and cyber attack.
Virtual disaster recovery:
 Virtual disaster recovery refers to the use of virtualized workloads for
disaster recovery planning and failover. To achieve this, organizations
need to regularly replicate workloads to an offsite virtual disaster
recovery site.
14. What are the major differences between virtual disaster recovery and physical CO 2.12 CL3
disaster recovery? Could you provide an in-depth comparison of the
implementation, advantages, and limitations of these two approaches to disaster
recovery
 Virtual disaster recovery involves replicating and recovering virtual
machines (VMs) and data from a primary data center to a secondary or
remote location. This is typically achieved using technologies like
hypervisor-based replication or software-defined storage solutions. The
virtual environment allows for more flexibility and agility in managing
and recovering workloads.
 Physical disaster recovery involves replicating and recovering physical
servers and hardware from a primary data center to a secondary site.
This typically involves creating an exact duplicate of the primary
environment in the secondary location, often using hardware-based
replication methods.
PART C
1. How does Service-Oriented Architecture (SOA) ensure functional aspects such as CO 2.1 CL2
service composition, service invocation, and service discovery? Additionally,
could you outline the importance of quality aspects like scalability, flexibility,
and security in a SOA environment, and how they contribute to the success of the
architecture?
 Service Oriented Architecture
 Components of SOA
 Characteristics of SOA
 Advantages of SOA
2. Flip-kart provides a service that displays the prices of items offered on CO 2.2 CL4
Flipkart.com. The presentation layer can be written in Java, but the service can be
communicated using a programming language. Identify and explain the service
with Features.
Using the following SOAP format construct the list
POST /StockPrice HTTP/1.1 Host : www.sample.com
Content-Type: application/soap+xml; charsetutf-8 Content-Length: <Size>
<?xml version= “1.0”>
<soap: Envelope xmlns:soap= “http://www.w3.org/2001/12/soap-envelope”
soap:encodingStyle= “http://www.w3.org/2001/12/soap-enoding” >
<soap:Header></soap:Header>
<soap:Body xmlns=http://www.sample.com/stock>
<m:GetPriceResponse>
<m: Price>58.5</m:Price>
</m:GetPriceResponse>
</soap:Body>
</soap: Envelope>
3. In the context of the publish-subscribe model, what is the significance of topics CO 2.2 CL3
and subscriptions? How do these concepts enable selective message distribution
to interested subscribers? Provide examples of topics and subscriptions to
illustrate their role in facilitating efficient message delivery to specific groups of
subscribers.
 Publish-Subscribe Model
 Architectural design
4. Explain the different levels of virtualization in detail by providing a suitable CO 2.6 CL2
diagram for each level of virtualization to illustrate how it works and its key
components. Additionally, highlight the advantages and use cases of each type of
virtualization in modern computing environments.
 Common virtualization layers include
 Instruction Set Architecture (ISA) level.
 Hardware Abstraction Layer (HAL) level.
 Operating System level.
 Library Support level and
 Application level.
5. Based on the position of the virtualization layer, virtualization is classified into CO 2.8 CL2
different structures. Distinguish the structure with necessary diagrams
A hypervisor is a hardware virtualization technique allowing multiple operating

systems, called guests to run on a host machine. This is also called the Virtual
Machine Monitor (VMM). Both perform the same virtualization operations.
Depending on the position of the virtualization layer, there are two different
structure of virtualization, namely Bare Metal Virtualization and Hosted
Virtualization.
6. Design the functionality of GNU/Linux based project developed for x86 CO 2.9 CL2
machines using virtualization and outline the important features also.
 Kernel-Based Virtual Machine
KVM Features are

 Quick EMUlator(QEMU) Monitor Protocol
 Kernal Same page merging
 KVM para-virtual clock
 CPU hot plug Support
 PCI hot plug Support
 VM Channel
 Migration
 SCSI Disk Emulation
 Virtio Devices
 CPU clustering
7. How does disaster recovery benefit from virtualization technologies? Could you CO 2.9 CL3
elaborate on how virtualization enables efficient disaster recovery strategies, such
as backup and replication, failover, and rapid restoration of services after a
disaster event? Provide examples of how virtualization plays a crucial role in
disaster recovery planning and implementation
 Virtual disaster recovery:
 Creation of A Robust Disaster Recovery Plan
 Data Recovery After a Disaster
 Future-Proofing the Business
8. Can you explain the architecture of Xen, a popular open-source hypervisor? How CO 2.9 CL2
does Xen provide virtualization capabilities, and what are the key components in
its architecture? Describe how Xen enables multiple virtual machines (VMs) to
run on a single physical machine and how it interacts with the underlying
hardware
 XEN Virtualization
 XEN Virtualization Architecture Diagram
UNIT-III
CLOUD ARCHITECTURE, SERVICES AND STORAGE
Layered Cloud Architecture Design , NIST Cloud Computing Reference Architecture , Public, Private and
Hybrid Clouds , laaS, PaaS, SaaS, Architectural Design Challenges , Cloud Storage , Storage-as-a-Service,
Advantages of Cloud Storage, Cloud Storage Providers – S3-A Case Study: The Grep TheWeb Application
SL.NO PART – A CO CL
1 Which of the following layer of Wolf platform architecture is depicted in the CO3.1 CL1
following figure?
a) upper
b) middle
c) lower
2 -----------------Instrumentation tool displays the real-time parameters of the CO3.1 CL1
application in a visual form in AppBase?
a) Security Roles Management
b) Dashboard Designer
c) Report Builder
a) SquareSpace is used in major Websites and organizes vast amounts of
information
b) LongJump creates browser-based Web applications that are database-
enabled
c) LongJump extends Python and uses a Model-View-Controller architecture
(MVC) for its framework
4 The architectural layer used as a front end in cloud computing is CO3.2 CL1
a) client
b) cloud
c) soft
5 _________ is a cloud computing service model in which hardware is virtualized CO3.2 CL1
in the cloud.
a) IaaS
b) CaaS
c) PaaS
6 -------------------is called hypervisor. CO3.3 CL1
a) VGM
b) VMc
c) VMM
7 Amazon Machine Images are virtual appliances that have been packaged to run CO3.3 CL1
on the grid of ____ nodes.
a) Ben
b) Xen
c) Ken
d) Zen
8 Which of the following is the fundamental unit of virtualized client in an IaaS CO3.3 CL1
deployment?
a) workunit
b) workspace
c) workload
9 A third-party VPN based on Google’s googleTalk is CO3.4 CL1
a) Hotspot VPN
b) Gbridge
c) AnchorFree Hotspot Shield
10 Which of the following is associated with considerable vendor lock-in? CO3.4 CL1
a) PaaS
b) IaaS
c) CaaS
d) SaaS
11 _____ offering provides the tools and development environment to deploy CO3.4 CL1
applications on another vendor’s application.
a) PaaS
b) IaaS
c) CaaS
12 Amazon Web Services offers a classic Service Oriented Architecture (SOA) CO3.4 CL1
approach to ______________
a) IaaS
b) SaaS
c) PaaS
a) Platforms can be based on specific types of development languages,
application frameworks, or other constructs
b) SaaS is the cloud-based equivalent of shrink-wrapped software
c) Software as a Service (SaaS) may be succinctly described as software that is
deployed on a hosted service
14 _________ as a Service is a cloud computing infrastructure that creates a CO3.5 CL1
development environment upon which applications may be build.
a) Infrastructure
b) Service
c) Platform
15 _________ serves as a PaaS vendor within Google App Engine system. CO3.5 CL1
a) Google
b) Amazon
c) Microsoft
16 Which of the following can be considered PaaS offering? CO3.5 CL1
a) Google Maps
b) Gmail
c) Google Earth
17 Rackspace Cloud Service is an example of _____________ CO3.5 CL1
a) IaaS
b) SaaS
c) PaaS
18 Which of the following aspect of the service is abstracted away? CO3.5 CL1
a) Data escrow
b) User Interaction
c) Adoption drivers
19 Open source software used in a SaaS is called _______ SaaS. CO3.5 CL1
a) closed
b) free
c) open
20 The componentized nature of SaaS solutions enables many solutions to support CO3.6 CL1
a feature called _____________
a) workspace
b) workloads
c) mashups
21 A storage data interchange interface for stored data objects is CO3.6 CL1
a) OCC
b) OCCI
c) OCMI
a) To determine whether your application will port successfully, you should
perform a functionality mapping exercise
b) Cloud computing supports some application features better than others
c) Cloud bursting is an overflow solution that clones the application to the cloud
and directs traffic to the cloud during times of high traffic
23 ________ data represents more than 50 percent of the data created every day. CO3.6 CL1
a) Shadow
b) Light
c) Dark
24 Cloud storage data usage in the year 2020 is estimated to be _____________ CO3.6 CL1
percent resident by IDC.
a) 10
b) 15
c) 20
25 A system does not provision storage to most users is CO3.7 CL1
a) PaaS
b) IaaS
c) CaaS
d) SaaS
26 Which of the following storage devices exposes its storage to clients as Raw CO3.7 CL1
storage that can be partitioned to create volumes?
a) block
b) file
c) disk
27 Impose additional overhead on clients and offer faster transfer is CO3.7 CL1
a) Block storage
b) File Storage
c) File Server
a) Virtual private servers can provision virtual private clouds connected through
virtual private networks
b) Amazon Web Services is based on SOA standards
c) Starting in 2012, Amazon.com made its Web service platform available
to developers on a usage-basis model
29 The central application in the AWS portfolio is CO3.8 CL1
a) Amazon Elastic Compute Cloud
b) Amazon Simple Queue Service
c) Amazon Simple Notification Service
d) Amazon Simple Storage System
30 Which of the following feature is used for scaling of EC2 sites? CO3.8 CL1
a) Auto Replica
b) Auto Scaling
c) Auto Ruling
SL.NO PART – B CO CL
1. Are there any specific tools, frameworks, or methodologies recommended for CO3.1 CL2
implementing Layoured Cloud Architecture effectively?If so, point out the
design of architecture.
Answer
Cloud computing is made up of a variety of layered elements, starting at
physical layer of storage and server infrastructure and working up through the
application and network layers.
The three cloud layers are,
 Information cloud
 Content cloud
 Infrastructure cloud
Infrastructure cloud layer: Abstracts applications from servers and servers
from storage. An infrastructure cloud layer includes the physical components
that run applications and store data.
Data center Layer: is the sub-layer of Infrastructure cloud layer. In a cloud
environment, this layer is responsible for Managing Physical Resources such
as servers, switches, routers, power supplies, and cooling systems. Providing
end users with services requires all resources to be available and managed in
data centres.
Physical servers connect through high-speed devices such as routers and
switches to the data centre.
Content cloud layer: Abstracts data from applications. The content cloud
implements metadata and indexing services over the infrastructure cloud.
Information cloud layer: Abstracts access from clients to data. For example,
a user can access data stored in a database in Singapore via a mobile phone,
watch a video located on a server in Japan from a laptop. The information
cloud abstracts everything from everything. Such a internet is an information
cloud
2 Two NIST Cloud service management requirements related to Service Level CO3.2 CL2
Agreements (SLAs) and accountability, and explain how SLAs help customers
gain assurance about the quality and availability of cloud services while
holding providers accountable for meeting specified performance metrics and
support response times.
Cloud Service Management:
Cloud service management includes all of the service-related functions that are
necessary for the management and operation of services.
Cloud service management can be described through the following
requirements.
Business support - deals with clients and supporting processes.
Provisioning and configuration - is the process of setting up the infrastructure.
Portability and interoperability - relate to the ability to build systems from
reusable components.
3. How does the Community Cloud model address data sovereignty concerns for CO3.3 CL2
government agencies, and what measures are in place to ensure the
confidentiality, integrity, and availability of sensitive government data within
this cloud environment?
Answer
A community cloud serves a group (community) of Cloud Consumers which
have shared concerns such as mission objectives, security, and privacy.
 Community cloud may be managed by
o The organizations (Or)
o By a third party
 May be implemented
o On customer premises (i.e. on-site community cloud) (Or)
o Off Premises
Community clouds are distributed systems created by integrating the services
of different clouds to address the needs of an industry, a community, or a
business sector.
or
Data Residency and Geographical Control: Community Cloud providers allow
government agencies to choose specific geographic regions where their data will be
stored and processed. This capability ensures that the data remains within the
jurisdiction or geographical boundaries defined by the government, helping to address
data sovereignty concerns.
Isolation and Segregation: In a Community Cloud environment, resources are isolated
and shared only among the members of the authorized community. This segregation
prevents unauthorized access and data leakage between different organizations,
providing an additional layer of data protection.
Enhanced Security Measures: Community Cloud providers implement robust security
measures, such as encryption, secure authentication mechanisms, and multi-factor
authentication, to safeguard sensitive government data from unauthorized access and
cyber threats.
Compliance with Regulatory Standards: Community Cloud providers are typically
compliant with industry-specific and government-specific regulations, certifications,
and standards. For instance, they may adhere to regulations like FedRAMP, HIPAA, or
GDPR, depending on the nature of the community's data and operations.
Data Backup and Disaster Recovery: Regular data backups and disaster recovery
mechanisms are put in place to ensure data availability and integrity. These measures
help recover data in case of accidental loss or disasters, minimizing downtime and data
loss.
Auditing and Transparency: Community Cloud providers often offer transparency
into their security practices, policies, and procedures. Government agencies can
perform audits and review security controls to ensure compliance and assess the overall
security posture.
Customizable Security Policies: The Community Cloud model allows government
agencies to tailor security policies and access controls to align with their specific
requirements and compliance needs. This level of customization enhances the control
and protection of sensitive data.
Service Level Agreements (SLAs): SLAs between the government agencies
and the Community Cloud provider define the agreed-upon levels of service,
performance, and security. SLAs ensure that the cloud provider is accountable
for meeting the expectations of the government agencies.
Continuous Monitoring and Incident Response: Community Cloud
providers employ continuous monitoring and proactive incident response
practices to detect and address security threats promptly.
Data Deletion and Disposal Policies: Providers implement secure data
deletion and disposal procedures to ensure that sensitive government data is
appropriately handled at the end of its lifecycle, minimizing the risk of data
exposure.
4. Mention the key features of a cloud service optimized for economic purposes CO3.4 CL2
using bursting. Include details about its architecture, scalability, cost-
effectiveness, integration, data consistency, monitoring, and security.
Architecture and Scalability:
 The cloud service architecture is built to support elastic scaling,
allowing it to dynamically adjust resources based on demand
fluctuations.
 Bursting capabilities enable the service to scale up or down rapidly,
ensuring it can handle both regular workloads and unexpected traffic
spikes.
Cost-Effectiveness:
 The cloud service operates on a pay-as-you-go model, meaning
customers are only charged for the resources they consume during
bursting events.
 During normal periods of low demand, the service scales back to its
baseline resources, minimizing costs.
Integration and Compatibility:
 The cloud service is designed to integrate seamlessly with various
applications and platforms, enabling smooth migration and adoption.
 Compatibility with popular programming languages and development
frameworks ensures easy deployment and management.
Data Consistency:
 Data consistency is maintained through robust replication and
synchronization mechanisms, ensuring that data remains coherent
across the entire application stack.
 Bursting events do not compromise data integrity, and data updates
are applied consistently.
Monitoring and Resource Management:
 The cloud service includes comprehensive monitoring and resource
management tools to track performance and resource utilization.
 Bursting triggers can be set based on configurable thresholds to
automatically scale resources as needed.
Security and Compliance:
 The cloud service implements industry-standard security practices,
encryption, and access controls to protect data and applications from
unauthorized access and cyber threats.
 Compliance with relevant regulations and standards is assured to meet
security and privacy requirements.
Auto-Scaling Policies:
 Auto-scaling policies are configured to govern resource adjustments
during bursting events. These policies may be based on factors like
CPU utilization, network traffic, or custom metrics.
 Bursting capacity can be scaled up or down based on predefined rules,
ensuring efficient resource allocation.
Resource Quotas and Limits:
 The cloud service allows users to set resource quotas and limits to
control spending during bursting periods.
 Administrators can define maximum resource limits to prevent
unexpected cost overruns.
Fault Tolerance and High Availability:
 The cloud service is designed to be fault-tolerant and highly available,
ensuring minimal service disruption during scaling events or potential
hardware failures.
Bursting Analytics and Reporting:
The cloud service offers analytics and reporting features to help users analyze
usage patterns, predict potential bursting events, and optimize resource
planning.
5. Analyze that vendor-neutral cloud service aggregator enable multi-cloud CO3.5 CL3
integration, automated scaling, load balancing, and backup for diverse cloud
providers while ensuring robust security, seamless application portability, and
comprehensive analytics within a unified interface integrated with APIs and
DevOps tools?
Multi-Cloud Integration:
The aggregator seamlessly integrates with various cloud providers, allowing
organizations to manage their resources and workloads from different clouds
through a single interface. This streamlines operations and reduces the need for
managing multiple cloud consoles.
Automated Scaling and Load Balancing:

The aggregator offers automated scaling capabilities that dynamically adjust
resources based on real-time demand. It ensures that applications can handle
varying workloads efficiently while optimizing resource utilization.
Load balancing is enabled to distribute incoming network traffic across
multiple cloud instances, ensuring high availability and performance.
Backup and Disaster Recovery:

The aggregator provides robust backup and disaster recovery solutions,
enabling organizations to safeguard their data and applications across diverse
cloud providers. It ensures data redundancy and facilitates quick recovery in
case of outages or data loss.
Security and Compliance:

Robust security features, including encryption, access controls, and identity
management, are integrated into the aggregator. It ensures data protection and
compliance with industry and regulatory standards across all connected cloud
providers.
Seamless Application Portability:

The aggregator supports application portability, allowing organizations to
deploy and migrate applications across different cloud providers easily. This
flexibility reduces vendor lock-in and fosters a competitive cloud market.
Comprehensive Analytics:
The aggregator provides extensive analytics and monitoring capabilities,
consolidating performance metrics and usage data from all connected cloud
providers. This centralized view enhances operational visibility and enables
informed decision-making.
Unified Interface with APIs and DevOps Tools:

The aggregator offers a single unified interface that simplifies cloud
management tasks for administrators and developers. It provides APIs and
DevOps tool integrations, promoting automation and facilitating infrastructure-
as-code practices.
Resource Optimization and Cost Management:

The aggregator helps optimize resource allocation across multiple clouds,
identifying cost-saving opportunities and suggesting efficient cloud
6. To which cloud computing service model does Amazon EC2 belong, and how CO3.6 CL3
does it align with the principles of that model, including resource provisioning,
self-service, elasticity, pay-as-you-go billing, virtualization, API access, and
rapid deployment?
Resource Provisioning:
Amazon EC2 provides virtualized compute resources in the form of instances,
which include CPU, RAM, and storage. Users can choose from a wide range
of instance types based on their specific performance requirements.
Self-Service:
EC2 offers self-service provisioning, enabling users to quickly create,
configure, and manage instances through the AWS Management Console,
command-line interface (CLI), or API calls without requiring human
intervention from AWS staff.
Elasticity:
EC2 instances can be easily scaled up or down to handle varying workloads.
Users can add or remove instances as needed to match demand, ensuring that
resources align with the current workload.
Pay-as-You-Go Billing:
Amazon EC2 follows a pay-as-you-go billing model, where users are charged
based on the actual resources consumed. This allows for cost optimization as
users only pay for the instances they use and the time they use them.
Virtualization:
EC2 leverages virtualization technology to create and manage instances. It
uses the Xen hypervisor to virtualize hardware resources, allowing multiple
instances to run on a single physical server.
API Access:
Amazon EC2 offers a comprehensive set of APIs that enable developers to
programmatically create, configure, and manage instances. The API access
allows for integration with various tools and automation of infrastructure
management.
Rapid Deployment:
EC2 enables rapid deployment of instances, reducing the time required to set
up and provision new servers. With pre-configured Amazon Machine Images
(AMIs) and templates, users can quickly launch instances with desired
software and configurations.
7. Could you provide a brief comparison of the key characteristics of CO3.7 CL2
Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software
as a Service (SaaS) in terms of the services utilized by customers?
Infrastructure as a Service (IaaS):

Customer Utilized Services: In IaaS, customers have access to
virtualized computing resources, such as virtual machines (VMs), storage, and
networking components. Customers are responsible for managing the
applications, data, runtime, and middleware.
Platform as a Service (PaaS):

Customer Utilized Services: In PaaS, customers gain access to a
complete development and deployment environment. This includes the
underlying infrastructure, operating system, middleware, and development
tools. Customers can focus on application development and deployment, while
the platform manages the underlying infrastructure.
Software as a Service (SaaS):

Customer Utilized Services: In SaaS, customers access and use fully
functional applications that are hosted and managed by the provider.
Customers do not need to worry about managing the infrastructure, operating
system, or application software; they simply use the application through a web
browser or app interface.
8. In the rapidly evolving cloud landscape, How can architects effectively CO3.7 CL2
manage and monitor the various components and resources within a cloud
architecture to ensure optimal performance and resource utilization?
Automated Provisioning and Orchestration:

Use automation tools and infrastructure-as-code (IaC) practices to provision
and manage cloud resources. Tools like Terraform or AWS CloudFormation
allow architects to define and deploy resources in a consistent and repeatable
manner.
Cloud Resource Tagging and Naming Conventions:

Establish well-defined tagging and naming conventions for cloud resources.
Tags can be used to categorize resources, enabling easier tracking, cost
allocation, and management.
Continuous Monitoring and Alerting:

Implement continuous monitoring of cloud resources using monitoring and
alerting services such as Amazon CloudWatch, Azure Monitor, or Google
Cloud Monitoring. Set up alerts to notify teams about performance issues,
resource bottlenecks, and potential security risks.
Resource Right-Sizing and Optimization:

Regularly analyze resource utilization and identify opportunities for right-
sizing instances or resources. Use cloud cost management tools to optimize
spending without sacrificing performance.
Scaling and Load Balancing Strategies:

Implement automatic scaling and load balancing mechanisms to ensure
resources are dynamically adjusted based on demand. This ensures optimal
performance during traffic spikes while avoiding unnecessary costs during
periods of low utilization.
Cloud Cost Management:

Monitor and manage cloud costs closely. Leverage cloud cost management
tools to track spending, set budgets, and analyze cost trends. Optimize cloud
spending by identifying cost-saving opportunities.
Performance Testing and Optimization:

Conduct regular performance testing and optimization exercises to identify
bottlenecks and improve application and infrastructure performance. Load
testing can help simulate various scenarios and ensure that the cloud
architecture can handle peak loads.
Security and Compliance Monitoring:

Implement robust security measures and monitoring to detect potential security
breaches. Utilize cloud-native security tools and third-party solutions to
enhance security posture and ensure compliance with industry standards.
Centralized Logging and Auditing:

Set up centralized logging and auditing of cloud resources to maintain
visibility into system activities and troubleshoot issues effectively.
Continuous Learning and Training:

Encourage continuous learning and training for architects and IT teams to stay
updated with the latest cloud technologies, best practices, and industry trends.
9. Which feature of this cloud storage provider enables users to preserve, retrieve, CO3.8 CL2
and restore previous versions of objects, providing additional data protection
and recovery capabilities?
Versioning is a critical feature in cloud storage services like Amazon S3

(Simple Storage Service), Microsoft Azure Blob Storage, and Google Cloud
Storage. When versioning is enabled for a bucket/container, the cloud provider
automatically keeps track of all object versions uploaded to that storage.
Instead of overwriting objects, each modification creates a new version of the
object, allowing users to access previous versions when needed.
Data Protection and Recovery:
Versioning enhances data protection by preserving multiple versions of
objects. In case of accidental deletions, data corruption, or human errors, users
can recover previous versions, reducing the risk of data loss.
Version Management:
Users can list all versions of an object, including the current version and any
previous versions. This provides granular control over data retrieval and
restoration.
Versioning Options:
Some cloud storage providers offer configuration options for versioning. Users
can choose to enable versioning at the bucket/container level, or they can
disable versioning for specific objects if versioning is not required for certain
data.
Object Lifecycle Policies:
Versioning can work in conjunction with object lifecycle policies, allowing
users to define rules for object deletion and archival. For example, you can
specify that previous versions of objects should be automatically deleted after
a certain period or moved to a long-term archival storage tier.
Storage Costs Consideration:
It's important to consider the storage costs associated with versioning, as
keeping multiple versions of objects consumes additional storage space.
However, versioning can be valuable for critical data or regulatory compliance
purposes.
10. In a cloud storage system with horizontal scalability, how does geographical CO3.8 CL2
distribution of nodes improve performance and reduce latency for users in
different regions?
Proximity to Users:
By having data centers closer to end users, the physical distance between users
and their nearest data center is minimized. This proximity reduces the time it
takes for data to travel back and forth, leading to lower latency and faster data
access.
Data Replication and Redundancy:

Geographical distribution enables data replication across multiple data centers.
This redundancy ensures data availability even if one data center experiences
an outage or becomes unreachable. Users can access their
data from a different, nearby data center.
Load Balancing and Traffic Management:

Distributed storage systems often employ load balancing and traffic
management techniques to route user requests to the nearest data center with
available capacity. This load distribution optimizes resource utilization and
prevents overloading of specific nodes.
Content Delivery Networks (CDNs):

Some cloud storage systems integrate with Content Delivery Networks
(CDNs) to cache and serve frequently accessed data from edge servers located
in various geographic regions. CDNs reduce latency by serving data from edge
nodes closest to users.
Global Content Availability:
Geographical distribution allows data to be replicated and cached globally.
This availability ensures that users from different regions can access content
with minimal delay, regardless of where the original data was stored.
Compliance with Data Regulations:

Distributed storage systems enable cloud providers to adhere to data
sovereignty and regulatory requirements. By storing data in data centers
located within specific regions, providers can ensure compliance with local
data storage and privacy laws.
Disaster Recovery and High Availability:

Geographical distribution enhances disaster recovery capabilities. In the event
of a regional outage or natural disaster, data can be quickly restored from other
regions, ensuring high availability and business continuity.
Reduced Network Congestion:

Geographical distribution helps distribute traffic across the network, reducing
congestion and improving overall network performance for users in different
regions.
11. Through which distribution channels does the company offer its storage plans CO3.9 CL3
and facilitate customer sign-ups and payments? How does the company build
and maintain customer relationships, including on boarding, technical support,
and regular communication?
Distribution Channels and Sign-Ups:

Website: Cloud storage providers usually offer storage plans directly through
their official websites. Customers can sign up for an account, choose a plan,
and complete the payment process online.
Mobile Apps: Many cloud storage providers have mobile applications
available on various platforms (iOS, Android) where users can sign up for
services and manage their storage plans conveniently through their
smartphones or tablets.
Resellers and Partners: Some cloud storage providers offer their services
through resellers and partners. These partners may include technology vendors,
system integrators, and managed service providers that bundle cloud storage
services with their offerings.
Marketplaces and App Stores: Cloud storage providers may also offer their
services through online marketplaces and app stores, such as the AWS
Marketplace or Google Cloud Marketplace.
Building and Maintaining Customer Relationships:
Onboarding and Training: Cloud storage providers focus on providing

seamless onboarding experiences to new customers. They often offer tutorials,
documentation, and training resources to help users get started with the
service.
Technical Support: Customer support is crucial in maintaining a strong
relationship. Cloud storage providers offer various support channels, such as
email, chat, and phone, to assist customers with technical issues and inquiries.
Regular Communication: Providers maintain regular communication with
customers through newsletters, updates, and product announcements. This
helps customers stay informed about new features, enhancements, and any
service-related information.
Community Forums: Many cloud storage providers host community forums
where customers can engage with other users and receive assistance from both
the provider's support team and experienced community members.
Customer Feedback and Surveys: Providers actively seek customer
feedback through surveys and feedback mechanisms to understand their needs
and identify areas for improvement.
Service-Level Agreements (SLAs): Cloud storage providers often offer SLAs
that outline the level of service and support customers can expect. SLAs
establish clear expectations and hold the provider accountable for meeting
agreed-upon service levels.
Personalization and Customization: Providers may offer personalized
recommendations and custom configurations to meet specific customer
requirements.
12. For large objects, what feature does Amazon S3 offer to improve upload CO3.9 CL2
performance and enable resumable uploads in case of interruptions?
For large objects, Amazon S3 offers a feature called "Multipart Upload" to

improve upload performance and enable resumable uploads in case of
interruptions. Multipart Upload is designed to upload large objects in parts,
breaking them into smaller chunks and uploading them concurrently, which
results in faster and more reliable uploads.
Key features of Multipart Upload in Amazon S3 include:
Improved Upload Performance: Multipart Upload improves upload

performance by allowing multiple parts of the object to be uploaded in parallel.
This parallelization reduces the time required to upload large files, especially
in scenarios with limited bandwidth or high network latency.
Resumable Uploads: If an interruption occurs during the upload process,

Multipart Upload enables resumable uploads. When the upload is paused or
fails, only the incomplete part needs to be retransmitted, rather than restarting
the entire upload process. This minimizes data redundancy and bandwidth
usage.
Automatic Part Handling: Amazon S3 handles the management and

assembly of the uploaded parts into a complete object. Once all parts are
uploaded, S3 consolidates them into a single object, making it ready for
immediate use.
Part Size Flexibility: With Multipart Upload, developers can choose the size
of each part, allowing them to optimize the upload process based on the
characteristics of the network and the size of the object.
Concurrent Uploads: Multiple parts of the object can be uploaded

concurrently, utilizing available bandwidth and maximizing the upload speed.
Ability to Pause and Resume: During the Multipart Upload process,

developers can pause, abort, or resume the upload at any time, giving them
better control over the upload process.
PART – C
1. Design a high availability architecture with failover mechanisms to minimize CO3.1 CL2
downtime and ensure continuous service availability in the cloud.
Multi-Region Deployment: Deploy your application and infrastructure across
multiple geographically dispersed regions. This ensures redundancy and fault
tolerance in case one region experiences an outage.
Load Balancers: Use load balancers to distribute incoming traffic across
multiple instances of your application deployed in different regions. This helps
in load distribution and ensures that the system can handle increased traffic.
Auto Scaling: Implement auto-scaling mechanisms to automatically add or
remove instances based on the demand. This ensures that the application can
handle varying workloads and provides elasticity to the system.
Database Replication: Set up database replication across multiple regions to
ensure data availability and reduce the risk of data loss. Use technologies like
Multi-AZ (Availability Zone) or cross-region replication for databases.
Content Delivery Network (CDN): Utilize a CDN to cache and serve static
content, reducing the load on your application servers and improving overall
performance.
Redundant Data Storage: Use redundant data storage solutions like object
storage or distributed file systems. This ensures that data remains accessible
even if one storage node fails.
Monitoring and Alerting: Implement a robust monitoring and alerting system
to detect and respond to issues proactively. Monitor the health of your
application, infrastructure, and services to ensure early detection of potential
problems.
Graceful Degradation: Plan for graceful degradation of services during peak
loads or failures. Determine which non-essential features can be temporarily
disabled to keep core functionalities operational.
Service Isolation: Segment your services into smaller, independent units to
minimize the impact of a failure in one service on others. This can be achieved
through containerization or microservices architecture.
Backup and Disaster Recovery: Regularly back up your data and
applications to a different region or separate cloud provider. Implement a
disaster recovery plan to recover the system in case of a catastrophic failure.
Cross-Region Replication of Services: If feasible, replicate essential services
in multiple regions to maintain high availability even if one region experiences
issues.
Active-Active Failover: For mission-critical services, implement an active-
active failover mechanism where the traffic is distributed across multiple
regions simultaneously, allowing for seamless failover without user disruption.
Health Checks and Auto Recovery: Configure health checks for your
application instances. If an instance fails health checks, an auto-recovery
mechanism should automatically replace it with a healthy one.
Disaster Recovery Testing: Periodically perform disaster recovery testing to
ensure that the failover mechanisms and backup procedures work as expected.
Immutable Infrastructure: Consider using immutable infrastructure
principles, where you replace instances instead of updating them. This can help
reduce configuration errors and ensure consistent deployments.
2. From a cost perspective, how does adopting the Platform as a Service (PaaS) CO3.2 CL3
model help businesses in optimizing expenses related to infrastructure
maintenance and resource utilization?
Elimination of Infrastructure Setup and Maintenance Costs: In the PaaS

model, the cloud service provider handles the underlying infrastructure,
including server setup, hardware maintenance, and updates. This eliminates the
need for businesses to invest in physical servers or data centers, reducing
capital expenditures (CapEx) on infrastructure.
Pay-as-You-Go Pricing: PaaS typically follows a pay-as-you-go pricing
model, where businesses pay only for the resources and services they consume.
This flexible pricing structure allows organizations to scale their resources up
or down based on actual usage, optimizing operational expenses (OpEx) and
avoiding over-provisioning.
Automated Resource Management: PaaS platforms automatically manage
resource provisioning and scaling based on application demand. This means
businesses don't need to spend time and effort manually optimizing resource
allocation. The system can dynamically adjust resources to match workload
fluctuations, ensuring efficient resource utilization.
Reduced IT Staffing Costs: With PaaS, the cloud service provider handles
many operational tasks, reducing the need for a large in-house IT team.
Businesses can reallocate their IT resources to focus on higher-value tasks,
innovation, and application development rather than infrastructure
management.
Faster Time-to-Market and Development Efficiency: PaaS offers pre-built
services and development tools that streamline the application development
process. Developers can leverage these services, APIs, and frameworks to
accelerate development, reducing the development time and associated costs.
Scalability without Downtime: PaaS platforms are designed to automatically
scale resources up or down based on demand. This elasticity ensures that
businesses can handle sudden spikes in traffic or demand without downtime,
maintaining service availability without overpaying for unused resources
during periods of low demand.
Reliability and High Availability: PaaS providers typically offer robust
infrastructure with high availability and redundancy. Businesses can take
advantage of this infrastructure to enhance reliability without investing in their
own redundant systems.
Security and Compliance: Reputable PaaS providers invest in top-tier
security measures and compliance certifications. By leveraging these secure
environments, businesses can avoid the cost of implementing and maintaining
their own stringent security protocols.
Focus on Core Business: By offloading infrastructure management and
maintenance to the PaaS provider, businesses can focus on their core
competencies and strategic goals, leading to increased productivity and cost
optimization.
3. Create a visual representation (diagram) showcasing the relationships between CO3.3 CL5
different NIST Cloud Service Management Requirements and how they
contribute to effective cloud service delivery.
Service Deployment :
This may be operated in one of the following deployment models:
 Public cloud - Done by service providers
 Private cloud - operated solely for a single organization
 Community cloud - organizations from a specific community with
common concerns
 Hybrid cloud - composition of two or more clouds (private,
community or public)
Service Orchestration:
 Service Orchestration supports the cloud providers activities in
arrangement, coordination and management of computing resources
in order to provide cloud services to cloud consumers.
 Has three layers such as Service Layer(Top), Resource Abstraction
Layer (Middle) and Physical Resource Layer(Lowest).
o Service Layer: interfaces for accessing services (IaaS, PaaS,
SaaS)
o Resource Abstraction / Control Layer: contains the system
components (hypervisors) which are used for accessing
physical resources.
o Physical Resource Layer: interfaces for accessing to physical
resources such as computers(CPU and memory),
networks(routers, firewalls) and storage components (hard
disks).
Cloud Service Management:
Cloud service management includes all of the service-related
functions that are necessary for the management and operation of services.
Cloud service management can be described through the following
requirements.
 Business support - deals with clients and supporting
processes. The components are shown in figure(below).
 Provisioning and configuration - is the process of setting up
the infrastructure. The components are shown in
figure(below).
Portability and interoperability - relate to the ability to build systems from
reusable components. The components are shown in figure(below).
4. For organizations with existing on-premises systems, how does the Private CO3.4 CL3
Cloud facilitate seamless integration with their current infrastructure and
enable hybrid cloud setups?
• Cloud services are used by a single organization, which are not
exposed to the public.
• Services are always maintained by a private network and the
hardware and software are dedicated only to single organization.
• Private cloud is physically located at
o Organization’s premises [On-site private clouds] (or)
o Outsourced(Given) to a third party[Outsource private
Clouds]
• Cloud may be managed either by
o Cloud Consumer organization (or) third party
• Private clouds are used by
o Government agencies
o Financial institutions
o Mid size to large-size organizations.
Out-sourced Private Cloud
On-site Private Cloud
• Private cloud supposes to deliver more efficient and convenient cloud

services.
• Offers higher efficiency, resiliency (to recover quickly), security, and
privacy.
• Provides
o Customer information protection.
o Follows its own standard procedures and operations.
Advantages:
 Offers greater Security and Privacy
 Organization has control over resources
 Highly reliable
 Saves money by vitalizing the resources
Disadvantages :
 Expensive when compared to public cloud.
 Requires IT Expertise to maintain resources.
5. Could you explain the key differences in how Google App Engine (GAE) CO3.5 CL3
abstracts infrastructure and handles resource management in the Platform as a
Service (PaaS) model versus its role as one of the components in the
Infrastructure as a Service (IaaS) model?
Platform as a Service (PaaS):
In the PaaS model, Google App Engine abstracts most of the underlying
infrastructure details, allowing developers to focus solely on writing and
deploying applications without worrying about managing the underlying server
infrastructure. Key characteristics of GAE's PaaS model include:
a. Abstraction of Infrastructure: GAE abstracts away the server and network

infrastructure, so developers don't need to manage virtual machines, operating
systems, or networking setups. They can concentrate on writing code and
configuring their applications.
b. Automatic Scalability: GAE automatically handles application scaling based

on demand. It can automatically allocate and deallocate resources to match the
incoming traffic without manual intervention.
c. Limited Control: The level of control over the infrastructure is limited in the
PaaS model. Developers have less control over the underlying infrastructure,
making it easier to manage but potentially less flexible for highly customized
requirements.
d. Pre-built Services: GAE offers a wide range of pre-built services, such as

databases, storage, authentication, and more. Developers can utilize these
services to add functionality to their applications without managing the
underlying infrastructure for those services.
Infrastructure as a Service (IaaS):
In the IaaS model, Google Cloud Platform (GCP) provides a lower-level

service that gives users more control over the underlying infrastructure and
resource management. Google Compute Engine is the IaaS component that
allows users to rent virtual machines (VMs) on which they have full control.
The key characteristics of GCP's IaaS model include:
a. Full Control: With IaaS, developers have full control over the virtual
machines, including the operating system, network settings, and other
configurations. This level of control enables highly customizable infrastructure
setups.
b. Manual Scalability: Unlike the automatic scaling of PaaS, in the IaaS model,
developers are responsible for manually configuring and managing the scaling
of virtual machines and resources as per the application's requirements.
c. Infrastructure Management: Users are responsible for managing their VMs,

including patching, updates, and overall server maintenance.
d. Customization: IaaS allows developers to install and run any software they
desire, providing a high degree of customization and flexibility.
6. How do organizations determine the most suitable approach (horizontal or CO3.6 CL3
vertical scalability) for their cloud storage system, considering factors like
budget, growth projections, and system complexity?
Workload Analysis: Organizations should begin by analyzing their current

workload and performance requirements. Understanding the nature of the data
being stored, the expected data growth rate, and the workload patterns will
provide insights into the storage demands.
Performance Requirements: Evaluate the performance requirements of the
application or system that will be utilizing the cloud storage. Consider factors
like I/O operations per second (IOPS), latency, and throughput requirements.
Budget Constraints: Budget is a crucial factor in any decision. Horizontal
scalability may involve distributing data across multiple inexpensive
commodity servers, making it more cost-effective for large-scale storage. On
the other hand, vertical scalability may involve investing in more powerful,
expensive hardware.
Growth Projections: Organizations need to consider their growth projections
and scalability requirements over time. Horizontal scalability is generally more
suitable for handling rapidly growing storage needs, as it can easily add more
storage nodes. Vertical scalability may require regular hardware upgrades,
which might not be as agile in response to fast-paced growth.
System Complexity: Assess the complexity of the storage system and how it
may impact management and maintenance. Vertical scalability might be
simpler to manage initially, as it involves fewer hardware components.
However, horizontal scalability can lead to more complex data distribution and
replication strategies.
Resilience and High Availability: Consider the importance of resilience and
high availability for the storage system. Horizontal scalability often provides
better redundancy and fault tolerance, as data can be distributed across
multiple nodes. Vertical scalability might be limited by the capabilities of a
single machine.
Cloud Service Provider Capabilities: If using a cloud service provider,
evaluate the offerings available. Some providers might offer specialized
storage solutions that align better with specific scalability requirements.
Future Flexibility: Think about future flexibility and adaptability. If there is a
possibility of the workload changing significantly in the future, a scalable and
flexible approach will be essential.
In many cases, a hybrid approach combining both horizontal and vertical
scalability might be the most suitable option. This approach leverages the
strengths of each method to optimize performance and cost-effectiveness.
7. In what ways does Cloud Storage as a Service (StaaS) simplify data storage CO3.7 CL2
management for individuals, small businesses, and large enterprises, compared
to traditional data storage methods?
Accessibility and Availability: Cloud storage allows users to access their data
from anywhere with an internet connection. This accessibility eliminates the
need for physical presence at a specific location, making it convenient for
users to retrieve and manage their data on the go.
Scalability: Cloud storage services typically offer flexible scalability options.
Users can easily scale up or down their storage capacity based on their
changing needs without having to invest in additional hardware or face the
complexities of managing physical storage devices.
No Hardware Maintenance: With traditional data storage methods,
individuals and businesses need to manage and maintain physical hardware,
such as servers, storage arrays, and backups. Cloud storage eliminates the need
for hardware maintenance as the service provider handles the infrastructure
upkeep.
Data Redundancy and Backup: Reputable cloud storage providers
implement data redundancy and backup mechanisms. This ensures that users'
data is safely stored in multiple locations, protecting against data loss due to
hardware failures or disasters.
Automatic Updates: Cloud storage services handle software updates and
security patches, relieving users of the responsibility of keeping their storage
infrastructure up-to-date and secure.
Pay-as-You-Go Pricing: Many cloud storage services offer pay-as-you-go
pricing models, where users pay only for the storage they consume. This
eliminates the need for large upfront investments in hardware and allows for
cost optimization.
Collaboration and Sharing: Cloud storage often includes collaboration
features that enable easy file sharing and real-time collaboration among team
members. This fosters efficient teamwork and eliminates the need for manual
file transfers.
Security and Compliance: Reputable cloud storage providers implement
robust security measures to protect data from unauthorized access.
Additionally, many providers adhere to industry standards and compliance
requirements, making it easier for businesses to meet regulatory obligations.
Data Synchronization: Cloud storage services often offer data
synchronization across multiple devices. This ensures that the latest version of
files is accessible and consistent across different devices, enhancing
productivity and user experience.
Reduced Administrative Overhead: Cloud storage as a service reduces the
administrative burden on individuals, small businesses, and large enterprises. It
allows them to focus on their core activities while leaving storage management
tasks to the service provider.
Global Accessibility: Cloud storage services have data centers located in
various regions worldwide, offering global accessibility and lower latency for
users accessing data from different geographic locations.
8. How does Amazon S3's distributed architecture and automatic replication of CO3.8 CL3
data contribute to the high availability of the Grep web application, ensuring
data access whenever needed, with minimal downtime?
GrepTheWeb Architecture
 Code-named GrepTheWeb because it can "grep" (a popular Unix
command-line utility to search patterns) the actual web documents.
 GrepTheWeb allows developers to do some pretty specialized
searches like selecting documents that have a particular HTML tag or
META tag.
 The output of the Million Search Results Service, which is a sorted
list of links and gzipped (compressed using the Unix gzip utility) in a
single file, is given to GrepTheWeb as input. It takes a regular
expression as a second input.
 It then returns a filtered subset of document links sorted and gzipped
into a single file.
 Since the overall process is asynchronous, developers can get the
status of their jobs by calling GetStatus() to see whether the execution
is completed. That process block diagram is shown in figure (below).
 Amazon S3 for retrieving input datasets and for storing output
dataset.
 Amazon SQS for buffering requests acting as a "glue" between
controllers.
 Amazon SimpleDB for storing intermediate status, log, and for user
data about tasks.
 Amazon EC2 for running a large distributed processing Hadoop
cluster on-demand. Hadoop for distributed processing, automatic
parallelization, and job scheduling.
 Launch phase is responsible for validating and initiating the

processing GrepTheWeb request, instantiating Amazon EC2
instances, launching Hadoop cluster on them and starting all job
processes.
 Monitor phase is responsible for monitoring the EC2 cluster, maps,
reduces, and checking for success and failure.
 Shutdown phase is responsible for billing and shutting down all
Hadoop processes and Amazon EC2 instances,
 Cleanup phase deletes Amazon SimpleDB transient data.
UNIT IV
RESOURCE MANAGEMENT AND SECURITY IN CLOUD
Inter Cloud Resource Management, Resource Provisioning and Resource Provisioning Methods, Global
Exchange of Cloud Resources-Scheduling Algorithms for Computing Clouds - Resource Management and
Dynamic Application Scaling -Security Overview, Cloud Security Challenges, Software-as-a-Service Security,
Security Governance, Virtual Machine Security, IAM, Security Standards.
SL.NO PART A CO CL
1 When you deploy an application on Google’s PaaS App Engine cloud service, CO4.1 CL1
the Administration Console provides you with which of the following
monitoring capabilities?
a) View data and error logs
b) Analyze your network traffic
c) View the application’s scheduled tasks
a) In the cloud, the particular service model you are using directly affects the
type of monitoring you are responsible for
b) In AaaS, you can alter aspects of your deployment
c) You can monitor your usage of resources through Amazon CloudWatch
3 The tools for managing Windows servers and desktops is CO4.1 CL1
a) Microsoft System Center
b) System Service
c) System Cloud
4 Which of the following is not a phase of cloud lifecycle management? CO4.1 CL1
a) The definition of the service as a template for creating instances
b) Client interactions with the service
c) Management of the operation of instances and routine maintenance
a) Google App Engine lets you deploy the application and monitor it
b) From the standpoint of the client, a cloud service provider is different
than any other networked service
c) The full range of network management capabilities may be brought to bear
to solve mobile, desktop, and local server issues
6 The Virtual machine conversion cloud is CO4.2 CL1
a) BMC Cloud Computing Initiative
b) Amazon CloudWatch
c) AbiCloud
7 _______ is Microsoft’s cloud-based management service for Windows CO4.2 CL1
systems.
a) Intune
b) Utunes
c) Outtunes
d) Windows Live Hotmail
8 The computing technology refers to services and applications CO4.2 CL1
that typically run on a distributed network through virtualized
resources are called.
a) Distributed Computing
b) Cloud Computing
c) Soft Computing
d) Parallel Computing
9 Which one of the following options can be considered as the Cloud? CO4.3 CL1
a) Hadoop
b) Intranet
c) Web Applications
10 Cloud computing is a kind of abstraction which is based on the notion of CO4.3 CL1
combining physical resources and represents them as _______resources to
users.
a) Real
b) Cloud
c) Virtual
d) none of the mentioned
11 Which of the following has many features of that is now known as cloud CO4.3 CL1
computing?
a) Web Service
b) Softwares
c) All of the mentioned
d)Internet
12 A cloud concepts is related to sharing and pooling of resources is CO4.3 CL1

a.Polymorphism
b.Virtualization
c.Abstraction
d.None of the mentioned
13 Which one of the following statements is not true? CO4.4 CL1
a) The popularization of the Internet actually enabled most cloud computing
systems.
b) Cloud computing makes the long-held dream of utility as a payment
possible for you, with an infinitely scalable, universally available system, pay
what you use.
c) Soft computing addresses a real paradigm in the way in which the
system is deployed.
d)All of the mentioned
14 Which of the following service provider provides the least amount of built in CO4.4 CL1
security?
a) SaaS
b) PaaS
c) IaaS
a) Different types of cloud computing service models provide different levels
of security services
b) Adapting your on-premises systems to a cloud model requires that you
determine what security mechanisms are required and mapping those to
controls that exist in your chosen cloud service provider
c) Data should be transferred and stored in an encrypted format for security
purpose
16 Which of the following area of cloud computing is uniquely troublesome? CO4.4 CL1
a) Auditing
b) Data integrity
c) e-Discovery for legal compliance
17 An essential element in cloud computing by CSA is CO4.5 CL1
a) Multi-tenancy
b) Identity and access management
c) Virtualization
18 Which is used for Web performance management and load testing? CO4.5 CL1
a) VMware Hyperic
b) Webmetrics
c) Univa UD
d) Tapinsystems
19 An application and infrastructure management software for hybrid multi- CO4.5 CL1
clouds is
a) VMware Hyperic
b) Webmetrics
c) Univa UD
d) Tapinsystems
20 Which of the following provides data authentication and authorization between CO4.5 CL1
client and service?
a) SAML
b) WS-SecureConversion
c) WS-Security
a) To address SOA security, a set of OASIS standards have been created
b) WS-SecureConversion attaches a security context token to communications
such as SOAP used to transport messages in an SOA enterprise
c) WS-Trust is an extension of SOA that enforces security by applying
tokens such as Kerberos, SAML, or X.509 to messages
22 A web services protocol for creating and sharing security context is CO4.5 CL1
a) WS-Trust
c) WS-SecurityPolicy
23 Which of the following is part of a general WS-Policy framework? CO4.6 CL1

a) WS-Trust
b) WS-Secure Conversion
c) WS-Security Policy
24 __________ is a mechanism for attaching security tokens to messages. CO4.6 CL1

a) STT
b) STS
c) SAS
25 For the _________ model, the security boundary may be defined for the CO4.6 CL1
vendor to include the software framework and middleware layer.
a) SaaS
b) PaaS
c) IaaS
26 This model type is not trusted in terms of security. CO4.6 CL1

a) Public
b) Private
c) Hybrid
27 Extends WS-Security to provide a mechanism to issue, renew, and validate CO4.7 CL1
security tokens is
a) WS-Trust
c) WS-SecurityPolicy
28 Which of the following is a key mechanism for protecting data? CO4.7 CL1
a) Access control
b) Auditing
c) Authentication
29 Which of the following are a common means for losing encrypted data? CO4.8 CL1
a) lose the keys
b) lose the encryption standard
c) lose the account
30 One of the weaker aspects of early cloud computing service offerings is CO4.8 CL1
a) Logging
b) Integrity checking
c) Consistency checking
SL.NO PART B CO CL
1. Does the lack of services and under provisioning of resources contribute to the CO 4.2 CL2
violation of SLA and penalties? And what are the implications of over
provisioning of resources, such as a decrease in revenue for the supplier?
Lack of Services and Under Provisioning:

SLA Violation: If a service provider fails to deliver the promised level of
service, such as not meeting uptime requirements or response time targets, it
can lead to SLA violations.
Penalties: SLAs often include penalty clauses that specify the consequences of
failing to meet the agreed-upon service levels. Penalties can include financial
compensation to the customer, service credits, or other forms of compensation.
Implications of Over Provisioning:

Over provisioning refers to allocating more resources than necessary to meet
the expected demand. While it might seem counterintuitive, over provisioning
can have negative consequences, including financial implications for the
supplier:
Increased Costs: Allocating excessive resources requires more investment in
terms of hardware, software licenses, maintenance, and energy consumption.
This can lead to higher operational costs for the service provider.
Decreased Efficiency: Over provisioning can lead to inefficient resource

utilization. Resources that are not fully utilized represent wasted capacity and
can't be used for other purposes.
Revenue Impact: Over provisioning can impact revenue in several ways:
Opportunity Cost: Resources allocated to over provisioning could have been

used to serve other customers, potentially generating additional revenue.
Inflexibility: Scaling down an over-provisioned system can be complex and

time-consuming, making it difficult to adjust to changing demands. This lack
of flexibility can lead to missed business opportunities.
Competitive Disadvantage: Higher costs resulting from over provisioning

might force a service provider to price their services higher, potentially making
them less competitive in the market.
2. The resource provisioning method address the dynamic allocation of CPU CO 4.3 CL2
resources, particularly in scenarios where users demand only one CPU but the
system automatically allocates two CPU's to their applications, Justify the
challenges related to CPU over commitment, virtualization, and performance
optimization?
CPU Overcommitment:
Resource Allocation Accuracy: Overcommitting CPU resources involves
allocating more virtual CPUs (vCPUs) to virtual machines (VMs) than there
are physical CPU cores available. This can lead to contention and resource
shortages if not managed properly.
Performance Degradation: If multiple VMs demand more CPU resources than

available, they might experience performance degradation due to resource
contention. This can lead to unpredictable response times and slow application
performance.
Virtualization:
Hypervisor Overhead: Virtualization introduces an additional layer (the
hypervisor) between the physical hardware and the VMs. This introduces
overhead for resource management, context switching, and emulation, which
can impact overall system performance.
Resource Isolation: While virtualization provides isolation between VMs,

there's still a possibility of resource contention, especially when VMs from
different tenants share the same physical hardware.
Performance Optimization:
Resource Balancing: Ensuring fair and efficient resource allocation across VMs
is challenging. Some VMs might be overutilized while others are underutilized,
leading to inefficient use of resources and potentially impacting performance.
Dynamic Resource Allocation: Automatically adjusting CPU allocations based

on workload demands requires sophisticated algorithms. Inaccurate decisions
can lead to both over commitment and underutilization issues.
3. Can you observe and describe an architecture that enables the seamless CO 4.3 CL3
integration of cross-domain capabilities, fostering on-demand, adaptable,
energized, and reliable infrastructure access through the utilization of
virtualization technology? Please highlight the key components, mechanisms,
and methodologies employed to ensure the successful implementation of such
an architecture, considering the challenges and benefits associated with this
complex system.
Architecture: Cross-Domain Virtualized Cloud Infrastructure
Key Components:
Virtualization Layer: This layer abstracts physical resources (compute, storage,

network) and creates virtual instances. It includes hypervisors for managing
virtual machines (VMs) and software-defined networking (SDN) controllers
for network virtualization.
Resource Pools: These are collections of physical resources (CPU, memory,

storage, and network) that are abstracted and allocated to VMs dynamically.
Orchestration and Management: This component handles resource
provisioning, scaling, and monitoring. It includes orchestration platforms,
management consoles, and APIs.
Security and Isolation: Mechanisms for ensuring security between different

domains, such as VM isolation, network segmentation, and encryption.
Automation and Self-Service: Users can provision and manage resources

through self-service portals, leveraging automation for quick deployment.
Elasticity and Scaling: The architecture allows resources to be scaled up or

down dynamically based on demand.
Virtualization: Hypervisors provide VMs with isolated environments,
enabling diverse workloads to coexist on shared hardware.
Software-Defined Networking: SDN enables dynamic network configuration
and isolation, allowing flexible connectivity across domains.
Orchestration and Automation: Orchestration tools automate resource
allocation, scaling, and management based on predefined policies and user
demand.
Service Catalogs: A catalog of preconfigured services and templates speeds up
the deployment of complex applications.
Multi-Tenancy: Mechanisms for segregating resources securely among
different tenants or domains.
APIs and Integration: Open APIs enable seamless integration with external
systems, allowing for custom workflows and integration with third-party tools.
Challenges:
Virtualization: Hypervisors provide VMs with isolated environments, enabling
diverse workloads to coexist on shared hardware.
Software-Defined Networking: SDN enables dynamic network configuration
and isolation, allowing flexible connectivity across domains.
Orchestration and Automation: Orchestration tools automate resource
allocation, scaling, and management based on predefined policies and user
demand.
Service Catalogs: A catalog of preconfigured services and templates speeds up
the deployment of complex applications.
Multi-Tenancy: Mechanisms for segregating resources securely among
different tenants or domains.
APIs and Integration: Open APIs enable seamless integration with external
systems, allowing for custom workflows and integration with third-party tools.
4. Explore the specific security concerns and challenges that have arisen on cloud CO 4.4 CL3
platforms, which have resulted in hesitancy among companies to migrate their
critical resources to the cloud.
Data Security and Privacy:

Data Breaches: Companies worry about unauthorized access leading to data
breaches. The shared nature of cloud infrastructure increases the potential
attack surface.
Data Location: Data may be stored in different geographical locations,

potentially leading to compliance and regulatory issues related to data
sovereignty.
Access Control and Identity Management:

Identity Theft: Poorly managed access controls can lead to identity theft and
unauthorized access to sensitive data or services.
Single Point of Failure: Centralized identity systems can become single points
of failure, leading to cascading security risks if compromised.
Data Loss and Availability:

Service Outages: Cloud service providers can experience downtime due to
technical issues or attacks, affecting the availability of critical resources.
Data Loss: Cloud providers are responsible for data availability, but data loss
incidents have occurred due to various reasons, including human errors and
hardware failures.
Multi-Tenancy and Segregation:

Resource Contention: Sharing infrastructure among multiple tenants can lead to
resource contention and potentially impact performance and security.
Isolation Failures: Inadequate isolation between tenants can lead to data
leakage or unauthorized access.
Compliance and Legal Concerns:

Regulatory Compliance: Different industries are subject to various regulations
(e.g., GDPR, HIPAA). Ensuring compliance in a shared cloud environment can
be complex.
Auditing: The lack of transparency in some cloud services can make auditing
for compliance challenging.
Vendor Lock-In:
Interoperability: Transitioning between different cloud providers or back to on-
premises solutions can be difficult due to vendor-specific technologies and
formats.
Insecure Interfaces and APIs:

API Exploitation: Weaknesses in APIs can be exploited by attackers to gain
unauthorized access to systems and data.
Lack of Standardization: Variations in API implementations among cloud

providers can complicate security efforts.
Cloud Service Provider Security:

Shared Responsibility: There can be confusion about the division of security
responsibilities between the customer and the cloud provider.
Provider Vulnerabilities: Security vulnerabilities in the cloud provider's

infrastructure can potentially impact all customers.
Data Encryption:
Data in Transit and at Rest: Ensuring data is encrypted both during
transmission and when stored is crucial to prevent unauthorized access.
Insider Threats:
Provider Employees: Concerns about insider threats from cloud provider
employees who have access to customer data.
Tenant Employees: Insider threats from within the tenant's organization,

including employees with unnecessary access privileges.
5. Identify the risks associated with each of the three levels of security models in CO 4.5 CL2
infrastructure security: physical security, network security, and data security?
Physical Security: Physical security focuses on safeguarding the physical

assets of an organization, such as buildings, equipment, and personnel. Risks
associated with physical security include:
Unauthorized Access: Intruders gaining access to restricted areas or facilities

can lead to theft, sabotage, or unauthorized data access.
Theft or Vandalism: Equipment, servers, and hardware can be stolen or

damaged, leading to data loss and operational disruption.
Insider Threats: Employees with malicious intent can exploit their physical
access privileges to compromise security.
Natural Disasters: Fires, floods, earthquakes, and other disasters can damage
facilities, leading to service disruption and data loss.
Lack of Monitoring: Insufficient surveillance and monitoring can prevent the

detection of unauthorized activities.
2. Network Security: Network security involves protecting the organization's

network infrastructure and data transmission. Risks associated with network
security include:
Data Interception: Hackers can intercept sensitive data during transmission,

leading to data breaches or unauthorized access.
Malware and Viruses: Network-connected systems are vulnerable to malware

and viruses that can compromise data integrity and availability.
Denial of Service (DoS) Attacks: Attackers can flood network resources,

causing service disruptions and downtime.
Weak Authentication: Weak passwords and insufficient authentication

mechanisms can lead to unauthorized access.
Insider Attacks: Malicious employees or contractors can exploit network

vulnerabilities to compromise data.
Unpatched Systems: Failure to apply security patches can leave systems

vulnerable to known exploits.
Data Security: Data security involves protecting the confidentiality, integrity,

and availability of data. Risks associated with data security include:
Data Breaches: Unauthorized access to sensitive data, including customer

information, financial data, and proprietary information.
Data Loss: Accidental or intentional data loss can occur due to hardware
failure, software bugs, or malicious actions.
Insider Threats: Employees with access to sensitive data can misuse or leak it.
Inadequate Encryption: Data transmitted or stored without encryption can be

intercepted and accessed by unauthorized parties.
Improper Data Handling: Poor data handling practices, such as sharing

credentials or leaving sensitive data exposed, can lead to data leaks.
Lack of Data Backups: Failure to regularly back up data can result in

permanent data loss during incidents.
6. In the context of the SPI (Software, Platform, Infrastructure) model, elaborate CO 4.5 CL3
on the intricate delineation of responsibilities concerning application security at
the SaaS and PaaS levels, and provide a comprehensive justification for why
cloud service providers assume the onus of safeguarding applications hosted
within their data centers.
SaaS Level: At the SaaS level, cloud service providers take on a significant
portion of application security responsibilities due to the fully managed nature
of SaaS offerings. Here's how the delineation of responsibilities works:
Cloud Service Provider Responsibilities:
Infrastructure Security: The provider ensures the security of the underlying

infrastructure, including data centers, networks, and servers, to prevent
unauthorized access and data breaches.
Application Security: Providers are responsible for securing the SaaS

application itself, including its code, databases, and interfaces.
Access Controls: Implementing robust access controls, authentication, and

authorization mechanisms to ensure that only authorized users can access the
application.
Encryption: Data at rest and in transit is typically encrypted by the provider to

prevent data exposure.
Patching and Updates: Keeping the SaaS application and underlying

components up to date with security patches to address known vulnerabilities.
Monitoring and Incident Response: Continuous monitoring of the

application's behavior and response to potential security incidents.
Compliance: Ensuring that the SaaS service complies with industry-specific

regulations and security standards.
Customer Responsibilities:
User Access Management: Customers are responsible for managing user

accounts, roles, and permissions within the SaaS application.
Data Management: Ensuring that data entered into the SaaS application
adheres to proper security practices and regulations.
Configuration and Customization: Customizing the application's settings to

align with the organization's security policies and requirements.
Data Backup and Recovery: Depending on the SaaS provider, customers
might need to ensure data backup and recovery strategies are in place.
PaaS Level: At the PaaS level, the division of security responsibilities is more
shared between the cloud service provider and the customer:
Justification for Cloud Service Providers Assuming Application Security:
Expertise: Cloud service providers have specialized teams and resources

dedicated to security, making them well-equipped to handle complex security
challenges.
Economies of Scale: Providers can invest in security tools, technologies, and

expertise that might be cost-prohibitive for individual customers.
Consistency: Providers can enforce security standards consistently across their

customer base, ensuring a higher level of security overall.
Mitigation of Risks: By taking on the responsibility of application security,

providers help mitigate risks for customers who might lack the resources or
expertise to address all aspects of security.
Trust and Reputation: Providers' commitment to security enhances their

reputation and builds trust among customers.
7. Could you elucidate the surreptitious techniques employed for third-party CO 4.5 CL2
sharing of user data without their knowledge?
Hidden Data Collection in Apps:
Silent Permissions: Mobile apps might request permissions unrelated to their

core functionality (e.g., a flashlight app asking for access to contacts) and use
these permissions to gather user data.
Background Data Collection: Apps can collect data even when not actively
used, sending information to third parties without the user's knowledge.
Cookie Tracking and Web Beacons:
Cross-Site Tracking: Cookies and tracking mechanisms are used to monitor

user behavior across websites, creating profiles that can be shared with third
parties.
Pixel Tracking: Invisible images or web beacons embedded in websites track

user interactions, enabling data collection and sharing without explicit consent.
Third-Party SDKs:
Invisible Data Collection: Mobile apps and websites may integrate third-party
software development kits (SDKs) that collect data without clear user
awareness.
Data Leakage: SDKs can unintentionally leak sensitive user data to third
parties due to poor implementation or security vulnerabilities.
Social Media Plugins:
Social Widgets: These elements on websites may appear harmless but can track
user activity and share data with social media platforms.
Shadow Profiles: Social media networks might collect data about non-users
through the interactions of users who have consented to share their contacts.
Browser Fingerprinting:
Unique Identifiers: Websites collect information about users' devices, browser

configurations, and system settings to create a unique fingerprint for tracking
purposes.
Persistent Tracking: Fingerprinting can be used to track users across different

websites without relying on cookies.
Location Tracking:
Background Location: Apps can gather location data even when not in use,
potentially sharing this information with third parties.
Geo-tagged Content: User-generated content like photos might contain location

information that can be extracted and shared.
Data Brokers and Aggregators:

Data Purchase: Companies buy and sell user data, creating comprehensive
profiles that can be used for targeted marketing without users' explicit
knowledge.
Data Mining: Publicly available data from various sources is aggregated to

create detailed user profiles.
Dark Patterns:
Deceptive Interfaces: Interfaces designed to confuse or mislead users into

consenting to data sharing or agreeing to terms without understanding the
implications.
Obfuscated Opt-Out: Making the process of opting out of data sharing difficult
to find or navigate.
Pre-Checked Boxes and Ambiguous Language:
Default Settings: Opt-in or sharing options are set as default, requiring users to
actively opt out.
Complex Privacy Policies: Policies written in complex language that users

might not fully understand, making it difficult to know what data is being
shared.
Bluetooth and Wi-Fi Tracking:
Beacon Technology: Bluetooth beacons in physical locations track users'

devices and movements, enabling data collection and sharing
8. Will the cloud future models likely incorporate the use of the internet to fulfill CO 4.6 CL3
their customers' requirements via SaaS with Web 2.0 collaboration
technologies?
The future of cloud computing is expected to incorporate the use of the internet
to fulfill customer requirements, especially through Software as a Service
(SaaS) offerings combined with Web 2.0 collaboration technologies. This
combination can lead to enhanced user experiences, improved collaboration,
and greater flexibility for both consumers and businesses. Here's how these
elements are likely to converge:
1. SaaS and Internet-Based Delivery: SaaS delivers software applications
over the internet, eliminating the need for users to install and maintain software
locally. This model is well-suited for both individuals and businesses looking
for convenient and cost-effective solutions. SaaS provides various benefits,
such as:
Accessibility: Users can access applications from anywhere with an internet
connection, enabling remote work and collaboration.
Automatic Updates: SaaS providers handle updates and patches, ensuring
users always have access to the latest features and security enhancements.
Scalability: SaaS applications can scale easily to accommodate changing user
demands without requiring manual adjustments.
Subscription Model: SaaS often operates on a subscription basis, allowing
users to pay only for what they use.
2. Web 2.0 Collaboration Technologies: Web 2.0 technologies emphasize
user-generated content, collaboration, and interactive experiences. These
technologies complement SaaS offerings and contribute to enhanced
collaboration and engagement. Some key features of Web 2.0 collaboration
technologies include:
Social Networking: Web 2.0 platforms enable users to connect, share
information, and collaborate within a network of peers.
Collaborative Editing: Tools that allow multiple users to edit and collaborate
on documents in real-time.
User-Generated Content: Users contribute content, reviews, ratings, and
feedback, enhancing the overall experience.
Rich User Interfaces: Interfaces that provide interactive and dynamic
experiences, improving user engagement.
9. Point out Why should a security management committee be established with CO 4.7 CL2
the objective of offering guidance on security measures and coordination with
IT strategies?
Establishing a security management committee is crucial for several reasons, as

it plays a pivotal role in aligning security measures with IT strategies and
ensuring comprehensive protection for an organization's digital assets. Here's
why such a committee should be formed:
1. Comprehensive Security Approach: A dedicated security management
committee brings together experts from various domains, including IT, legal,
compliance, and risk management. This collective expertise ensures a holistic
approach to security that considers multiple aspects, vulnerabilities, and
potential threats.
2. Strategic Alignment: The committee facilitates the alignment of security
initiatives with the organization's overall business and IT strategies. It ensures
that security measures are in line with the organization's goals and objectives,
avoiding conflicts or misalignments.
3. Risk Management: By evaluating risks associated with technology
adoption, data handling, and compliance, the committee helps identify potential
threats and vulnerabilities. It plays a proactive role in risk mitigation and helps
prevent potential security breaches.
4. Governance and Oversight: The committee establishes governance
mechanisms that define roles, responsibilities, and accountability for security-
related matters. This structure ensures that security decisions are well-informed
and in compliance with regulations.
5. Cross-Functional Collaboration: With representatives from various
departments, the committee encourages collaboration between IT and other
business units. This collaboration fosters a better understanding of security
requirements across the organization.
10. Develop an architectural security framework involves designing a structured CO 4.8 CL3
approach to ensure the security of an organization's information technology
infrastructure.
The following are some of the key concepts of architectural security

framework:
Risk management: The first step in designing an architectural security

framework is to identify and assess the risks to the organization's IT
infrastructure. This includes threats, vulnerabilities, and impact.
Security controls: Once the risks have been identified, security controls can be
put in place to mitigate them. Security controls can be technical, procedural, or
administrative.
Defense in depth: A defense in depth approach is used to protect the IT
infrastructure from multiple attack vectors. This means implementing a variety
of security controls that work together to protect the system.
Least privilege: The principle of least privilege states that users should only be
granted the access they need to perform their job duties. This helps to reduce
the risk of unauthorized access to sensitive data.
Continuous monitoring: The security of the IT infrastructure should be
continuously monitored to detect and respond to threats. This includes
monitoring for security incidents, vulnerabilities, and changes to the
environment.
There are many different architectural security frameworks available, each with
its own strengths and weaknesses. Some of the most popular frameworks
include:
Security Architecture Framework (SABSA): SABSA is a comprehensive

framework that covers all aspects of security architecture. It is a good choice
for organizations that want a holistic approach to security.
Open Security Architecture (OSA): OSA is a lightweight framework that
focuses on the implementation of security controls. It is a good choice for
organizations that want to quickly implement security controls.
TOGAF: TOGAF is a general-purpose framework for enterprise architecture. It
can be used to design a secure IT infrastructure as part of a broader enterprise
architecture project.
The best architectural security framework for an organization will depend on

its specific needs and requirements. However, all frameworks should include
the key concepts discussed above.
Here are some additional tips for designing an architectural security

framework:
Get buy-in from all stakeholders. Security is everyone's responsibility, so it is

important to get buy-in from all stakeholders in the organization. This includes
IT staff, business leaders, and employees.
Keep it simple. The security framework should be easy to understand and
implement. It should not be so complex that it is difficult to maintain.
Be flexible. The security framework should be flexible enough to adapt to
changes in the organization's environment.
Be adaptive. The security framework should be adaptive enough to respond to
new threats and vulnerabilities.
11. Identify the security framework composed of policy and governance CO 4.9 CL3
components used for creation, maintenance and termination of digital identifies
with controlled access of shared resources.
The security framework that you are describing is called a digital identity
management (IDM) framework. It is a set of policies, procedures, and
technologies that are used to create, maintain, and terminate digital identities.
IDM frameworks typically include the following components:
Identity Provisioning: This is the process of creating and assigning digital

identities to users.
Identity Management: This is the process of managing the lifecycle of digital
identities, including updating, disabling, and deleting them.
Identity Authentication: This is the process of verifying the identity of a user.
Identity Authorization: This is the process of granting users access to
resources.
Identity Audit and Monitoring: This is the process of monitoring the use of
digital identities and detecting unauthorized access.
IDM frameworks can be used to protect a variety of resources, including:
Information systems: This includes computers, networks, and databases.

Physical assets: This includes buildings, equipment, and vehicles.
Financial assets: This includes cash, securities, and other valuables.
Intellectual property: This includes patents, trademarks, and copyrights.
12. In the realm of information security, could you elucidate the principal objective CO 4.10 CL2
underlying the process of authentication and its inherent dissimilarities
concerning purpose in comparison to the process of authorization?
Characteristic Authentication Authorization
Determine what
Purpose Verify the identity of a user can
access
Happens after
Time Happens before authorization
Role,
Username and password, security token,
Factors job function,
biometric data
privileges
PART C
1. In the intricate world of cloud computing, could you expound upon the CO 4.2 CL3
fundamental utilization of virtual machines as foundational building blocks for
crafting the execution environment spanning diverse resource sites? Moreover,
elaborate on the intricacies involved in carrying out resource provisioning
within a dynamic environment?
Virtual Machines (VMs) as Foundational Building Blocks:
In cloud computing, a virtual machine is a software-based emulation of a

physical computer. It operates within a host system and runs an operating
system and applications just like a physical machine. VMs are fundamental to
cloud infrastructure because they enable efficient resource utilization, isolation,
and flexibility. Here's how they serve as foundational building blocks:
Resource Isolation: VMs allow multiple virtual instances to run on the same
physical hardware while being isolated from each other. This isolation prevents
conflicts between different applications and users sharing the same physical
resources.
Hardware Abstraction: VMs abstract the underlying physical hardware,
allowing applications to run on different hardware configurations without
needing to modify the software. This abstraction makes it easier to migrate
VMs between different host systems.
Flexibility and Scalability: VMs are highly flexible and scalable. They can be
quickly deployed, duplicated, and resized to match varying workloads. This
elasticity enables efficient resource allocation based on demand.
Application Testing and Development: VMs are often used for software
development and testing. Developers can create multiple VMs with different
configurations to test software compatibility and conduct experiments without
affecting production systems.
Legacy Application Support: VMs can host legacy applications that require
specific operating systems or hardware configurations. This allows
organizations to transition to newer infrastructure while still supporting older
applications.
Resource Provisioning in Dynamic Environments:
Resource provisioning refers to the process of allocating and managing

computing resources (such as CPU, memory, storage, and network bandwidth)
to meet the demands of applications and services. In dynamic cloud
environments, provisioning becomes more complex due to varying workloads
and the need to optimize resource utilization. Here's how resource provisioning
works:
Auto Scaling: To accommodate changing workloads, cloud platforms use

auto-scaling mechanisms. When the demand for resources increases, additional
VM instances are automatically launched. Conversely, when demand
decreases, surplus instances are terminated.
Elasticity: Elasticity refers to the ability of a system to quickly scale up or
down in response to workload changes. This ensures that applications can
handle varying levels of traffic without compromising performance.
Monitoring and Analytics: Resource provisioning relies on continuous
monitoring of system performance and workload metrics. Cloud providers use
monitoring data and analytics to predict resource needs and adjust provisioning
accordingly
2. Identify the architecture with the primary objective of facilitating the brokerage CO 4.3 CL3
and seamless sharing of cloud resources across multiple Clouds. This is done
with the aim of efficiently scaling applications and ensuring optimal
performance and resource utilization.
In a multi-cloud architecture, organizations leverage resources from multiple

cloud service providers (CSPs) simultaneously. This approach offers several
benefits, including avoiding vendor lock-in, enhancing resilience, optimizing
costs, and accessing specialized services from different providers.
Key components and concepts of a multi-cloud architecture include:
Cloud Brokerage: The architecture often includes a cloud brokerage layer or

platform that acts as an intermediary between an organization and multiple
cloud providers. The brokerage platform assists in selecting the most suitable
cloud resources based on application requirements, cost considerations, and
performance expectations.
Unified Management: Multi-cloud architecture aims to provide a unified
management interface to manage resources across different clouds. This helps
streamline operations and avoid the complexities of managing each cloud
separately.
Resource Abstraction: The architecture abstracts the underlying cloud
resources, making it easier to manage applications and services irrespective of
the specific cloud provider's infrastructure.
Resource Orchestration: Orchestration tools and platforms are used to
automate the deployment, scaling, and management of applications across
multiple clouds. This ensures consistency and efficient utilization of resources.
Application Portability: Multi-cloud architecture enables applications to be
deployed and run seamlessly across different clouds without significant
modifications. This portability is achieved through containerization (using
technologies like Docker) or serverless computing.
Load Balancing and Scaling: Multi-cloud environments can distribute
application workloads across multiple clouds for load balancing and improved
performance. Auto-scaling mechanisms can dynamically adjust resource
allocation based on demand.
Vendor Diversity: Organizations can leverage the strengths and capabilities of
different cloud providers for specific parts of their applications. For instance,
they might use one cloud provider for machine learning services and another
for data storage.
Disaster Recovery and Resilience: By using resources from multiple clouds,
organizations can create robust disaster recovery strategies that span across
different geographic regions and cloud providers.
Optimized Costs: Multi-cloud architecture allows organizations to choose the
most cost-effective cloud options for their workloads and avoid being locked
into a single provider's pricing model.
Hybrid Cloud Integration: Multi-cloud architecture can be integrated with
on-premises data centers to create hybrid cloud setups. This extends the
flexibility and scalability of the cloud to existing infrastructure.
3. Nowadays most small and medium size companies move to the cloud because CO 4.4 CL3
of their advantages such as lower infrastructure, no maintenance cost, model
pay off, on demand access etc. Justify with various security issues.
Lower Infrastructure Costs: Advantage: Cloud computing eliminates the
need for companies to invest in and maintain their own physical hardware,
which can result in cost savings. Security Concern: Sharing infrastructure
with other users in a multi-tenant environment might expose companies to
security risks if other tenants have vulnerabilities or malicious intent. Adequate
isolation and segmentation are essential to mitigate these risks.
No Maintenance Cost: Advantage: Cloud providers handle the maintenance
and updates of the underlying infrastructure, freeing companies from these
tasks. Security Concern: Relying on providers for maintenance means putting
trust in their security practices. Companies must ensure that providers adhere to
rigorous security standards and promptly address vulnerabilities.
Pay-as-You-Go Model: Advantage: Cloud's pay-as-you-go model allows
companies to scale resources up or down based on demand, optimizing costs.
Security Concern: Rapidly scaling resources could lead to misconfigurations
or oversights in security settings, potentially exposing sensitive data or
resources. Automated monitoring and response mechanisms are crucial.
On-Demand Access: Advantage: Cloud services provide instant access to
computing resources, enabling agility and quick deployments. Security
Concern: The convenience of on-demand access might lead to a lack of proper
security assessments before deploying resources, increasing the risk of
deploying vulnerable applications.
Global Accessibility: Advantage: Cloud services can be accessed from
anywhere, promoting remote work and collaboration. Security Concern: This
accessibility increases the potential attack surface, as users might access
resources from unsecured networks or devices. Robust authentication and
encryption are vital to safeguard against unauthorized access.
Resource Consolidation: Advantage: Virtualization and resource
consolidation enhance efficiency by allowing multiple VMs on a single
physical server. Security Concern: If a single physical server is compromised,
multiple VMs could be at risk. Proper segmentation and monitoring are
necessary to prevent lateral movement.
Third-Party Dependencies: Advantage: Companies can utilize third-party
cloud services to add functionality and efficiency. Security Concern:
Integrating third-party services can introduce security vulnerabilities,
especially if proper due diligence isn't conducted on those services' security
practices.
Data Residency and Compliance: Advantage: Cloud providers offer data
centers in various regions, facilitating data storage and compliance with local
regulations. Security Concern: Data residency regulations might conflict with
data storage in certain geographic locations. Ensuring compliance while
benefiting from cloud services requires careful consideration.
Human Error: Advantage: Cloud providers handle much of the infrastructure
management, reducing the likelihood of human errors. Security Concern:
However, human error can still occur in application configuration, access
control, and data management, leading to security breaches.
Vendor Selection and Risk Assessment: Advantage: Cloud providers offer a
wide range of services, making it easier to select services that suit business
needs. Security Concern: However, not all providers prioritize security
equally. Companies must thoroughly evaluate potential providers and
understand their security practices.
4. Cloud service providers are responsible for providing security for applications CO 4.5 CL 3
hosted in their data centers. Demonstrate the levels of the attack and name of
the attack.
Physical Security:
Attack Name: Physical Intrusion
Description: Unauthorized physical access to data centers or server rooms.
CSP Mitigation: CSPs implement strict physical security measures, including

biometric access controls, surveillance cameras, security personnel, and
restricted access areas to prevent unauthorized entry.
Network Security:
Attack Name: Distributed Denial of Service (DDoS) Attack
Description: Overwhelming a network or server with a flood of traffic to make

it unavailable.
CSP Mitigation: CSPs deploy DDoS protection mechanisms such as traffic

filtering, rate limiting, and using globally distributed networks to absorb excess
traffic.
Host Security: Attack Name: Malware Injection
Description: Injecting malicious code into an application or system to

compromise it.
CSP Mitigation: CSPs implement host-based intrusion detection and

prevention systems, regular malware scans, and isolate virtual machines to
contain potential infections.
Data Security: Attack Name: Data Breach
Description: Unauthorized access to sensitive data, potentially leading to data

theft or exposure.
CSP Mitigation: CSPs use encryption to protect data at rest and in transit,
access controls to limit who can access data, and regular security audits to
identify vulnerabilities.
Application Security:
Attack Name: SQL Injection
Description: Exploiting vulnerabilities in an application's input fields to

execute malicious SQL queries.
CSP Mitigation: CSPs provide secure Level

5. In what ways does SaaS offer cost-effectiveness for businesses in terms of CO 4.6 CL2
infrastructure and operational expenses?
Software as a Service (SaaS) offers several ways in which it can provide cost-
effectiveness for businesses in terms of both infrastructure and operational
expenses:
Elimination of Hardware Costs: With SaaS, businesses don't need to invest

in expensive hardware infrastructure to run applications. The software is hosted
and managed by the SaaS provider, reducing the need for purchasing and
maintaining hardware.
No Upfront Software Costs: SaaS operates on a subscription model, allowing

businesses to avoid the upfront costs associated with purchasing software
licenses. This makes budgeting more predictable and reduces initial capital
expenditures.
Reduced Maintenance Costs: SaaS providers handle software updates,
patches, and maintenance tasks. This eliminates the need for businesses to
allocate resources and expenses for ongoing maintenance and ensures the
software remains up-to-date.
Scalability and Flexibility: SaaS applications can scale up or down based on
demand. Businesses don't need to invest in excess capacity to accommodate
peak usage, resulting in better resource utilization and cost savings.
Pay-as-You-Go Pricing: Businesses pay for what they use, following a pay-
as-you-go pricing model. This ensures that costs are directly aligned with
usage, reducing wastage and overprovisioning of resources.
Reduced IT Staffing Costs: Since SaaS providers manage the infrastructure,
businesses can reduce their IT staff's workload and associated expenses related
to software deployment, maintenance, and troubleshooting.
Rapid Deployment: SaaS applications are typically ready for use with
minimal setup and configuration. This reduces implementation time and
associated costs, allowing businesses to start benefiting from the software
quickly.
Remote Accessibility and Collaboration: SaaS applications can be accessed
from anywhere with an internet connection. This promotes remote work and
collaboration, potentially reducing expenses related to physical infrastructure
and office space.
Access to Advanced Features: SaaS often provides access to advanced
features and functionalities without requiring businesses to invest in developing
or integrating these features themselves.
Outsourced Support: SaaS providers often offer customer support as part of
their offerings. Businesses can rely on the provider's expertise for
troubleshooting and issue resolution, reducing the need for extensive in-house
support teams.
Reduced Risk of Obsolescence: SaaS applications are regularly updated by
the provider with new features, security enhancements, and performance
improvements. This reduces the risk of using outdated software and the
associated costs of maintaining legacy systems.
Global Accessibility: SaaS applications can be accessed from anywhere,
enabling international operations without the need for establishing physical
infrastructure in multiple locations.
6. In the context of cloud computing environments, could you elaborate on the CO 4.7 CL4
feasible methods or approaches that enable the achievement of Security
Governance, considering the intricacies involved in managing security policies,
controls, risk assessments, and compliance measures to safeguard data,
applications, and resources effectively?
In cloud computing environments, achieving effective security governance is

crucial to ensure the protection of data, applications, and resources. Security
governance involves establishing and managing security policies, controls, risk
assessments, and compliance measures to mitigate security risks and meet
regulatory requirements. Here are feasible methods and approaches to achieve
security governance in cloud computing:
Clear Security Policies:
Develop comprehensive security policies that outline the rules, responsibilities,

and expectations for security in the cloud environment. These policies should
cover data handling, access controls, encryption, incident response, and more.
Risk Assessment and Management:
Conduct regular risk assessments to identify potential threats, vulnerabilities,

and risks associated with the cloud environment. Prioritize risks based on
impact and likelihood and develop strategies to mitigate or accept them.
Compliance Management:
Stay informed about relevant regulatory requirements and industry standards

that apply to your organization. Implement controls and processes to ensure
compliance with these standards. Cloud providers often offer compliance
certifications, which can aid in meeting regulatory obligations.
Identity and Access Management (IAM):
Implement strong IAM practices to control access to cloud resources. Use

principles like least privilege, role-based access controls (RBAC), and multi-
factor authentication (MFA) to ensure only authorized users have access.
Data Protection and Encryption:
Encrypt sensitive data both in transit and at rest. Implement encryption

mechanisms provided by the cloud provider or use third-party encryption tools
for added security.
Configuration Management:
Follow best practices for securely configuring cloud resources. Leverage

automation tools to enforce consistent and secure configurations across the
environment.
Continuous Monitoring:
Implement continuous monitoring to detect and respond to security incidents in

real time. Use intrusion detection systems (IDS), security information and
event management (SIEM) solutions, and log analysis to identify anomalies
and threats.
7. In what ways does FISMA outline information security requirements for CO 4.8 CL3
federal agencies and their cloud service providers, ensuring compliance with
federal information security standards?
The Federal Information Security Management Act (FISMA) outlines

information security requirements for federal agencies and their cloud service
providers (CSPs) to ensure compliance with federal information security
standards. FISMA is a U.S. federal law that establishes a framework for
protecting federal information and information systems against unauthorized
access, use, disclosure, disruption, modification, or destruction.
FISMA provides guidance on how federal agencies and their CSPs should
approach information security to protect sensitive data and maintain the
integrity and availability of information systems. Here are the key ways in
which FISMA outlines information security requirements:
Risk Management Framework (RMF): FISMA requires federal agencies and

CSPs to adopt a risk management framework for assessing and managing risks
to information and information systems. The RMF provides a structured
approach for categorizing systems, selecting security controls, implementing
controls, assessing controls' effectiveness, authorizing systems, and monitoring
security postures.
Security Controls and Guidelines: FISMA provides a set of security controls

and guidelines known as the National Institute of Standards and Technology
(NIST) Special Publication 800-53. These controls cover a wide range of
security domains, including access control, encryption, identity management,
incident response, and more. Federal agencies and CSPs must implement and
manage these controls based on the risk assessments of their systems.
Continuous Monitoring: FISMA emphasizes continuous monitoring of

security controls and systems to identify and respond to potential security
threats in real time. This ongoing monitoring approach ensures that security
remains effective and adapts to changing threats and vulnerabilities.
Reporting and Compliance Audits: FISMA requires federal agencies to

report their security posture and compliance with information security
requirements to the Office of Management and Budget (OMB) and the U.S.
Congress. CSPs supporting federal agencies also need to provide security-
related information to demonstrate compliance with FISMA regulations.
Security Authorization: Federal agencies and CSPs must undergo a security

authorization process to formally assess and document the security controls
implemented in their systems. This process involves evaluating risks,
implementing controls, conducting security assessments, and making risk-
based decisions on system authorization.
Continuous Improvement: FISMA promotes a culture of continuous

improvement in information security. Federal agencies and CSPs are expected
to learn from security incidents, audits, and assessments and use these lessons
to enhance security postures and practices.
Cloud-Specific Requirements: FISMA acknowledges the use of cloud

computing by federal agencies and outlines specific requirements for cloud
security. Cloud service providers must comply with FISMA standards and
provide federal agencies with information needed for risk assessments and
security authorization.
Security Documentation: FISMA mandates the development of security

documentation, including security plans, risk assessments, security assessment
reports, and security authorization packages. These documents provide a
comprehensive view of security measures and are essential for demonstrating
compliance.
Privacy and Data Protection: FISMA emphasizes the protection of

personally identifiable information (PII) and sensitive federal data. Federal
agencies and CSPs must implement measures to ensure the privacy and
confidentiality of such information.
8. Analyse the key elements of the functional architecture of Identity and Access CO 4.9 CL3
Management (IAM) that facilitate the management of user identities and their
access to resources within an organization's IT ecosystem, and how do these
components work together to provide a robust and secure IAM solution?
The functional architecture of Identity and Access Management (IAM) is

designed to facilitate the management of user identities and their access to
resources within an organization's IT ecosystem. IAM systems play a critical
role in ensuring proper authentication, authorization, and accountability while
maintaining security and compliance. The key elements of IAM's functional
architecture and how they work together to provide a robust and secure
solution are as follows:
Identity Lifecycle Management: This component covers the creation,

modification, and deletion of user identities. It includes processes for user
registration, onboarding, role assignment, and offboarding. Proper identity
lifecycle management ensures that user access is granted and revoked in a
controlled and consistent manner.
Authentication and Single Sign-On (SSO): IAM systems provide

mechanisms for authenticating users when they access applications and
resources. Single Sign-On enables users to access multiple applications with a
single set of credentials. Strong authentication methods, such as multi-factor
authentication (MFA), enhance security by requiring multiple forms of
verification.
Authorization and Role-Based Access Control (RBAC): Authorization

controls dictate what resources users are allowed to access and what actions
they can perform. Role-Based Access Control assigns roles to users based on
their job functions, and these roles determine their access permissions. This
approach simplifies access management and ensures principle of least
privilege.
Policy Management: Policy management involves defining and enforcing

access control policies across the organization. Policies determine who can
access which resources under what circumstances. IAM systems centralize
policy management to maintain consistency and reduce security gaps.
User Directory and Identity Store: User directories store user profiles,
attributes, and credentials. These directories serve as the authoritative source of
user identities and are often integrated with existing systems, such as Active
Directory or LDAP. IAM systems synchronize and manage these user
directories.
Access Request and Approval Workflow: Access request workflows allow

users to request access to specific resources. These requests are subject to
approval processes defined by the organization. IAM systems facilitate these
workflows, ensuring that proper authorization is obtained before granting
access.
Audit and Compliance Management: IAM systems maintain detailed audit
logs of user activities, access requests, approvals, and changes to access
permissions. These logs support compliance requirements, security
investigations, and accountability.
Provisioning and Deprovisioning: Provisioning involves setting up user

accounts, granting access, and assigning roles upon user onboarding.
Deprovisioning ensures that access is revoked and accounts are disabled or
deleted when users leave the organization. Automating these processes reduces
the risk of orphaned accounts.
Password Management and Self-Service: IAM systems offer self-service

capabilities for users to manage their passwords, reset forgotten passwords, and
update personal information. This reduces the burden on IT support while
enhancing security.
Integration and Federation: IAM solutions often integrate with various
applications, services, and directories to ensure consistent access control.
Federation enables users to access resources across different domains or
organizations using their home credentials.
APIs and Extensibility: IAM systems provide APIs to allow integration with
custom applications and external services. This extensibility ensures that the
IAM solution can adapt to the organization's evolving needs.
Centralized Management Console: A unified management console provides

administrators with a single interface to manage identities, access policies, and
security settings. This simplifies administration and enhances control.

191cs721 Cloud Computing QB With Answers PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

191cs721 Cloud Computing QB With Answers PDF

Uploaded by

Copyright:

Available Formats

VEL TECH MULTI TECH Dr.RANGARAJAN Dr.

SAKUNTHALA ENGINEERING COLLEGE

Sl.no Part A UNIT CL

11 Which one of the following statements is not true? CO1.3 CL1

15 Which of the following statement is not true? CO1.4 CL1

19 The Deployment process phase is ----------------------. CO1.5 CL1

a. Selecting Cloud Computing Provider

21 Cloud computing architecture is a combination of? CO1.6 CL1

a. service-oriented architecture and grid computing

29 Significant characteristics of Distributed systems have of CO1.8 CL1

Characteristics ofhigh computing power technology are

Parallel computing is often favored because the following reasons.

The logical arrangements of Software Styles areclassified as shown in Table below.

Data flow · Pipe and filter

Virtual machine · Rule-based system

Call and return · Top down systems

Number of Parallel computing occurs on one Distributed computing occurs

Processing In parallel computing multiple In distributed computing,

Synchronization All processors share a single There is no global clock in

Memory In Parallel computing, computers In Distributed computing,

Usage Parallel computing is used to Distributed computing is used

The ability of cloud resources to grow or shrink based on workload is a fundamental

Cloud computing enables the ability to increase or decrease computing resources

Parallel computing involves the simultaneous execution of multiple tasks or parts of

 Storage Maintenance Window Architecture diagram

13 Another name for the system virtual machine is CO2.4 CL1

e) All of the mentioned

The constraint of "statelessness" in RESTful APIs limits the scope of network

Common virtualization layers include

A hypervisor is a hardware virtualization technique allowing multiple operating

KVM Features are

Automated Scaling and Load Balancing:

Backup and Disaster Recovery:

Security and Compliance:

Seamless Application Portability:

Unified Interface with APIs and DevOps Tools:

Resource Optimization and Cost Management:

Infrastructure as a Service (IaaS):

Platform as a Service (PaaS):

Software as a Service (SaaS):

Automated Provisioning and Orchestration:

Cloud Resource Tagging and Naming Conventions:

Continuous Monitoring and Alerting:

Resource Right-Sizing and Optimization:

Scaling and Load Balancing Strategies:

Cloud Cost Management:

Performance Testing and Optimization:

Security and Compliance Monitoring:

Centralized Logging and Auditing:

Continuous Learning and Training:

Versioning is a critical feature in cloud storage services like Amazon S3

Data Replication and Redundancy:

Load Balancing and Traffic Management:

Content Delivery Networks (CDNs):

Compliance with Data Regulations:

Disaster Recovery and High Availability:

Reduced Network Congestion:

Distribution Channels and Sign-Ups:

Building and Maintaining Customer Relationships:

Onboarding and Training: Cloud storage providers focus on providing

For large objects, Amazon S3 offers a feature called "Multipart Upload" to

Key features of Multipart Upload in Amazon S3 include: