Week 4 and terms
Week 4 and terms
Week 4 and terms
Week 4 and terms
Week 4 and terms
100

What is the purpose of backup in cloud computing?

Backup involves creating copies of data or resources to protect against accidental loss, corruption, or system failures.

100

Refers to the process of setting up and configuring infrastructure and resources required for software development, testing, and deployment.

Provisioning

100

Refers to the allocation and management of data storage resources in the cloud, including object storage, block storage, and file storage.

Storage

100

Involves identifying, analyzing, and evaluating potential risks associated with cloud services and their impact on an organization.

Risk assessment

100

These are documented step-by-step instructions that outline how to perform routine tasks or processes in a consistent and standardized manner.

Standard operating procedures (SOPs)

200

These are triggered by predefined thresholds or events to inform administrators or users about potential issues or changes in the cloud environment.

Alerts

200

Involves managing and tracking changes to software, hardware, and infrastructure configurations to maintain consistency and reliability.

Configuration management

200

These are methods of allocating and tracking costs based on resource usage, allowing organizations to assign costs to specific departments or users.

Chargebacks

200

Refers to the process of identifying and documenting the cloud-related assets and resources utilized by an organization

Asset inventory

200

Refers to the structured approach and processes used to plan, coordinate, and implement changes in an organization while minimizing disruption and risk.

Change management

300

Involves replicating data or resources across multiple geographic regions to ensure high availability and disaster recovery capabilities.

Geo-redundancy

300

Involves simulating high user loads to measure the performance and stability of an application or system under expected or peak usage conditions.

Load testing

300

Refers to the activities and costs associated with keeping cloud resources up to date, secure, and optimized for performance.

Maintenance

300

Refers to the actions taken to address identified risks, which may include risk mitigation, risk avoidance, risk acceptance, or risk transfer.

Risk response

300

Guidelines and rules that define how an organization protects its assets, data, and information systems from unauthorized access, breaches, and vulnerabilities.

Security policies

400

Refers to the placement of data or resources in close proximity to the users or applications that require them, reducing latency and improving performance.

Locality

400

Involves coordinating and automating multiple tasks, processes, or services to achieve seamless deployment and management of applications and infrastructure.

Orchestration

400

Pricing model offered by cloud providers where unused or spare cloud resources are made available at discounted prices.

 Spot instances

400

Involves implementing controls and measures to reduce the likelihood or impact of identified risks in cloud services.

Mitigation

400

Is the process of handling and mitigating security incidents or breaches to minimize damage, restore services, and prevent future occurrences.

Incident response

500

Involves the organization, storage, and manipulation of data within the cloud environment.

Data management

500

Ensures that recent changes or updates to an application do not introduce new defects or negatively impact existing functionality.

Regression testing

500

Are long-term commitments made to cloud providers in exchange for lower pricing on compute resources?

Reserved instances

500

Refers to the potential dependency and difficulty in switching cloud service providers due to proprietary technologies or contractual terms.

Vendor lock-in

500

Outline the rules and guidelines for effective and appropriate communication within an organization, including email usage, confidentiality, and information sharing.

Communication policies

M
e
n
u