Cloud and Datacenter Architecture Flashcards

1
Q

Scalability

A
  • Costs involved in supplying more of the service linearly
  • If costs more than double for twice the users, it is less scalable
  • Horizontal/scaling out: adding more nodes
  • Vertical/scaling up: adding resources to each node
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Elasticity

A
  • Systems ability to handle changes in demand in real time

- Also able to reduce costs when demand is low

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Resouce pooling

A
  • Resources are not dedicated to single customer
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Virtualization

A
  • Provisioning resources using management software rather than hardware
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Public Cloud Model

A
  • Service offered to cloud consumers or tenants
  • Subscriptions or pay as you go financing
  • Often provide low tier services free of charge
  • Risks from shared resources involve performance and security
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Hosted Private

A
  • Hosted by a third party exclusive use for one org

- More secure and better performance but more expensive

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Private

A
  • Owned by org
  • One business unit often manages cloud services
  • Greater control
  • Often banking of government
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Community

A
  • Several orgs share costs of hosted private or fully private cloud
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Hybrid

A
  • A combination of the other cloud models

-

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

IaaS

A

Infrastructure as a Service

  • Provisioning servers, load balancers, SANs, etc. quickly.
  • Renting as needed from service providers data center
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

SaaS

A

Software as a Service

  • Access sofrware on vendors servers with Pay as you go or lease agreement.
  • Virtual infrastructure allows provisioning on demand quickly
  • Tested and developed in cloud without needing to be deployed on user computers
  • 365, Salesforce, Gsuite
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

PaaS

A

Platform as a Service

  • Somewhere between SaaS and Iaas
  • Deploys servers and storage but provides webapplication/database platform on top
  • Oracle or MS SQL or MySQL
  • Platform would not be configured to do anything
  • Your own developers would need to create software that runs using platforms like CRM or e-commerce
  • Provider is responsible for integrity of platform components
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

DaaS

A

Desktop as a Service

- Removes need for org to deploy and maintain client PCs and software installs

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

API

A

Application Programming Interface

  • Simplest way to access cloud services
  • Can also be implemented with VPN
  • Can suffer from performance issues from latency and bandwidth throttling
  • Should not be a solution for mission critical or high volume applications
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Internet/VPN Connection

A
  • Connecting to cloud services over website or API
  • VPN can be used if supported by cloud provider
  • Cost effective and easy to implement for distributed users
  • Can suffer from poor performance and latency from the public internet
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Colocation/Private direct

A
  • A direct link to the data center
  • Or customer infrastructure in Cloud provider data center
  • Better for orgs with more centralized operations where connection to cloud can be from main HQ
17
Q

IaC

A

Infrastructure as Code

- Infrastructure management where automation and orchestration to replace manual configuration

18
Q

Snowflake System

A
  • System with unique build or configuration

- Inconsistency creates security issues and problems as scripts fail because of configuration differences

19
Q

Automation

A
  • configuration and building done by code
  • Imperative: require precise steps to follow to achieve configuration. Similar to scripting languages
  • Declarative: Take desired configuration as input and leave details to implementation platform
20
Q

Orchestration

A
  • Performing a series of automated tasks

- Steps must take place in the correct sequence taking dependencies into account

21
Q

Cloud Responsibility Matrix

A
  • Identifying responsibilities you and the provider are taking in SLA