Cloud Computing Exam Questions, Study notes of Applied Computing

A set of exam questions related to cloud computing. The questions cover topics such as the main characteristics of cloud computing, virtual appliances, full virtualization and para-virtualization, VME requirements, public and private cloud, platform as a service, security architecture design, application security, AWS services, and development technologies. The document also includes a section on challenges in cloud computing, computing platforms and technologies, virtualization for Linux and Windows, layered cloud architectural development design, secure software development life cycle, and GAE functional modules. The exam questions are suitable for university students studying information technology, computer science, and engineering.

Typology: Study notes

2023/2024

Available from 12/01/2023

divya-varsha
divya-varsha 🇮🇳

4 documents

1 / 36

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
UNIVERSITY QUESTIONS
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24

Partial preview of the text

Download Cloud Computing Exam Questions and more Study notes Applied Computing in PDF only on Docsity!

UNIVERSITY QUESTIONS

B.E./B.Tech. DEGREE EXAMINATIONS, NOVEMBER/DECEMBER 2021. Seventh/Eighth Semester Computer Science and

(b) Outline the various deployment models of cloud with neat sketch and identify which among them could be applied to formulate cloud structure for a small firm.

  1. (a) Represent the structure of inter-cloud resource management and explain why two or more clouds need to interact with each other. Provide an example for the same. Or (b) What is IAM and detail the segregation roles carried out by IAM when services of multiple organizations are maintained within the same geographical location?
  2. (a) Detail the structure of Openstack and explain each of its components. Or (b) Write detailed steps to set the google app engine environment for executing any program of your choice. PART C — (1 * 15 = 15 marks)
  3. (a) As a data center administrator, you are responsible to carry out the maintenance, operations, infrastructure design and management. If a primary computer system fails in the data center, elaborate the steps that must be carried out to overcome the failure. illustrate the same with a neat sketch. Or (b) Elaborate the working of MapReduce with an example. B.E./B.Tech. DEGREE EXAMINATIONS NOVEMBER/DECEMBER 2020 Seventh/Eighth Semester Computer Science and Engineering CS 8791 — CLOUD COMPUTING (Common to Computer and Communication Engineering/Information Technology) (Regulations 2017) Time : Three hours Maximum : 100 marks Answer ALL questions. PART A — (10 * 2 = 20 marks)
  4. List the main characteristics of cloud computing
  1. Illustrate the virtual appliances in cloud computing.
  2. Differentiate full virtualization and para-virtualization
  3. Outline the requirements of VMM.
  4. Differentiate Public cloud and Private cloud.
  5. Summarize the benefits and drawbacks of using “Platform as a Service”.
  6. Point out the layers in security architecture design.
  7. Identify the uses of application security.
  8. Outline the main services that are offered by AWS.
  9. Identify the development technologies currently supported by AppEngine. Part – B ( 5 x 13 = 65 Marks)
  10. a) Explain the following challenges in cloud. i) Security. ii) Data lock-in and Standardization. iii) Fault tolerance and Disaster recovery. OR b) Outline the computing platforms and technologies for the development of cloud computing applications.
  11. a) Explain the different phenomenon that has gained an interest towards virtualization technologies. OR b) Explain about Virtualization for Linux and Windows and NT Platform. Design the process of Live Migration of VM from one host to another.
  12. a) Explain the various Layered Cloud Architectural Development design for effective cloud computing environment. OR b) Demonstrate the architectural design of compute and storage clouds.
  13. a) Describe the Secure Software Development Life Cycle with neat diagram. OR

CS8791- CLOUD COMPUTING

NOV/DEC 2022 ANSWER KEY

1. What is the use of elasticity in cloud? Cloud Elasticity enables organizations to rapidly scale capacity up or down, either automatically or manually. Cloud Elasticity can refer to 'cloudbursting' from on-premises infrastructure into the public cloud for example to meet a sudden or seasonal demand. 2. Define on-demand provisioning? customers are provided with resources on runtime. In this delivery model, cloud resources are deployed to match customers' fluctuating demands. Deployments can scale up to accommodate spikes in usage and down when demands decrease. 3. Write the two major roles in SOA? There are two major roles within Service-oriented Architecture: Service provider: The service provider is the maintainer of the service and the organization that makes available one or more services for others to use. 4. Discuss the purpose of publish – subscribe model? The publish-subscribe (pub/sub) model enables event-driven architecture, which is required in several modern applications. You can use events to trigger and communicate between decoupled services. An event is a change in state, or an update, like an item being placed in a shopping cart. 5. Why do we need hybrid cloud? Justify The primary benefit of a hybrid cloud is agility. The need to adapt and change direction quickly is a core principle of a digital business. Your enterprise might want (or need) to combine public clouds, private clouds, and on-premises resources to gain the agility it needs for a competitive advantage. 6. Give the advantages of storage-as-a-service? The key benefit to STaaS is that you are offloading the cost and effort to manage data storage infrastructure and technology to a third-party CSP. This makes it much more effective to scale up storage resources without investing in new hardware or taking on configuration costs. 7. State the difference resource provisioning methods?

