Cloud Computing Fundamentals: Concepts, Models, and Security, Exams of Biology

A comprehensive overview of cloud computing fundamentals, covering key concepts, service models, deployment models, security considerations, and data management. It explores various aspects of cloud computing, including virtualization, databases, orchestration, containers, and hypervisors. The document also delves into cloud security, data life cycle management, and data dispersion techniques. It is a valuable resource for students and professionals seeking to understand the basics of cloud computing.

Typology: Exams

2024/2025

Available from 01/08/2025

tutor-lee-1
tutor-lee-1 🇺🇸

4.3

(3)

11K documents

1 / 7

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
CCSP (2024) with complete
verified solutions
Cloud Computing Characteristics - answer On-Demand Self Service,
Rapid Elasticity & Scalability,
Broad Network Access,
Resource Pooling,
Measured Service
Cloud Computing Service Models - answer Infrastructure as a
Service (IaaS),
Platform as a Service (PaaS),
Software as a Service (SaaS)
Cloud Computing Deployment Models - answer Private, Public,
Hybrid, Community
Cloud Service Customer - answer One that consumes cloud
resources or organization that uses the cloud
Cloud Service Provider - answer Cloud Provider or Cloud Managed
Service Provider is the entity that provides cloud services or hosts
services in the cloud
Cloud Service Broker - answer Purchases services from a cloud
provider and makes them available to cloud consumers
Cloud Carrier - answer The entity that connects the cloud
customers to the cloud provider (ISP)
pf3
pf4
pf5

Partial preview of the text

Download Cloud Computing Fundamentals: Concepts, Models, and Security and more Exams Biology in PDF only on Docsity!

CCSP (2024) with complete

verified solutions

Cloud Computing Characteristics - answer On-Demand Self Service, Rapid Elasticity & Scalability, Broad Network Access, Resource Pooling, Measured Service Cloud Computing Service Models - answer Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Software as a Service (SaaS) Cloud Computing Deployment Models - answer Private, Public, Hybrid, Community Cloud Service Customer - answer One that consumes cloud resources or organization that uses the cloud Cloud Service Provider - answer Cloud Provider or Cloud Managed Service Provider is the entity that provides cloud services or hosts services in the cloud Cloud Service Broker - answer Purchases services from a cloud provider and makes them available to cloud consumers Cloud Carrier - answer The entity that connects the cloud customers to the cloud provider (ISP)

Virtualization - answer Abstracting applications/computer away from the underlying resources (OS & Hardware); requires a hypervisor Databases - answer Data stored in a way that makes it easily searchable/retrievable; relational; object-oriented Orchestration - answer Finding ways for functions to work together without being dependent for each other; Cloud Provider responsibility unless consumer is creating their own applications to access the cloud environment Containers - answer Synthetic platform that allows applications to run without being installed the underlying hardware; doesn't need an OS or hardware Hypervisor - answer Software that allocates CPU/RAM to the virtual instance; must be secured or users of another VM may "escape" and access other tenants environments or data Type 1 Hypervisor - answer Bare Metal; Runs on underlying hardware; more secure than Type 2; This hypervisor can be considered the OS for the VM's being hosted Type 2 Hypervisor - answer Hypervisor that runs on the OS already installed on the underlying hardware; functions similarly as an application alongside other applications; ex. Virtualbox, VMware Cloud Shared Considerations - answer Interoperability, portability, reversibility, availability, security, privacy, resiliency, performance, governance, maintenance and versioning, service levels and SLAs, auditability, regulatory

key distribution; Diffie-Hellman used to share key between two users Asymmetric Encryption - answer One key to encrypt, one key to decrypt; Can provide confidentiality and/or nonrepudiation; PKI; Public key is shared; Private key is held confidential by the owning user Key Management - answer Keys must be issued securely; Key Exposure = Data Exposure; Reissuing a key can be problematic and expensive; Losing a key = Losing data; Key Backup/Duplication increases risk; Key escrow solves Key backup/duplication risk: Key escrow is a 3rd party that manages, stores, and protects copies of keys; Best Practice: Never store keys along with the data/systems they are securing Cloud Access Security Broker (CASB) - answer Will perform key management between the Cloud Consumer and CSP; Security Groups - answer Set of rules/permissions is how entities interact with each other over a network; equivalent to network segmentation/isolation on-prem Container Security - answer Physical infrastructure should be protected/secured by the CSP in their data center; Communications within the container should be secure, applications should be isolated and can't share data by default; different applications shouldn't be able to communicate from different containers; Physical/Logical access control; Orchestration will prevent applications from becoming dependent of entities outside of themselves; Vulnerability management; Version control for containers, only current and improved containers should be used, versioning helps determine this information Cloud Data Life Cycle - answer CSU-SAD (Create, Store, Use, Share, Archive, Destroy)

Data Dispersion - answer Carves up files/datasets and distribute them across multiple physical/logical assets/locations. RAID in the cloud; Fault Tolerance, Resiliency, Security RAID vs. REDUNDANCY - answer Raid is fault tolerance (continue to work with issues) vs. Redundancy is replicated devices that take over operations Bit-splitting - answer Data Dispersion with encryption; Resiliency and Security Object Storage - answer Unstructured; Data stored as objects with labels/metadata/identifiers File Storage - answer Structured; Typically hierarchy; Data stored as files Raw-Disk/Block - answer Customer has access to unformatted disk space, which they can format/partition as they see fit Ephemeral - answer Transitory storage; Removed whenever instance is destroyed Tokenization - answer Not encryption; data is offloaded to a secure storage area and a token is issued to retrieved from other site Structured Data - answer Designed to be queried; Database Unstructured Data - answer Harder to accomplish data discovery; Data Discovery accomplished through Metadata, Labels (System or User defined), Content/Context/Analytics

DNSSEC - answer DNSSEC validation must be enabled on DNS clients; Does not require changes within any applications; DNS zones and DNS records must be digitally signed Functional Requirements - answer What do I need this app to do? Non-functional Requirements - answer What else would I like this app to be? SDLC Phase - answer Requirements Definition, Design, Development, Verification/Testing, Maintenance/Operation, ~Decommissioning Requirements Definition - answer Functional/Non-functional requirements are documented; Stakeholder inputs; Design - answer Software Developers scheme out how the software should be created; Data flows, operations, etc. NO ACTUAL CODING Development - answer Software is being built Verification/Testing - answer Takes place along the entire SDLC to make sure business requirements are being met Maintenance/Operation - answer Software is deployed into the production environment Software Methodologies - answer Waterfall, Spiral, Cleanroom, AGILE, DevSecOps, Continuous Integration/Continuous Delivery (CI/CD)