Scalable Systems Midterm 1

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/160

encourage image

There's no tags or description

Looks like no tags are added yet.

Last updated 2:28 AM on 9/28/26
Name
Mastery
Learn
Test
Matching
Spaced
Call with Kai
Chat

No analytics yet

Send a link to your students to track their progress

161 Terms

1
New cards

Cloud computing

On-demand network access to shared configurable resources that can be rapidly provisioned and released.

2
New cards

Provisioning vs. deployment

Provisioning creates/configures infrastructure; deployment places application code/configuration onto it.

3
New cards

On-demand self-service

Consumers can provision resources without a provider employee handling each request.

4
New cards

Broad network access

Cloud capabilities are available over networks through mechanisms usable by many client platforms.

5
New cards

Resource pooling

A provider dynamically assigns shared physical resources to isolated customers.

6
New cards

Rapid elasticity

Capacity can be acquired and released quickly as demand changes.

7
New cards

Measured service

The provider meters resource use, such as compute time, storage, requests, or transferred bytes.

8
New cards

Public cloud

Provider-owned infrastructure shared by many customers, such as AWS.

9
New cards

Private cloud

Cloud infrastructure reserved for one organization, even if some workloads are publicly reachable.

10
New cards

Hybrid cloud

A system that uses private/on-prem resources together with public-cloud resources.

11
New cards

Multicloud

Using resources from more than one public-cloud provider.

12
New cards

IaaS

Provider supplies infrastructure building blocks; customer manages the OS, software stack, and application.

13
New cards

PaaS

Provider operates the platform; customer deploys and remains responsible for its application code.

14
New cards

FaaS

A narrow PaaS model where customers provide event handlers and the provider supplies compute and scaling.

15
New cards

SaaS

Provider operates the application; customers mainly use and configure it.

16
New cards

Control plane

Operations that provision, configure, or delete resources.

17
New cards

Data plane

Normal steady-state work, such as an ALB forwarding a request to a backend.

18
New cards

Infrastructure as Code

Infrastructure described as versioned, reviewable, repeatable configuration rather than manual clicks.

19
New cards

AWS Console, CLI, and SDKs

Different clients that ultimately call the same AWS service APIs.

20
New cards

AWS Region

A geographic area containing multiple Availability Zones; most AWS resources belong to one Region.

21
New cards

Availability Zone

A failure-isolated group of datacenters inside one Region.

22
New cards

VPC

A virtual network that exists within one AWS Region.

23
New cards

Subnet

A range of VPC IP addresses that lies entirely within one Availability Zone.

24
New cards

What does choosing a subnet determine for an EC2 launch?

It determines the Availability Zone in which that instance launches.

25
New cards

Private IPv4 address

An address used within the VPC; it is not directly Internet-routable.

26
New cards

Public IPv4 address

An Internet-routable address AWS maps to an instance's private address.

27
New cards

Why is a public IPv4 address not enough for reachability?

A route must exist, security policy must allow traffic, and a process must be listening.

28
New cards

AMI

A reusable image that supplies an EC2 instance's starting software and storage configuration.

29
New cards

Does changing one running instance change its AMI?

No. Changes affect that instance's volume unless a new AMI is explicitly created.

30
New cards

Instance type

The EC2 configuration defining vCPUs, memory, architecture support, and network/storage performance limits.

31
New cards

Do more vCPUs automatically make one CPU-bound thread faster?

No. They allow more threads to run concurrently; one ready thread still runs on one vCPU at a time.

32
New cards

EBS volume

AWS-managed block storage attachable to an EC2 instance in the same Availability Zone.

33
New cards

Can an EBS volume attach directly across Availability Zones?

No. Create a snapshot and a new volume in the other AZ instead.

34
New cards

EBS snapshot

A point-in-time copy of an EBS volume that persists separately and can create new volumes.

35
New cards

AMI launch and root volumes

Each launch gets its own root volume, so later changes do not alter the AMI or another instance.

36
New cards

Process memory vs. EBS

Process memory is volatile; files on EBS can survive reboot and stop/start.

37
New cards

Security group

A set of stateful allow rules attached to a network interface.

38
New cards

What does 'stateful' mean for a security group?

If a connection is allowed in one direction, its response traffic is automatically allowed back.

39
New cards

What must exist for an EC2 connection to work?

An address, network path, network permission, access permission when needed, and a listening process.

40
New cards

Why can SSM replace direct SSH access?

SSM uses an outbound agent connection and AWS identity, so port 22 and distributed private SSH keys are unnecessary.

41
New cards

Instance role

An IAM role whose temporary credentials are made available to software running on an EC2 instance.

42
New cards

Instance role vs. administrator identity

The instance role controls the instance software's AWS calls; the administrator's identity controls their own AWS calls.

43
New cards

EC2 reboot

Restarts the OS; process memory is lost, but the instance, EBS volumes, NIC, private IP, and public IP remain.

44
New cards

EC2 stop/start

Loses process memory but keeps instance ID, EBS volumes, NIC, and private IP; an auto public IP changes.

45
New cards

EC2 termination

Permanently ends the instance; EBS volumes are deleted or retained according to DeleteOnTermination.

46
New cards

Why can a stopped EC2 instance still cost money?

Its compute charge stops, but retained EBS volumes and other allocated resources can still be billed.

47
New cards

P0 Region

us-west-2 (US West, Oregon).

48
New cards

P0 instance type

t3.nano.