The three models are advanced provisioning, dynamic provisioning and user self-provisioning. With advanced provisioning, the customer signs a formal contract of service with the cloud provider. The provider then prepares the agreed-upon resources or services for the customer and delivers them.

8. Illustrate password assurance testing? Password Assurance Testing is a service that can be used to harness the computational power of the cloud in attempts to break into a company's system by guessing passwords. This approach minimizes resources and time spent on the client side. 9. Give some of the application of GAE. What are the benefits of cloud federation? Google App Engine (often referred to by the acronym GAE or simply App Engine) is a cloud computing platform as a service for developing and hosting web applications in Google- managed data centers. Applications are sandboxed and run across multiple servers.

  1. What is the use of the Google SDC secure data connection? What are the benefits of cloud federation? It minimizes the time and cost of providers due to dynamic scalability. It connects various cloud service providers globally. The providers may buy and sell services on demand. It provides easy scaling up of resources. Secure Data Connector agent is a reference implementation of the Google Secure Data Connector protocol. This protocol allows Google Apps Premier & Google Apps for Education customers to make available specific resources that Google's hosted applications (the cloud) can access inside the customer's network. **PART – B
  2. (a) illustrate in detail about parallel and distributed programming models?** The new developments in parallel and distributed systems in cloud computing with significant research ideas, directions, and technologies!!! Due to the vast number of benefits, parallel and distributed systems are growing fast in the cloud computing field. Since these concepts are keen to understand the technical issues and functional requirements in the design of the best cloud systems. Our resource teams have so many years of experience in handling parallel and distributed computing models. So, we are always passionate to create continuous achievements in the field of cloud computing. This makes our handhold research scholars and final year students select us all the time for their dream projects. Here, we have given you some main benefits of parallel and distributed systems in cloud computing. efits of Parallel and Distributed Computing

Cloud computing is all about renting computing services. This idea first came in the 1950s. In making cloud computing what it is today, five technologies played a vital role. These are distributed systems and its peripherals, virtualization, web 2.0, service orientation and utility computing ● Distributed Systems: It is a composition of multiple independent systems but all of them are depicted as a single entity to the users. The purpose of distributed systems is to share resources and also use them effectively and efficiently. Distributed systems possess characteristics such as scalability, concurrency, continuous availability, heterogeneity, and independence in failures. But the main problem with this system was that all the systems were required to be present at the same geographical location. Thus to solve this problem, distributed computing led to three more types of computing and they were-Mainframe computing, cluster computing, and grid computing. ● Mainframe computing: Mainframes which first came into existence in 1951 are highly powerful and reliable computing machines. These are responsible for handling large data such as massive input-output operations. Even today these are used for bulk processing tasks such as online transactions etc. These systems have almost no downtime with high fault tolerance. After distributed computing, these increased the processing capabilities of the system. But these were very expensive. To reduce this cost, cluster computing came as an alternative to mainframe technology. ● Cluster computing: In 1980s, cluster computing came as an alternative to mainframe computing. Each machine in the cluster was connected to each other by a network with high bandwidth. These were way cheaper than those mainframe systems. These were equally capable of high computations. Also, new nodes could easily be added to the cluster if it was required. Thus, the problem of the cost was solved to some extent but the problem related to geographical restrictions still pertained. To solve this, the concept of grid computing was introduced. ● Grid computing: In 1990s, the concept of grid computing was introduced. It means that different systems were placed at entirely different geographical locations and these all were connected via the internet.

These systems belonged to different organizations and thus the grid consisted of heterogeneous nodes. Although it solved some problems but new problems emerged as the distance between the nodes increased. The main problem which was encountered was the low availability of high bandwidth connectivity and with it other network associated issues. Thus. cloud computing is often referred to as “Successor of grid computing”. ● Virtualization: It was introduced nearly 40 years back. It refers to the process of creating a virtual layer over the hardware which allows the user to run multiple instances simultaneously on the hardware. It is a key technology used in cloud computing. It is the base on which major cloud computing services such as Amazon EC2, VMware vCloud, etc work on. Hardware virtualization is still one of the most common types of virtualization. ● Web 2.0: It is the interface through which the cloud computing services interact with the clients. It is because of Web 2.0 that we have interactive and dynamic web pages. It also increases flexibility among web pages. Popular examples of web 2.0 include Google Maps, Facebook, Twitter, etc. Needless to say, social media is possible because of this technology only. It gained major popularity in 2004. ● Service orientation: It acts as a reference model for cloud computing. It supports low-cost, flexible, and evolvable applications. Two important concepts were introduced in this computing model. These were Quality of Service (QoS) which also includes the SLA (Service Level Agreement) and Software as a Service (SaaS). ● Utility computing: It is a computing model that defines service provisioning techniques for services such as compute services along with other major services such as storage, infrastructure, etc which are provisioned on a pay-per-use basis.

