Untitled Flashcards Set

Part I: Fundamental Concepts

1. Definition and Key Characteristics

Q: In your own words, define cloud computing. A: The on-demand delivery of computing services (e.g., servers, storage, databases, networking, software) over the internet, typically with pay-as-you-go pricing.

Q: Name any two essential characteristics of cloud computing as per common standards (e.g., NIST). A:

1. On-demand self-service

2. Broad network access

2. Service Models

Q: Briefly differentiate between Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) in terms of responsibilities shared by the provider and the customer. A:

• IaaS: Provides compute, storage, and networking resources. The customer manages the OS, middleware, and applications.

• PaaS: Provides an environment (runtime, frameworks, etc.) for application development. The provider manages infrastructure and OS maintenance.

3. Deployment Models

Q: Compare public cloud and private cloud in terms of ownership, resource sharing, and typical use cases. A:

• Public Cloud: Owned by third-party providers (e.g., AWS, Azure), resources are shared, used for scalability and cost-effectiveness.

• Private Cloud: Dedicated to one organization, offers greater control and security but higher costs.

4. Historical Milestone

Q: Identify one major milestone or event that significantly contributed to the modern concept of cloud computing and describe its impact. A: The launch of Amazon EC2 in 2006 introduced a pay-as-you-go model for virtual server instances, enabling organizations to rent compute capacity on demand.

Part II: Virtualization and Containers

5. Hypervisor-Based Virtualization

Q: What is a hypervisor, and why is it central to creating virtual machines? A: A hypervisor manages the creation and operation of virtual machines by abstracting physical hardware, enabling multiple VMs to share the same host securely and efficiently.

6. Containers vs. VMs

Q: List two advantages containers have over full virtual machines. A:

1. Faster startup times (lightweight, no separate guest OS).

2. More efficient resource usage (shared kernel).

Q: Name one potential drawback of container-based virtualization. A: Weaker isolation than full VMs since containers share the host OS kernel.

7. Container-Oriented Architecture

Q: Provide a brief scenario where containerization is beneficial. Explain why in one or two sentences. A: A microservices-based application benefits from containerization because each microservice can be packaged with its dependencies, allowing rapid deployment and scaling.

8. Scaling Approaches

Q: Define horizontal scaling versus vertical scaling and give an example of when each is most appropriate. A:

• Horizontal Scaling: Adding more instances/servers to handle increased load (e.g., adding multiple web servers behind a load balancer).

• Vertical Scaling: Increasing resources (CPU/RAM) on an existing machine (e.g., upgrading a server’s specs).

9. Load Balancing

Q: Explain the role of a load balancer in a cloud environment. A: Distributes incoming traffic across multiple servers to prevent overloading a single server and ensure high availability.

Q: How does it help achieve reliability and scalability? A: Redirects traffic to healthy instances if one fails, ensuring application availability and scalability.

Part III: Cloud Operations & Management

10. Auto-Scaling

Q: Describe auto-scaling and how it helps organizations handle variable workloads. A: Automatically adjusts the number of active instances/resources based on real-time metrics like CPU usage or network traffic, ensuring stable performance without manual intervention.

11. Shared Responsibility Model

Q: Under the cloud shared responsibility model, what are the security responsibilities of a cloud provider vs. a customer? A:

• Provider: Physical security, data center infrastructure, hypervisor/core cloud platform security.

• Customer: Data protection, access management, network configurations, secure service usage.

12. Cloud Storage

Q: Briefly compare object storage and block storage in the cloud. A:

• Object Storage: Stores data as objects identified by unique keys (e.g., Amazon S3), ideal for unstructured data.

• Block Storage: Provides raw block-level storage volumes (e.g., Amazon EBS), allowing OS installation and direct disk access.

13. Security and Compliance

Q: Name two common security threats in cloud computing and how to mitigate each. A:

1. Unauthorized access – Use strong authentication (MFA) and role-based access control.

2. Data breaches – Enable encryption at rest and in transit, with monitoring for anomalies.

14. Hybrid Cloud Scenario

Q: How should a mid-sized financial services company use a hybrid cloud? A:

• Private Cloud: Store sensitive customer data for compliance.

• Public Cloud: Run analytics workloads that fluctuate seasonally.

Q: Two challenges of hybrid cloud? A:

1. Complexity in integration and data transfer.

2. Maintaining consistent security and monitoring.

Part IV: Cloud Economics and Best Practices

15. Pricing Models

Q: List two common pricing models and when to use them. A:

1. On-Demand: Pay for usage, ideal for short-term or unpredictable workloads.

2. Reserved Instances: Commit for 1-3 years at a lower rate, ideal for stable workloads.

16. Reserved Instances

Q: What are reserved instances, and why choose them over on-demand? A:

• Prepaid instances for a set term at a lower cost.

• Best for predictable workloads to reduce expenses.

17. Spot Instances

Q: Describe a scenario where spot instances are useful and one risk of using them. A:

• Scenario: Large-scale batch processing jobs that can tolerate interruptions.

• Risk: Instance termination if market prices exceed the bid.

18. Cloud Cost Optimization

Q: Name two best practices for managing cloud costs. A:

1. Use auto-scaling and right-size instances.

2. Monitor usage and set budget alerts.

19. Case Study Takeaway

Q: What is one key lesson from cloud migration case studies? A: Plan migration carefully, ensuring compatibility and security before moving critical workloads.