π§± Prerequisites: Before You Start Your AWS Journey#
This chapter covers everything you need to know before diving into AWS. If you’re from a non-technical background or need a refresher on networking, computing, and IT fundamentals β start here. These concepts are essential for understanding AWS services and for the SAA-C03 exam.
π― Learning Objectives#
- Understand IP addressing, CIDR notation, and subnetting
- Learn the OSI model and common network protocols
- Grasp virtualization concepts β the foundation of cloud computing
- Distinguish between block, file, and object storage
- Understand relational vs NoSQL databases
- Learn security fundamentals (encryption, hashing, certificates)
- Differentiate cloud service models (IaaS, PaaS, SaaS)
1. Networking Fundamentals#
1.1 IP Addressing#
Every device on a network needs an IP address β like a home address for your computer.
IPv4 (most common): 192.168.1.1 β 4 numbers, each 0β255, separated by dots
IPv6 (newer, larger): 2001:0db8:85a3:0000:0000:8a2e:0370:7334 β hexadecimal, 8 groups
Public vs Private IPs:
- Public IP: Reachable from the internet (e.g., your home router’s WAN IP)
- Private IP: Only accessible within a private network. RFC 1918 defines these ranges:
10.0.0.0/8(big networks β AWS uses this for VPCs)172.16.0.0/12(medium networks)192.168.0.0/16(small networks β your home WiFi)
π Exam Tip: AWS VPCs always use private IPs from RFC 1918. If you see
10.0.0.0/16in a question, that’s a VPC CIDR.
1.2 CIDR Notation Explained#
CIDR (Classless Inter-Domain Routing) tells you how many IP addresses a network has.
10.0.0.0/16 β The /16 means "first 16 bits are fixed"
Remaining 16 bits = 2^16 = 65,536 IPs| CIDR | Subnet Mask | IPs Available | Analogy |
|---|---|---|---|
/8 |
255.0.0.0 | 16,777,214 | A country |
/16 |
255.255.0.0 | 65,534 | A large city |
/24 |
255.255.255.0 | 254 | A street |
/28 |
255.255.255.240 | 14 | A few houses |
/32 |
255.255.255.255 | 1 | A single house |
Quick formula: Available IPs = 2^(32 - prefix) - 2
Why subtract 2? The first IP is the network address and the last is the broadcast address β they can’t be assigned to devices.
π Exam Tip: You’ll need to calculate subnet sizes for VPC exam questions. Know that
/16= 65,536,/24= 256,/28= 16 IPs.
1.3 Subnetting#
Subnetting means dividing a large network into smaller ones. AWS does this when you create subnets inside a VPC.
Example: You have 10.0.0.0/16 (65,536 IPs). You want 4 subnets:
- Subnet 1:
10.0.0.0/18β 16,384 IPs (10.0.0.0 β 10.0.63.255) - Subnet 2:
10.0.64.0/18β 16,384 IPs (10.0.64.0 β 10.0.127.255) - Subnet 3:
10.0.128.0/18β 16,384 IPs - Subnet 4:
10.0.192.0/18β 16,384 IPs
1.4 The OSI Model#
The OSI model is a layered framework for understanding network communication. Think of it like sending a package:
| Layer | Name | What Happens | Example |
|---|---|---|---|
| 7 | Application | The actual data you send/receive | HTTP, HTTPS, FTP, SMTP |
| 6 | Presentation | Encoding, encryption, compression | SSL/TLS, JPEG, GIF |
| 5 | Session | Managing the conversation | NetBIOS, RPC |
| 4 | Transport | Reliable delivery (TCP) or fast/no-guarantee (UDP) | TCP, UDP |
| 3 | Network | Routing between networks | IP, routing protocols |
| 2 | Data Link | Communication within a local network | Ethernet, MAC addresses |
| 1 | Physical | Cables, radio signals, fiber optics | Ethernet cable, WiFi |
π Exam Tip: For SAA, focus on Layer 3 (IP), Layer 4 (TCP/UDP), and Layer 7 (HTTP/HTTPS). Security Groups are stateful (Layer 3-4), NACLs are stateless (Layer 3-4).
1.5 TCP vs UDP β The Key Difference#
| Feature | TCP | UDP |
|---|---|---|
| Connection | Connection-oriented (handshake first) | Connectionless (just send) |
| Reliability | Guaranteed delivery with retransmission | No guarantee β fire and forget |
| Ordering | Packets arrive in order | Packets may arrive out of order |
| Speed | Slower (overhead for reliability) | Faster (no overhead) |
| Use Cases | Web browsing (HTTP), email (SMTP), file transfer (FTP) | Video streaming, VoIP, DNS, gaming |
The TCP 3-Way Handshake: SYN β SYN-ACK β ACK (this is how connections are established)
sequenceDiagram
participant Client
participant Server
Note over Client,Server: Step 1 - Connection Establishment
Client->>Server: SYN (Synchronize) - Hi, can we talk?
Server->>Client: SYN-ACK (Synchronize-Acknowledge) - Sure, I'm ready!
Client->>Server: ACK (Acknowledge) - Great, let's start!
Note over Client,Server: Connection Established β
Client->>Server: HTTP GET /index.html (Data Transfer)
Server->>Client: HTTP 200 OK + HTML Response
Note over Client,Server: Step 3 - Connection Teardown
Client->>Server: FIN (Finish)
Server->>Client: ACK
Server->>Client: FIN
Client->>Server: ACKWhy TCP matters for AWS: ALB operates at Layer 7 (HTTP/HTTPS) and uses TCP as its underlying transport. NLB operates at Layer 4 (TCP/UDP) and preserves the client IP. Understanding TCP helps you debug connectivity issues with Security Groups, NACLs, and load balancers.
π Exam Tip: ALB operates at Layer 7 (HTTP), NLB at Layer 4 (TCP/UDP). If you need ultra-low latency or static IPs, pick NLB.
1.6 Common Network Ports (Memorize These!)#
| Port | Protocol | Service | Why You Need It |
|---|---|---|---|
| 22 | TCP | SSH | Connect to EC2 Linux instances |
| 80 | TCP | HTTP | Web traffic (unencrypted) |
| 443 | TCP | HTTPS | Web traffic (encrypted) |
| 3389 | TCP | RDP | Connect to EC2 Windows instances |
| 3306 | TCP | MySQL | RDS MySQL/MariaDB connections |
| 5432 | TCP | PostgreSQL | RDS PostgreSQL connections |
| 6379 | TCP | Redis | ElastiCache Redis connections |
| 11211 | TCP | Memcached | ElastiCache Memcached connections |
| 27017 | TCP | MongoDB | DocumentDB connections |
| 5439 | TCP | Redshift | Redshift connections |
| 2049 | TCP | NFS | EFS connections |
1.7 DNS β The Internet’s Phonebook#
DNS (Domain Name System) translates human-readable domain names (like aws.amazon.com) into IP addresses.
DNS resolution flow:
- You type
aws.amazon.comin your browser - Your computer asks the DNS resolver (e.g., 8.8.8.8 β Google DNS)
- The resolver asks the root DNS server β TLD server (.com) β authoritative server (amazon.com)
- The authoritative server returns the IP:
176.32.103.205 - Your browser connects to that IP
Common DNS record types:
| Record | Purpose | Example |
|---|---|---|
| A | Maps domain to IPv4 address | example.com β 192.0.2.1 |
| AAAA | Maps domain to IPv6 address | example.com β 2001:db8::1 |
| CNAME | Maps domain to another domain (alias) | www.example.com β example.com |
| MX | Mail server records | Directs email to mail servers |
| NS | Name servers for the domain | Tells who holds the DNS records |
| TXT | Arbitrary text (verification, SPF) | Domain ownership verification |
π Exam Tip: In Route53, Alias records (free) can map to AWS resources (ALB, CloudFront). CNAME records cannot point to root domains (e.g., you can’t CNAME
example.com). This is a common exam question!
1.8 HTTP/HTTPS#
HTTP (Hypertext Transfer Protocol) is how web browsers and servers communicate.
HTTP Request Methods:
GETβ Retrieve data (read-only)POSTβ Create new dataPUTβ Update/replace dataPATCHβ Partial updateDELETEβ Remove data
HTTP Status Codes (Memorize These):
| Code | Meaning | Example Scenario |
|---|---|---|
| 200 | OK | Request succeeded |
| 201 | Created | New resource created (POST) |
| 301 | Moved Permanently | Redirect to new URL |
| 400 | Bad Request | Client sent invalid data |
| 401 | Unauthorized | Need to log in |
| 403 | Forbidden | Authenticated but no permission |
| 404 | Not Found | Resource doesn’t exist |
| 500 | Internal Server Error | Server-side error |
| 502 | Bad Gateway | Upstream server failed |
| 503 | Service Unavailable | Server overloaded or down |
1.9 Firewalls β Stateful vs Stateless#
A firewall controls what traffic is allowed in/out of a network.
graph LR
SG[Security Group - Stateful] --> IN[Allow TCP 22 Inbound]
SG --> OUT[Auto Allow Return Traffic]
NACL[NACL - Stateless] --> IN2[Allow TCP 22 Inbound]
NACL --> OUT2[Explicitly Allow Ephemeral Ports Outbound]| Feature | Stateful | Stateless |
|---|---|---|
| Remembers connections | β Yes β auto-allows return traffic | β No β must explicitly allow both directions |
| Performance | Slightly slower (tracks state) | Faster (simple rule lookup) |
| Configuration | Easier (fewer rules needed) | Harder (need inbound + outbound rules) |
| AWS Example | Security Groups | Network ACLs (NACLs) |
π Exam Tip: If you see “return traffic is automatically allowed” β Security Group. If you see “must explicitly allow inbound and outbound” β NACL. This is guaranteed to appear on the exam!
2. Operating Systems & Compute Concepts#
2.1 Linux Basics for AWS#
Most AWS services run on Linux. You’ll need to know these basics:
File System Hierarchy:
| Directory | Purpose |
|---|---|
/ |
Root directory |
/etc |
Configuration files |
/var |
Variable data (logs: /var/log) |
/home |
User home directories |
/tmp |
Temporary files |
/opt |
Optional software |
/usr |
User programs |
Essential Commands:
# File operations
ls -la # List files with details
cd /path # Change directory
pwd # Print working directory
cp source dest # Copy file
mv source dest # Move/rename file
rm file # Remove file
mkdir dir # Create directory
chmod 755 file # Change permissions
chown user:group # Change owner
# Viewing files
cat file # Print file content
less file # View file with scroll
tail -f file # Follow file (logs)
head -n 10 file # First 10 lines
grep "pattern" # Search for text
# Process management
ps aux # List running processes
top # Interactive process viewer
kill PID # Kill process
kill -9 PID # Force kill
# Networking
netstat -an # Show network connections
curl http://url # Make HTTP request
ping host # Test connectivity
ssh user@host # Connect to remote server2.2 SSH β Secure Shell#
SSH lets you securely connect to a remote Linux machine (like EC2) using key pairs:
How SSH key pairs work:
- Private key (
mykey.pem) β Keep secret, never share - Public key (
mykey.pub) β Put on the server (~/.ssh/authorized_keys)
# Generate key pair
ssh-keygen -t rsa -b 2048 -f mykey
# Connect to EC2
ssh -i mykey.pem ec2-user@54.123.45.67
# Permissions matter! (SSH refuses too-open permissions)
chmod 400 mykey.pem2.3 Virtualization Concepts (Critical for AWS!)#
Virtualization is the technology that makes cloud computing possible. A single physical server runs multiple Virtual Machines (VMs), each thinking it has its own hardware.
Hypervisor Types:
| Type | Description | Example |
|---|---|---|
| Type 1 (Bare Metal) | Runs directly on hardware, no host OS | AWS Nitro, VMware ESXi, Microsoft Hyper-V |
| Type 2 (Hosted) | Runs on top of an existing OS | VirtualBox, VMware Workstation |
AWS Nitro System:
- AWS’s custom-built virtualization platform
- Offloads virtualization functions to dedicated hardware (Nitro cards)
- Benefits: Near bare-metal performance, improved security, faster innovation
- Powers all modern EC2 instances
How VMs Work:
ββββββββββββββββββββββββββββββββββββββββββββββββ
β Physical Server (Hardware) β
ββββββββββββββββββββββββββββββββββββββββββββββββ€
β βββββββββββ βββββββββββ βββββββββββ β
β β VM 1 β β VM 2 β β VM 3 β ... β
β β (Web) β β (DB) β β (App) β β
β β Ubuntu β β CentOS β β Windows β β
β βββββββββββ€ βββββββββββ€ βββββββββββ€ β
β β Nitro Hypervisor (AWS) β
β ββββββββββββββββββββββββββββββββββββββββββββContainers vs VMs:
| Feature | VM | Container |
|---|---|---|
| OS | Full OS per VM | Shares host OS kernel |
| Startup | Minutes | Seconds |
| Size | GBs | MBs |
| Isolation | Strong (hardware-level) | Process-level (namespaces) |
| Resource usage | Heavy (duplicate OS overhead) | Lightweight |
| AWS Services | EC2 (VMs) | ECS, EKS, Fargate (containers) |
π Exam Tip: If you need strong isolation (multi-tenant, compliance), use VMs/EC2. If you want fast startup and efficiency, use containers (ECS/Fargate). Lambda is “serverless” β no VMs or containers to manage.
3. Storage Concepts#
3.1 Block vs File vs Object Storage#
This is critical for AWS β all storage services fall into one of these categories:
| Feature | Block Storage | File Storage | Object Storage |
|---|---|---|---|
| How it works | Raw disk volume, formatted with filesystem | Shared filesystem accessed over network | Flat namespace, HTTP-accessible |
| Access | Via OS (mount as drive) | Via network (NFS, SMB) | Via API/HTTP (REST) |
| Modify | Can modify small parts of a file | Can modify small parts | Must replace entire object |
| Performance | Fastest (low latency) | Moderate (network overhead) | Moderate |
| Use cases | OS disk, databases, high-performance apps | Shared files, home directories | Static files, backups, logs, media |
| AWS Example | EBS (Elastic Block Store) | EFS (Elastic File System) | S3 (Simple Storage Service) |
Simple Analogy:
- Block = A notebook with pages you can write on any page
- File = A shared whiteboard everyone can see and edit
- Object = A photo album where you add/remove entire photos
3.2 IOPS vs Throughput vs Latency#
| Term | What It Measures | Analogy |
|---|---|---|
| IOPS | Input/Output Operations Per Second β number of read/write operations | How many times can you open/close a drawer per second |
| Throughput | Data transferred per second (MB/s or GB/s) | How much water flows through a pipe per second |
| Latency | Time for a single operation (ms) | How long it takes to open a drawer |
Relationship: Throughput = IOPS Γ I/O size
π Exam Tip: For databases β high IOPS. For streaming/large files β high throughput.
4. Database Fundamentals#
4.1 Relational Databases (SQL)#
Data organized in tables with rows and columns. Think of a spreadsheet.
Key concepts:
- Table: Collection of related data (e.g.,
Customers) - Row/Record: A single entry (e.g., one customer)
- Column/Field: A single attribute (e.g.,
Name,Email) - Primary Key: Uniquely identifies each row
- Foreign Key: References a primary key in another table
- Index: Speeds up searches (like a book’s index)
- SQL: Language to query data (
SELECT * FROM Customers WHERE City = 'New York')
ACID Properties:
| Property | What It Means |
|---|---|
| Atomicity | All or nothing β transaction completes fully or not at all |
| Consistency | Data follows all rules/constraints after transaction |
| Isolation | Concurrent transactions don’t interfere with each other |
| Durability | Once committed, data survives crashes/power loss |
AWS Services: Amazon RDS (MySQL, PostgreSQL, Oracle, SQL Server, MariaDB), Amazon Aurora
4.2 NoSQL Databases#
Non-relational databases designed for scale, flexibility, and performance at the cost of some consistency guarantees.
Types of NoSQL databases:
| Type | Description | Example | AWS Service |
|---|---|---|---|
| Key-Value | Simple key β value store | Redis, DynamoDB | DynamoDB |
| Document | JSON-like documents | MongoDB | DocumentDB |
| Wide-Column | Rows with flexible columns | Cassandra | Keyspaces |
| Graph | Relationships between entities | Neo4j | Neptune |
BASE Model (opposite of ACID):
- Basically Available β system is always accepting data
- Soft state β data might change over time
- Eventual consistency β data will be consistent eventually (not immediately)
π Exam Tip: If the question mentions “high traffic, low latency, serverless, flexible schema” β DynamoDB. If it mentions “complex queries, joins, transactions” β RDS/Aurora.
5. Security Foundations#
5.1 Encryption: Symmetric vs Asymmetric#
| Feature | Symmetric | Asymmetric |
|---|---|---|
| Keys | Same key encrypts and decrypts | Public key encrypts, private key decrypts |
| Speed | Fast | Slow |
| Key management | Hard (must share key securely) | Easier (public key is… public) |
| Use cases | Data at rest encryption, bulk encryption | SSL/TLS, digital signatures, key exchange |
| Algorithm example | AES-256 | RSA, ECDSA |
AES-256: The standard for encrypting data at rest in AWS (S3, EBS, RDS all use it).
5.2 TLS/SSL β How HTTPS Works#
TLS (Transport Layer Security) is what makes HTTPS secure. Here’s how it works:
1. Client connects to server (e.g., https://aws.amazon.com)
2. Server sends its SSL certificate (includes public key)
3. Client verifies the certificate against a trusted CA (Certificate Authority)
4. Client generates a symmetric session key
5. Client encrypts the session key with the server's public key
6. Server decrypts with its private key
7. Now both sides have the same symmetric key β secure communication
Result: π Encrypted tunnel for the rest of the sessionKey terms:
- Certificate Authority (CA): Trusted organization that issues certificates (Amazon Trust Services, DigiCert, Let’s Encrypt)
- ACM: AWS Certificate Manager β free SSL/TLS certificates for AWS services
5.3 Hashing vs Encryption#
| Feature | Hashing | Encryption |
|---|---|---|
| Reversible? | β No (one-way) | β Yes (requires key) |
| Purpose | Integrity verification, password storage | Confidentiality |
| Output length | Fixed length (SHA-256 = 256 bits) | Variable (same length as input) |
| Algorithm | SHA-256, SHA-512, MD5 (insecure) | AES-256, RSA |
| AWS Example | S3 checksums | S3 SSE-S3/SSE-KMS |
π Exam Tip: Passwords should be hashed (never encrypted). Data should be encrypted for confidentiality. CloudTrail logs use hashing for integrity.
6. Cloud Computing Concepts#
6.1 IaaS vs PaaS vs SaaS#
| Model | What You Manage | What Provider Manages | AWS Example |
|---|---|---|---|
| IaaS | Apps, data, OS, middleware, runtime | Virtualization, servers, storage, networking | EC2 (you manage OS and above) |
| PaaS | Apps, data | Everything below (OS, middleware, runtime, infrastructure) | RDS (you manage data only) |
| SaaS | Nothing β just use the app | Everything | WorkMail, Chime |
Analogy: Pizza as a Service π
- On-prem: You make everything (dough, sauce, toppings, bake)
- IaaS: Buy pre-made dough (EC2 + your OS + your app)
- PaaS: Buy a frozen pizza (RDS β just add your data)
- SaaS: Order delivery (use the app)
6.2 Public vs Private vs Hybrid Cloud#
| Public Cloud | Private Cloud | Hybrid Cloud | |
|---|---|---|---|
| Who owns | Cloud provider (AWS) | Your organization | Both |
| Where | Provider’s data centers | Your data center | Both connected |
| Access | Anyone (multi-tenant) | Your organization only | Selected workloads in each |
| Example | AWS, Azure, GCP | VMware on-premises | AWS + Direct Connect to on-prem |
6.3 HA, Fault Tolerance, Scalability, Elasticity#
| Concept | Definition | Analogy |
|---|---|---|
| High Availability | System stays up despite component failures (measured in “9s”) | A building with backup power generator |
| Fault Tolerance | System continues operating even when components fail completely | An airplane can fly with one engine |
| Scalability | Ability to handle increased load | A restaurant adding more tables |
| Elasticity | Auto-scaling up AND down based on demand | A restaurant that expands and contracts |
| Vertical Scaling | Make one server bigger (more CPU/RAM) | Upgrade from motorcycle to truck |
| Horizontal Scaling | Add more servers | Add more trucks to the fleet |
Availability “9s”:
- 99% (“two 9s”) = ~3.65 days downtime/year
- 99.9% (“three 9s”) = ~8.76 hours downtime/year
- 99.99% (“four 9s”) = ~52.56 minutes downtime/year
- 99.999% (“five 9s”) = ~5.26 minutes downtime/year
6.4 Disaster Recovery: RTO and RPO#
| Term | Full Name | What It Means |
|---|---|---|
| RTO | Recovery Time Objective | Maximum acceptable downtime (how long can we be down?) |
| RPO | Recovery Point Objective | Maximum acceptable data loss (how much data can we lose?) |
Example: RTO = 1 hour, RPO = 15 minutes
- If disaster strikes at 2:00 PM, you must be back online by 3:00 PM
- You can lose at most 15 minutes of data (last backup at 1:45 PM)
The Relationship: Lower RTO/RPO = More cost and complexity
6.5 CAPEX vs OPEX#
| CAPEX | OPEX | |
|---|---|---|
| Full Name | Capital Expenditure | Operational Expenditure |
| What it is | Buy upfront (servers, data centers) | Pay as you go (cloud services) |
| Cash flow | Large upfront cost | Small recurring payments |
| Flexibility | Locked into capacity decisions | Scale up/down as needed |
| Cloud corollary | Reserved Instances (partial) | On-Demand instances |
π Exam Tip: Cloud computing = OPEX model. No upfront hardware costs. This is a fundamental advantage of cloud.
β Chapter Quiz#
-
A solutions architect needs to design a VPC with a CIDR of 10.0.0.0/16 and create 8 equal-sized subnets. What is the subnet mask and how many usable IP addresses does each subnet provide?
- A) /19 β 8,190 usable IPs
- B) /20 β 4,094 usable IPs
- C) /24 β 254 usable IPs
- D) /18 β 16,382 usable IPs
-
Which AWS firewall is STATEFUL and automatically allows return traffic?
- A) Network ACL (NACL)
- B) Security Group
- C) AWS WAF
- D) AWS Shield
-
A company is migrating a production database to EC2 and is concerned about performance interference from other tenants. Which EC2 tenancy option provides dedicated physical server isolation?
- A) Shared tenancy
- B) Dedicated Instance
- C) Dedicated Host
- D) Spot Instance
-
Which storage type is best for a shared filesystem that multiple EC2 instances need to access simultaneously?
- A) S3 (object storage)
- B) EBS (block storage)
- C) EFS (file storage)
- D) Instance Store
-
In the shared responsibility model, what does AWS secure?
- A) Customer applications
- B) Customer data
- C) Security OF the cloud (physical infrastructure, hypervisor)
- D) Customer IAM policies
-
Which database type uses ACID transactions and is best for complex queries with joins?
- A) DynamoDB
- B) Amazon RDS (relational)
- C) ElastiCache
- D) S3
-
A security auditor requires all traffic between an ALB and EC2 web servers to be encrypted. Which protocol and port combination should the security group allow from the ALB to the instances?
- A) TCP 80
- B) TCP 443
- C) TCP 22
- D) TCP 3389
-
A company needs to encrypt data at rest in S3. Compliance requires them to manage their own keys with annual rotation. Which S3 encryption option should be used?
- A) SSE-S3
- B) SSE-KMS with customer managed key
- C) SSE-C
- D) Client-side encryption
-
A company needs RTO of 15 minutes and RPO of 5 minutes. Which DR strategy is most appropriate?
- A) Backup & Restore
- B) Pilot Light
- C) Warm Standby
- D) Multi-Site Active-Active
-
Which AWS service provides VIRTUAL MACHINES in the cloud?
- A) AWS Lambda
- B) Amazon EC2
- C) Amazon ECS
- D) AWS Fargate
-
A company wants to use 10.0.0.0/22 as their VPC CIDR. How many usable IP addresses does this provide?
- A) 1022
- B) 1024
- C) 4094
- D) 4096
-
An application requires the lowest possible network latency between multiple EC2 instances. Which placement group strategy should be used?
- A) Spread
- B) Partition
- C) Cluster
- D) Distributed
-
Which S3 encryption option allows the customer to provide their own encryption keys?
- A) SSE-S3
- B) SSE-KMS
- C) SSE-C
- D) Client-side encryption
-
Which of the following is a characteristic of Amazon RDS over DynamoDB? (Select TWO)
- A) Supports complex JOIN queries
- B) Provides ACID transactions across multiple tables
- C) Scales serverless to zero
- D) Handles millions of requests per second
- E) Stores unstructured JSON documents
-
What is the key difference between a Security Group and a Network ACL?
- A) Security Groups are stateless; NACLs are stateful
- B) Security Groups are stateful; NACLs are stateless
- C) Both are stateful
- D) Both are stateless
-
A company uses an Auto Scaling group across three Availability Zones. The minimum instance count is 3. If one AZ becomes unavailable, how many instances will remain healthy?
- A) 1
- B) 2
- C) 3
- D) 0
-
An organization needs an RTO of less than 15 minutes and an RPO of less than 1 minute. Which DR strategy is most appropriate?
- A) Backup & Restore
- B) Pilot Light
- C) Warm Standby
- D) Multi-Site Active-Active
-
Which OSI layer is responsible for routing packets between different networks?
- A) Layer 2 β Data Link
- B) Layer 3 β Network
- C) Layer 4 β Transport
- D) Layer 7 β Application
-
An EC2 instance needs to access an S3 bucket without storing long-term credentials on the instance. What is the BEST approach?
- A) Store IAM access keys in a config file
- B) Attach an IAM Role to the EC2 instance profile
- C) Use an S3 bucket policy that allows public access
- D) Hardcode credentials in the application code
-
Which is an advantage of horizontal scaling over vertical scaling?
- A) Simpler application architecture
- B) No theoretical limit to scaling capacity
- C) Lower per-instance licensing costs
- D) Easier to implement for stateful workloads
-
Which cloud model connects on-premises infrastructure to a public cloud provider via dedicated private networking?
- A) Public Cloud
- B) Private Cloud
- C) Hybrid Cloud
- D) Community Cloud
-
A company wants no upfront costs and the flexibility to stop using resources at any time. Which AWS pricing model should they choose?
- A) Reserved Instances
- B) Savings Plans
- C) On-Demand
- D) Spot Instances
-
Which statement accurately describes hashing compared to encryption?
- A) Hashing is reversible; encryption is one-way
- B) Encryption is reversible with a key; hashing is one-way
- C) Both are reversible with the correct key
- D) Both are one-way functions
-
A solutions architect needs block storage with the highest possible IOPS for a latency-sensitive database. Which option is BEST?
- A) S3 Standard
- B) EBS io2 Block Express
- C) EFS General Purpose
- D) S3 Glacier Deep Archive
-
In the shared responsibility model, which of the following is the customer’s responsibility?
- A) Physical security of AWS data centers
- B) Patching the EC2 instance operating system
- C) Network cable maintenance
- D) Hypervisor security
π Answers
- B β /16 with 8 subnets = /19 per subnet (16+3=19). 2^(32-19)=8192 total, minus 2 reserved = 8190 usable.
- b β Security Groups are stateful; NACLs are stateless
- C β Dedicated Host provides physical server isolation for licensing and compliance requirements.
- c β EFS provides shared file storage accessible by multiple EC2 instances simultaneously
- c β AWS secures “Security OF the Cloud” (physical, hypervisor, network)
- b β RDS uses ACID and supports joins/complex queries
- B β HTTPS uses TCP port 443 for encrypted traffic between ALB and instances.
- B β SSE-KMS with customer managed key provides encryption with customer-controlled keys and automatic annual rotation.
- d β Multi-Site Active-Active provides the lowest RTO/RPO
- b β EC2 provides virtual machines (instances)
- a β /22 = 2^10 = 1024 total IPs, minus 2 (network + broadcast) = 1022 usable
- c β Cluster placement groups provide lowest latency and maximum throughput within a single AZ
- c β SSE-C (Server-Side Encryption with Customer-Provided Keys) lets customers supply their own keys
- a, b β RDS supports complex joins and ACID transactions across tables; DynamoDB is better for serverless and high throughput
- b β Security Groups are stateful (return traffic auto-allowed); NACLs are stateless
- B β With 3 instances across 3 AZs (1 per AZ), losing one AZ leaves 2 instances healthy.
- d β Multi-Site Active-Active provides the lowest RTO and RPO values
- b β Layer 3 (Network) handles routing using IP addresses
- b β IAM Roles for EC2 (instance profiles) provide temporary credentials via the metadata service
- b β Horizontal scaling has no theoretical limit; vertical scaling caps at the largest available instance size
- c β Hybrid Cloud connects on-premises to public cloud (e.g., AWS Direct Connect or VPN)
- c β On-Demand is pay-as-you-go with no upfront commitment
- b β Encryption is reversible with a key; hashing is a one-way function for integrity verification
- b β EBS io2 Block Express delivers up to 256K IOPS for high-performance database workloads
- b β Customers are responsible for security IN the cloud, including guest OS patching
π Additional Resources#
- AWS Cloud Practitioner Essentials
- Subnet Calculator β practice CIDR calculations
- Linux Journey β free Linux basics course
- Networking Basics (Cisco)