12. (a) Describe in detail about the REST a software architecture style for distributed systems? REpresentational State Transfer (REST) is a software architectural style that defines the constraints to create web services. The web services that follows the REST architectural style is called RESTful Web Services. It differentiates between the computer system and web services. The REST architectural style describes the six barriers.

customer's data codes. Servers are not connected with the user interface or user status to make the server simpler and scalable. Servers and clients are independently replaced and developed until the interface is changed.

  1. Stateless Stateless means the state of the service doesn't persist between subsequent requests and response. It means that the request itself contains the state required to handle the request. It can be a query-string parameter, entity, or header as a part of the URI. The URI identifies the resource and state (or state change) of that resource in the unit. After the server performs the appropriate state or status piece (s) that matters are sent back to the client through the header, status, and response body. o Most of us in the industry have been accustomed to programming with a container, which gives us the concept of "session," which maintains the status among multiple HTTP requests. In REST , the client may include all information to fulfil the server's request and multiple requests in the state. Statelessness enables greater scalability because the server does not maintain, update , or communicate any session state. The resource state is the data that defines a resource representation. Example, the data stored in a database. Consider the application state of having data that may vary according to client and request. The resource state is constant for every customer who requests it.
  2. Layered system It is directly connected to the end server or by any intermediary whether a client cannot tell. Intermediate servers improve the system scalability by enabling load-balancing and providing a shared cache. Layers can enforce security policies.
  3. Cacheable On the World Wide Web, customers can cache responses. Therefore, responses clearly define themselves as unacceptable or prevent customers from reusing stale or inappropriate data to further requests. Well-managed caching eliminates some client-server interactions to improving scalability and performance.
  4. Code on Demand (optional) The server temporarily moves or optimizes the functionality of a client by logic that it executes. Examples of compiled components are Java applets and client-side scripts. Compliance with the constraints will enable any distributed hypermedia system with desirable contingency properties such as performance, scalability, variability, visibility, portability, and reliability.

(b) Illustrate the migration steps and performance effects involved in live VM. The phases a particular VM undergoes during a migration to Google Cloud. Some phases are optional, and others are unavailable during cloud-to-cloud migrations. Full migration The full migration operation moves VMs in one step from source to target. In doing so, it:

  1. Performs the run-in-cloud process.
  2. Waits for the VMs to be in the Cache on Demand state, when storage is streamed to the cloud.
  3. Migrates the VM data to Google Cloud.
  4. After storage is fully copied to Google Cloud, prepares the VM to detach. When this process has completed, the VM state changes to Ready to Detach. Full migration is an automatic process that includes the following tasks (which you can also run manually). ● run-in-cloud ● storage migration ● prepare to detach Run-in-cloud This operation moves the source VMs from your on-premises data center to Google Cloud. This does not completely move VM storage to the cloud -- you migrate storage with storage migration. The run-in-cloud operation:
  5. Shuts down the source VMs.
  6. Attaches to the VM's volumes.
  7. Starts the VM on Google Cloud, streaming storage as needed. Storage migration

A test clone creates clones of selected VMs to test them in Compute Engine. The test clone behaves like the live systems and leverages data from the source VM. However, test clones do not modify any live data because data from the test environment is not written back on-premises. Upon creating a test clone, Migrate for Compute Engine:

  1. Attaches to the VM volumes.
  2. Starts each instance in Google Cloud. Storage is streamed from the VM to Google Cloud. migration lifecycle Delete clone Deleting the test clone removes it from Google Cloud. Note that deleting the test clone has no impact whatsoever on your live system or data. Any changes made to data in the test clone are not replicated back to your live system. Offline migration Migrate for Compute Engine can migrate workloads with operating systems or file systems that Migrate for Compute Engine's streaming technology does not support, but that the cloud environment does support. See Supported operating systems for a list of operating systems supported for offline migration. During the offline migration process, Migrate for Compute Engine:
  3. Migrates storage.
  4. Starts the new VM only after migration is completed.
  5. Detaches the VM. 13.(a) Discuss the features of software as a service and explain in detail about SaaS with example? As the global Software as a Service (SaaS) market experiences a rapid growth, more and more SaaS based applications are flooding the market. Are all these applications really SaaS or the vendors applying the SaaS tag to just about everything? It will be interesting to know what exactly constitutes a Software as a Service (SaaS) application. Some of the must have or nice to have features and key characteristics of SaaS applications are the following: ● - Multi-tenancy model

