Serverless Flashcards

1
Q

developers don’t have to manage servers anymore they just deploy code, functions

A

Serverless

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q
  • AWS Lambda
  • DynamoDB
  • AWS Cognito
  • AWS API Gateway
  • Amazon S3
  • AWS SNS & SQS
  • AWS Kinesis Data Firehose
  • Aurora Serverless
  • Step Functions
  • Fargate
A

All serverless services

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

Virtual functions limited by time tthat run on-demand

A

Lambda

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

First 1,000,000 requests are free, $0.20 per 1 million requests thereafter

A

Lambda

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

Max execution time of a lambda function

A

15 minutes

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

A code that you write and attach to CloudFront distributions that runs close to your users to minimize latency

A

Edge Function

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

Lightweight functions written in JavaScript for high-scale, latency-sensitive CDN customizations that allow millions of requests/second with Sub-ms startup times

A

CloudFront Functions

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

functions written in NodeJS or Python that scales to 1000s of requests/second

A

Lambda@Edge

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

Does Lambda@Edge trigger from Origin Request/Response

A

Yes

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

CloudFront Functions vs. Lambda@Edge

  • Cache key normalization
    • Transform request attributes (headers,
      cookies, query strings, URL) to create an optimal Cache Key
  • Header manipulation
    • Insert/modify/delete HTTP headers in the request or response
  • URL rewrites or redirects
  • Request authentication & authorization
    • Create and validate user-generated tokens (e.g., JWT) to allow/deny requests
A

CloudFront Functions

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

CloudFront Functions vs. Lambda@Edge

  • Longer execution time (several ms)
  • Adjustable CPU or memory
  • Your code depends on a 3rd libraries (e.g., AWS SDK to access other AWS services)
  • Network access to use external services for processing
  • File system access or access to the body of HTTP requests
A

Lambda@Edge

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

By default, is your Lambda function
launched inside your own VPC?

A

No

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

Lambda must be configured to launch in the VPC by defining the VPC ID, the Subnets and the Security Groups

A

True

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

Lambda will create an ENI (Elastic Network Interface) in your subnets to be launched in your VPC

A

True

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

IImproves Lambda functions directly accessing your DB by by pooling and sharing DB
connections

A

RDS Proxy

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

If using Lambda with RDS proxy it must be deployed in your VPC

A

True

17
Q

Allows you to process data events from within a RDS for PostgreSQL and Aurora MySQL DB by allowing outbound traffic, and required permissions

A

Lambda

18
Q

Notifications that tells information about the DB
instance itself (created, stopped, start, …)

A

RDS Event Notifications

19
Q

NoSQL fully managed Database-as-a-Service (DBaaS) product available within AWS. It is highly resilient across multiple AZ in a region or globally

A

DynamoDB

20
Q

The capacity mode used with an unknown, unpredictable load or low admin overhead on a DynamoDB table

A

On-Demand

21
Q

The capacity mode in DynamoDB where the RCU and WCU are set on a per-table basis

A

Provisioned mode

22
Q

Most flexible way to get data from a DynamoDB table but the least efficient by moving through the table and consuming the capacity of every item

A

Scan

23
Q

Reading DynamoDB data which is directed at a random node across the AZs. Possible to return with stale data if a node is checked before replication completes

A

Eventually Consistent reads

24
Q

Reading DynamoDB data that is directly connected to the leader node which always returns the most up-to-date copy of data

A

Strongly Consistent reads

25
Q

in-memory cache designed specifically for DynamoDB designed for fast response times for accessing Eventually Consistent Data. There is a primary Node which writes and replica nodes that read spread across AZs

A

DynamoDB Accelerator (DAX)

26
Q

Provides multi-master global replication of DynamoDB tables which can be used for performance, HA or DR/BC reasons. Tables are replication in multiple regions and added to a single table

A

DynamoDB Global Tables

27
Q

A continuous stream of backups of a DynamoDB Table over 35 days that needs to be enabled on a per-table basis

A

Point-In-Time Recovery

28
Q

fully managed service with support for the WebSocket Protocol that makes it easy for developers to create, publish, maintain, monitor, and secure APIs at any scale

A

Amazon API Gateway