49
New cards

P0 request path

Laptop -> SSM port forward -> Uvicorn -> FastAPI route -> in-memory dictionaries.

50
New cards

Management path

The route operators use to administer a system; it can differ from the application's client path.

51
New cards

systemd

Linux service manager that starts and supervises long-running processes such as the P0 URL shortener.

52
New cards

Uvicorn in P0

The HTTP application server process that accepts requests and invokes the FastAPI application.

53
New cards

127.0.0.1

Loopback: reachable only from the same machine.

54
New cards

0.0.0.0

Bind on all IPv4 interfaces, allowing connections through reachable non-loopback addresses too.

55
New cards

Why couldn't P0 be reached directly from the Internet?

Its security group allowed no inbound connection, and the app itself listened only on loopback.

56
New cards

SSM port forwarding

Maps a local laptop port through an authenticated SSM session to a port on the EC2 instance.

57
New cards

What does localhost mean?

The machine where the client is running; laptop localhost and EC2 localhost are different endpoints.

58
New cards

What does GET /health prove?

That the HTTP server and application can accept that request and return a successful response on the tested path.

59
New cards

Why can the wrong AWS Region make an instance look missing?

Regional resources have separate inventories; selecting another Region shows a different instance list.

60
New cards

Why does restarting the P0 process erase short links?

The application stores link state only in that process's memory.

61
New cards

Capability is not approval

A cloud API may technically permit an action even when policy or the assignment says you should not perform it.

62
New cards

Launch template

A versioned EC2 resource describing parameters for future instance launches.

63
New cards

What can a launch template include?

AMI, instance type, security groups, storage, instance role, user data, and other launch settings.

64
New cards

Does creating a launch template from an instance capture later filesystem changes?

No. It copies launch choices, not modifications made to the running instance afterward.

65
New cards

What does a new launch-template version change?

Future launches that use that version; it does not reconfigure already-running instances.

66
New cards

User data

Launch-time text, often a shell script, processed by cloud-init to configure a new instance.

67
New cards

cloud-init

Guest software that processes EC2 user data, normally during the instance's first boot.

68
New cards

Custom AMI vs. user-data setup

A custom AMI can start faster; user data keeps setup scripted but repeats work at every launch.

69
New cards

Vertical scaling

Change the capacity of one machine, such as moving to a larger EC2 instance type.

70
New cards

Horizontal scaling

Change the number of machines doing the work.

71
New cards

Why doesn't horizontal scaling always increase throughput?

A shared bottleneck, such as a database, may limit the whole system regardless of backend count.

72
New cards

Multiple instances in one AZ

They improve tolerance of individual-instance failure but not failure of that Availability Zone.

73
New cards

Why spread instances across AZs?

To reduce correlated failure risk if an entire Availability Zone becomes unavailable.

74
New cards

Reverse proxy

A server that accepts a client request and forwards it to another server.

75
New cards

Load balancer

A reverse proxy that chooses among multiple backend servers providing the same service.

76
New cards

Round-robin balancing

Rotate requests among eligible targets.

77
New cards

Least-outstanding-requests balancing

Prefer a target with fewer unfinished requests.

78
New cards

Health check

A probe used to decide whether a backend is eligible to receive traffic.

79
New cards

Application Load Balancer

AWS-managed HTTP/HTTPS reverse proxy that routes client requests to healthy targets.

80
New cards

ALB listener

The protocol and port on which an ALB accepts client connections.

81
New cards

ALB listener rule

Conditions plus an action, such as forwarding matching paths to a target group.

82
New cards

Target group

A named set of possible backends plus target port, health-check, and routing settings.

83
New cards

Target

A backend endpoint registered in a target group, such as an EC2 instance on port 8080.

84
New cards

Why did P1 bind Uvicorn to 0.0.0.0:8080?

The ALB and other VPC machines must reach the app through the instance's network interface, not only loopback.

85
New cards

Load balancer vs. Auto Scaling group

The load balancer distributes requests; the ASG changes how many EC2 instances exist.

86
New cards

Auto Scaling group

A resource that manages interchangeable EC2 instances using a launch template and selected subnets.

87
New cards

ASG minimum capacity

Lowest desired capacity the group may use.

88
New cards

ASG desired capacity

The current target number of instances the group tries to maintain.

89
New cards

ASG maximum capacity

Highest desired capacity the group may use.

90
New cards

Why isn't desired capacity the same as ready capacity?

Instances may still be launching, failing health checks, draining, or being replaced.

91
New cards

ASG scale-in and draining

The ASG deregisters a target, lets existing work drain, then terminates the instance.

92
New cards

ALB health vs. ASG replacement

ALB health controls routing; if enabled for the ASG, failed ALB health can also trigger replacement.

93
New cards

Manual scaling

An operator directly changes desired capacity.

94
New cards

Scheduled scaling

Capacity settings change at known future or recurring times.

95
New cards

Dynamic scaling

AWS changes desired capacity in response to metrics.

96
New cards

Target tracking

Dynamic scaling tries to keep a chosen metric near a target value.

97
New cards

Step scaling

Alarm ranges specify how much capacity to add or remove.

98
New cards

Stickiness

Routes a client's later requests to the same backend, but does not copy or preserve backend state.

99
New cards

Where should shared durable state live?

In an external database or service reachable by all replaceable application instances.

100
New cards

Main goal of P1a

Build a launch-template version that creates a working backend without manual repair.