practitioner Flashcards

1
Q

Advantages of cloud computing

A

1) trade capital expense to variable expense
2) Benefit from massive economies of scale
3) stop guessing about capacity
4) Increase speed and agility
5) Stop spending money running and maintaining data centers
6) go global in minutes

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

choosing the right AWS region

A

1) Data sovereignty Laws
2) Latency to end user
3) AWS service (is present in that region or not)

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

Setting up billing alarm

A

-> CloudWatch -> billing -> click create alarm -> activate SNS (simple notification service )

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

different ways to access AWS (IAM)

A

1) programmatic access( using the command line)
2) Aws management console
3) Using SDKs ( software development kits)

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

IAM set user permission

A

1) add the user to a group (the “group” is a place to store users and they will inherit all the permission at that group)
2) copy permission from the existing user
3) attach existing policies directly (policies are basically Json script)

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

IAM identity access management

A

when we create a user/group it is created globally
ie identity created is not region specific

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

IAM best practice

A

1) root account for only creating account and not login

2)one user = one real human ( no platform user )

3) use group/policies for better management of user

4) have strong password policies

5)MFA

6)ROLES for AWS service communication with each other )

7)Access key (programmatic access)

8) IAM credential report ( to audit permission for the user/group)

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

IAM credential report

A

list all users and the details about the Password (if Changed regularly or not) Access key, MFA ( on or off)

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

S3 ( simple storage services )

A

dksndol

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

Basic of S3

A

1) the name must be unique globally

2) URL syntax “ https://s3-(? region).amazonaws.com/(bucket name)

3)http-200 means upload is successful

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

characteristics of object present in the S3

A

1) Key(name)

2)value(the object itself)

3) versionID

4)metadata (info/comments about the data present)

5)Sub resource :-
access control list
torrent

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

S3 features

A

1) Tiered storage available
2) life-cycle management
3) versioning
4) encryption
5) secure using access control list and bucket policies

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

S3 storage tier

A

-> standard
-> IA(infrequently accessed)
-> one zone IA
-> intelligent tier
-> s3 glacier Instant Retrieval
-> s3 glacier Flexible Retrieval
-> s3 glacier deep archive

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

s3 for what all charges are applicable

A

-> storage
->request
-> Storage management pricing
->data transfer
-> transfer acceleration
-> cross-region replication

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

restricting bucket access

A

-> bucket policies (applied for entire bucket)
-> object policies (applied for individual files)
->IAM

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

cloud front types of distribution

A

-> Web distribution (mainly for websites)

-> RTMP(for media streaming)

17
Q

Why Roles

A

roles are much more secure than using access key and secret access key and also easy to manage

like IAM these are not region specific

18
Q

OLTP and OLAP

A

-> online transaction processing ( used to fetch normal application query wrt data )
-> online analytic processing ( used to pull large data for business intelligence ) data warehousing

19
Q

Load balancer Types

A

-> Application load balancer (layer 7 makes an intelligent decision)
-> Network load balancer (extreme performance /static IP)
-> Classic load balancer( test and dev low cost)

target group are attached so that when a request comes at port 80 will be shifting the load to the instance present in the target group ( attach suitable sg to allow 80 requests)

20
Q

RDS (types of database engine)

A

-> SQL server ( Microsoft)
-> oracle
-> MySql server
-> postgress
->Aurora
->Maria db
-> dynamoDB ( NON RDS !! )

21
Q

RDS key features

A

-> multi AZ ( for disaster recovery )
-> read replicas ( for performance )

22
Q

Data warehouse

A

use for different types of architecture both from a database perspective and infrastructure layer ( redshift )

23
Q

ElastiCache

A

is a web service that makes it easy to deploy, operate, and scale an in-memory cache in the cloud. The service improves the performance of web applications by allowing you to retrieve information from fast, managed, in-memory caches, instead of relying entirely on slower disk-based databases.

-> redis
-> memcached

24
Q

Elastic Beanstalk

A

quickly run the application without worrying about the infrastructure that runs these application

25
Q

traditional vs cloud

A

-> IT assets are provisioned resources
-> Global, available, and scalable
-> higher-level managed service
-> built-in security
-> Architecting for cost
-> operations on AWS

26
Q

Scalability

A

-> scale up
-> scale out
-> stateless application (lambda)
-> distributed load to multiple node
-> stateless components (cookies)
-> stateful components (shopping cart details)
-> implement session affinity (sticky session )
-> distributed processing

27
Q

Disposable resource insted of fixed

A

-> instantiating compute resource
-> bootstrapping
-> golden images
-> containers
-> hybrid
-> infrastructure as code
->cloud formation

28
Q

Automation

A

-> Serverless management and deployment
-> infrastructure management
-> beanstalk
-> ec2 auto-recovery
-> system manager
-> auto-scaling
-> alarms and events
-> cloudwatch alarms
-> cloudwatch event
-> lambda seheduled
-> WAF security automation

29
Q

service not servers

A

managed services
serverless architecture

30
Q

AWS global service

A

IAM
ROute53
cloud frount
sns
ses

31
Q

AWS service to on-prem

A

snowball (80 TB)
snowball edge (basically computer van use lambda )
storage gateway ( stays in on-prem)
code deploy
ops-works
iot greengrass

32
Q

cloud watch

A

monitoring service to monitor AWS resources and applications in AWS
-> ec2
-> auto scaling groups
-> load balancer
-> rout53
-> ebs
-> storage gateway
-> cloudfrount

33
Q

aws systems manager

A

-> manage fleets ec2 instance and vm
-> Peace of software is installed in each ec2
-> can be both inside AWS and on-prem
-> Use the run command to install patch software
-> Integrate with cloudwatch

34
Q

service health dashboard

A

-> overview of all region
-> historical info on AWS service ( daily basis)’
-> RSS feeds