Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

AWS Cloud Architect > Module2: Introduction to Cloud Architecting > Flashcards

Module2: Introduction to Cloud Architecting Flashcards

1
Q

Role of the cloud architect

A

Apply best practice for a cloud service aiming at meeting technical and business needs through the application of the AWS well architected framework

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

Cloud Architect mindset

A

Backward: From the business need to the architecture

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

Year of Commercial appearance of AWS

A

2006

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

First AWS services

A

Amazon Simple Queue Services (SQS)
Simple Storage Services (S3)
Amazon Elastic Cloud Compute (EC2)

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

Cloud architecting lifecycle

A

Plan: Set technical strategies with business leads
Analyse solution to business need

Research: Investigate cloud services and workload requirement
Review existing architectures
Design prototype solutions

Build: Design the roadmap with milestones work streams and owner
Manage adoption and migration

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

6 Pillars of the AWS well architected framework

A
  • Operational Excellence
  • Security
  • Reliability
  • Performance Efficiency
  • Cost optimisation
  • Sustainability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

The operational Excellence pillar

A
  • Run and Monitor systems that deliver business value
  • Continually improve supporting processes and procedures
  • View the entire workload as code
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

The security pillar

A

*Strong identity foundation (who has a key)
*Traceability (who opened a door)
*Security at all layers (Not because you enter the building that you can go into the safe)
*Risk assessment and mitigation strategies (if fire where are extinguishers, exit routes)

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

The Reliability pillar

A

*Recover quickly
*Dynamically meet demande
*Mitigate disruptions

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

The Performance efficiency pillar

A

*Choose and maintain efficient resources
*Democratize advanced technologies
*Employ mechanical Sympathy (use a tool with the knowledge of how it operates best)

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

The cost optimization pillar

A

*Measure efficiency
*Elimiate uneeded expense
*Adopt the right consumption model
*Consider using managed services

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

The sustainability pillar

A

*Establish sustainability goals
*Maximize utilisation
*Choose efficient hardware and software
*Reduce downstream impact

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

The AWS WA Tool

A

Review your workload and compare to best practices.
Delivers action plan
Provide a step by step guidance
consistent process to review and measure the architecture
Accessible in the management console

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

What is a trade off?

A

what you prioritoze depending on your need. But what you gain on one side, you may loose in the other:
Cost vs performance
Consistency and durability vs latency
…
Base your trade on empirical data and testing

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

What are anti patterns?

A

Bad solution design

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

Where should we be scalable ?

A

At every layer (everywhere)

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

How to be scalable?

A

Amazon CloudWatch can detect the load on the server CPU. A certain load for a certain period can trigger the increase or decrease of capacity through an alarm.
The alarm will trigger EC2 Auto Scaling.
Should go both ways (Up and down)

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

What is being elastic

A

Capacity to adjust resources up and downward to the workload

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

Best practice 1 :

A

Scalability

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

How are scalability and automation linked

A

With automation, you save time in being reactive to the workload

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

Best practice 2:

A

Automation

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

How to automate

A

CloudWatch => EC2 auto scaling => Automatic alarms => Log and tracking

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

Best Practice 3:

A

Use IaC

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

What’s IaC

A

infrastructure as Code: Provision your infrastructure as code (programmatically) instead of doing it manually.
Deploy duplicate, reduce config error, propagate changes…

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

Common use of IAC

A

Build test and deploy applications

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

Best practice 4:

A

Treat ressources as disposable.
Automate, test, stop, replace, update.
Don’t get attached. Ressources are kleenex. Good hygiene is to replace,

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

Best practice 5:

A

Loosely coupled components

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

What does loosely coupled components mean

A

Don’t make your infrastructure too rigid by tighing components togethers. Use tool like Elastic Load balancing to dynamically engage ressources, handle failures and scale components.

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

Two solutions to decouple components?

A

*Load balancer
*Message queues

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

Best practice 6:

A

Design services not servers

31
Q

Design services not servers: meaning?

A

EC2 let’s you design your server.
But!! Don’t rely only on that.
Use Container or serverless solutions when appropriate.
Message queues to communicate
Web assets can be stored off server (S3)
Authentification can be handled by aws.

32
Q

Services supporting best practice 6:

A

Lambda functions
SQS messaging
DynamoDB (no sql database)
ELB (Loa balancer)
SES (Simple email)
Cognito (Identification)

33
Q

Best practice 7:

A

Choose the right database

34
Q

How to choose the right database?

A

Read and write neeeds
Storage requirements
Object size and nature
Durability requirements
Latency requirements
# of users
nature of queries
strength of integrity control

35
Q

Best practice 8:

A

Avoid single points of failure

36
Q

How to think to avod single points of failure?