● - Automated provisioning ● - Single Sign On ● - Subscription based billing ● - High availability ● - Elastic Infrastructure ● - Data Security ● - Application Security ● - Rate limiting/QoS ● - Audit Multi-tenancy Model Multi-tenancy is a kind of software architecture in which a single deployment of a software application serves multiple customers. Each customer is called a tenant. Tenants may be given the ability to customize some parts of the application, now a days applications are designed in a such a way that per tenant, the storage area is segregated by having different database altogether or having a different sachems inside a single database or same database with discriminators. Automated Provisioning The users should be able to access the SaaS applications on the fly, which means the process of provisioning the users with the services needs to be automated. SaaS applications are typically used by B2B/B2C customers and this requirement demands creating companies/users just by invoking web services and provide the access credentials. Most of the SaaS applications provide this critical feature and a great example would be CREST API from Microsoft. Cloud Services Broker (CSB) platforms can automate this procedure to provide access to SaaS applications on demand basis. Another important characteristic is the de-provisioning ability - remove the access from the user/organizations whenever the customer decides not to use the Software as a Service applications. A good example for this is Salesforce, used by sales folks to manage the sales related operations. Typically, Salesforce tenant gets created for an organization with unique identification by invoking APIs of Saleforce. Another set of APIs are called to create users under the tenant and the access credentials are shared to user. Also delete API is called for when an organization decides to discontinue the application. Single Sign On An enterprise organization would want to have a single identity system in place in order to authenticate the various systems which are going to be consumed by users. Also, it is important for enterprises to have a single page to provide login credentials and access all Software as a Service applications provisioned to the respective users. So, Software as a Service applications should be easily integrated with various identity management systems without much change. It is also a big maintenance overhead for enterprises to store & maintain multiple credentials per system which are used by enterprise users. So it becomes important to enable Single Sign On for SaaS applications to authenticate against existing identity system and provide an experience of logging in once and use the various systems. Typically, Software as a Service applications use SAML or OpenID kind of impersonations to enable this critical piece. Also, another important factor is that the SaaS applications are multi-tenant, each tenant would want to authenticate against their own identity & access management system.

SaaS applications should be equipped with protection against vulnerabilities. Typically, they should be protected against OWASP/SAN identified vulnerabilities. Also, strong identity and access management controls should be enabled for SaaS applications. The other aspects that make the Software as a Service application secure are the following: ● Strong session management, protection against hijack the session ● Identifying unauthorized session, protection against multi-session etc. ● Usage of cookies not storing sensitive data, follow Cookie etc. ● Step-Up authentication like password lock out etc. ● Multi factor authentication ● Strong implementation on separation of duties ● Protection against DoS/DDoS ● Protection against buffer overflow attacks ● Also integration points open with CASB will help in gaining confidence of the customers. Rate Limiting/QoS Every business has preferred/important users apart from the regular list of users using the applications. These days, in order to provide better service to all class of customers, rate limiting is a good feature to have. The number of hits/ number of transaction can be technically limited to ensure the smooth business transactions. Also, SaaS applications can be enabled with Rate limiting/QoS configure-ability which helps organizations to manage their user base. Audit Generally SaaS applications are equipped with providing audit logs of business transactions and this enables customers to work out a business strategy by applying business intelligence plans. These services also should be able to comply with government regulations and internal policies. (b) (i) compare and contrast : public, private and hybrid cloud? The term cloud computing spans a range of classifications, types, and architecture models. This networked computing model has transformed how we work—you’re likely already using the cloud. But the cloud isn’t one thing—cloud computing can be categorized into three general types: ● Public cloud is cloud computing that’s delivered via the internet and shared across organizations. ● Private cloud is cloud computing that is dedicated solely to your organization. ● Hybrid cloud is any environment that uses both public and private clouds. This article looks at cloud computing at the highest level by: ● Defining cloud computing ● Exploring public, private, and hybrid cloud environments ● Sharing use cases and examples Public vs private vs hybrid cloud: At a glance

(ii) List the architectural design challenges in cloud computing? Introduction Cloud computing is an emerging technology and has many challenges in various aspects of information handling. Challenges in Cloud Computing