A

Assume everything fails. Then design backwards

37
Q

How to avoid single point of failure?

A

Duplicate when needed to min. downtime depending on your SLAs.
Common practice is to have a secondary database server provisionned with an image of the primary at regular intervals. If the primary goes offline then secondary takes over

38
Q

Best practice 9:

A

Optimize for cost

39
Q

How to optimize for cost

A

WHAT METRICS SHOULD I MONITOR
RIGHT SIZING
TURN OFF
HOW FREQUENT DO I NEED THIS RESSOURCE
CAN I REPLACE WITH MANAGED SERVICES

40
Q

Best practice 10:

A

Use caching

41
Q

What is caching

A

technique where upon first request, data is temporarily stored closer to the user, and reused for the subsequent request. Allows to make dat available more quickly

42
Q

What does caching rely on?

A

Cloud Front and edge location

43
Q

Benefits of caching

A

Quicker (Low latency) but also cheaper because not pulled from S3 anymore when cached.

44
Q

Best practice 11:

A

Secure the entire infrastructure

45
Q

How to secure the entire infrastructure?

A

Use managed ressources
Log
Isolate
Encrypt at rest and in transit
Granular access control
MFA
Automate deployments to keep security consistent

46
Q

Key takeaways: Best practices for building solutions on AWS

A

As you design solutions, evaluate trade-offs and base your decisions on empirical data
Follow these best practices when building solutions on AWS:
Implement scalability
.Automate your environment.
Treat resources as disposable
.Use loosely-coupled components.
Design services, not servers.
Choose the right database solution
.Avoid single points of failure.Optimize for cost
.*Use caching.
*Secure your entire infrastructure

47
Q

Regions

A

32

48
Q

AZ

A

102

49
Q

Data centers

A

200

50
Q

What geographical feature for low latency ?

A

PoPs (Point of presence)
Regional Edge Caches

=> Edgel locations

51
Q

Why choose a spcific region

A

Regulation and conformity to laws applicable to org

52
Q

Why choose a specific Availability Zone

A

To keep close to user and reduce latency

53
Q

Why choose multiple AZ

A

To mitigate risks

54
Q

AWS Gov CLoud

A

Restricted access for sensitive data requires special authorization

55
Q

Are regions isolated

A

YES

56
Q

Several AZ in region can one fail without impacting the others?

A

Yes. Built for failure independance. Located low risk site with power supply.
Plan for disaster and distribute accross AZ

57
Q

Local Zones

A

Exist close to areas wher no region exists to lower latency

58
Q

Define Operational Excellence in the context of the Well-Architected Framework.

A

The ability to run and monitor systems to deliver business value and continually improve processes and procedures.

59
Q

Explain Reliability in the AWS Well-Architected Framework.

A

The ability of a system to recover from failures and meet customer demands.

60
Q

What are Well-Architected Tool’s main functions?

A

To assess workloads against the Well-Architected Framework and provide recommendations.

61
Q

What is the importance of “failover” in Reliability?

A

Ensuring that applications can automatically switch to a backup system in case of failure.

62
Q

How does AWS CloudTrail contribute to security?

A

By logging and monitoring account activity to track changes and detect anomalies.

63
Q

Define “decoupling” in system architecture.

A

Designing systems so that components are independent, reducing the impact of failures.

64
Q

What is the significance of Auto Scaling in Performance Efficiency?

A

Automatically adjusts resources to maintain performance and minimize costs.

65
Q

What is Amazon CloudFront?

A

Content Delivery Network (CDN) that speeds up the distribution of static and dynamic web content.

66
Q

How many Availability Zones are typically found in an AWS Region?

A) At least one
B) Two or more
C) Five

A

B

67
Q

Which AWS service helps monitor resource utilization?

A) CloudWatch
B) CloudFormation
C) IAM

A

A

68
Q

What is the primary function of AWS Auto Scaling?

A) Load balancing
B) Cost allocation
C) Dynamic resource adjustment

A

C

69
Q

What is the main purpose of Edge Locations?

A) Hosting databases
B) Providing low-latency content delivery
C) Managing User identitites

A

B

70
Q

What does AWS Config help with?

A) Performance metrics
B) Tracking resource compliance and changes
C) User management

A

B

71
Q

What is a common strategy for improving Reliability?

A) Reducing redundancy
B) Implementing failover solutions
C) Increasing costs

A

B

72
Q

In the context of the Well-Architected Framework, what is “decoupling”?

A) Combining services for efficiency
B) Isolating components to improve resilience
C) Reducing costs by eliminating services

A

B

73
Q

Which service is used to create a secure network infrastructure?

A) VPC
B) S3
C) EC2

A

A

AWS Cloud Architect (16 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions