Latihan AWS Solutions Architect Professional

AWS Organizations lets you manage accounts, policies, and consolidated billing centrally. Databases, DNS, and CDNs are different.

SCPs define guardrails that cap what principals in member accounts can do. S3 policies, routes, and backups are different.

Control Tower automates landing zone setup with guardrails and account factory. Load balancers, databases, and VPNs are different.

AWS RAM shares resources such as subnets and licenses across accounts. Firewalls, DNS, and storage classes are different.

Config aggregators consolidate configuration and compliance data from many accounts and Regions. Databases, load balancers, and backups are different.

Resource groups collect resources with shared tags for management and automation. Security groups, subnets, and DNS zones are different.

Service Catalog lets administrators publish approved products for users to launch. Code repos, firewalls, and CDNs are different.

Cross-account roles let principals in one account assume permissions in another. Buckets, VPCs, and databases are not roles.

StackSets deploy the same CloudFormation template to multiple accounts and Regions. Backups, DNS, and load balancers are different.

Organizations govern accounts, SCPs set permission guardrails, Control Tower builds landing zones, and RAM shares resources.

KMS creates and controls encryption keys used across AWS services. Databases, firewalls, and load balancers are different.

Secrets Manager stores credentials and can rotate them automatically. DNS, CDN, and build tools are different.

GuardDuty analyzes VPC, DNS, and CloudTrail data for threats. Backups, databases, and load balancers are different.

Security Hub centralizes findings from GuardDuty, Inspector, Config, and partners. Repositories, DNS zones, and firewalls are different.

Inspector scans workloads for software vulnerabilities and exposure. CDNs, databases, and VPNs are different.

WAF filters HTTP and HTTPS requests with rules. DNS, databases, and backups are different.

Shield Advanced protects applications from sophisticated DDoS attacks. Firewall rules, DNS zones, and load balancers are different.

Roles provide temporary credentials and permissions to trusted principals. Database users, subnets, and DNS records are different.

Artifact provides compliance reports, certifications, and agreements. Registries, builds, and firewalls are different.

KMS manages keys, Secrets Manager rotates secrets, GuardDuty detects threats, and Security Hub aggregates findings.

Cost Explorer provides charts and reports for AWS spending. Databases, load balancers, and DNS are different.

Budgets track cost and usage against thresholds and notify when limits are crossed. Invoices, security groups, and storage classes are different.

Savings Plans offer lower rates in exchange for a commitment to consistent usage. Engines, VPNs, and CDNs are different.

RIs reserve capacity and reduce costs for predictable workloads. Backups, DNS records, and firewalls are different.

Spot Instances provide large discounts for interruptible workloads using spare capacity. Dedicated hosts, databases, and load balancers are different.

Lifecycle policies move objects between storage classes or delete them based on rules. Encryption, users, and routing are different.

Compute Optimizer analyzes usage and recommends instance and resource sizes. Databases, VPNs, and CDNs are different.

Pricing Calculator estimates monthly costs for planned workloads. Reports, firewalls, and DNS are different.

Consolidated billing aggregates usage so volume discounts apply across accounts. Separate payments, deletion, and budgets are different.

Cost Explorer analyzes spend, Budgets alerts on thresholds, Savings Plans commit usage, and Compute Optimizer advises sizing.

Application Migration Service (MGN) automates server migration to AWS. Engines, DNS, and CDNs are different.

DMS moves data between source and target databases with minimal downtime. Warehouses, caches, and backups are different.

SCT converts schemas between database engines to support heterogeneous migrations. Transfers, DNS, and firewalls are different.

DataSync automates and accelerates data transfers to and from AWS storage. Databases, CDNs, and VPNs are different.

Snowball devices move large data sets physically when networks are impractical. VMs, databases, and DNS records are different.

Migration Hub provides a central view of migration progress. Warehouses, load balancers, and backups are different.

Transfer Family provides managed file transfer protocols to Amazon S3 and EFS. Database tools, DNS, and CDNs are different.

Heterogeneous migrations change the database engine and typically use SCT. Same-engine, physical, and DNS changes are different.

Cutover redirects users and workloads to the migrated environment. Backups, scans, and queries are not cutover.

MGN migrates servers, DMS migrates databases, SCT converts schemas, and Snowball transfers data physically.

Multi-AZ deployments tolerate Availability Zone failures. Single-zone, no backup, and log deletion reduce resilience.

RDS Multi-AZ maintains a synchronous standby for automatic failover. Read replicas scale reads, snapshots back up, and caches speed reads.

Failover routing uses health checks to switch traffic when the primary endpoint fails. Latency, weighted, and geolocation are different policies.

AWS Backup centralizes backup policies and monitoring for supported services. Databases, DNS, and firewalls are different.

RTO measures acceptable downtime and RPO measures acceptable data loss. Indexes, routes, and security rules are different.

Cross-region replication protects data by copying it to another Region. Same-region copies, deletion, and users do not provide regional DR.

Elastic Disaster Recovery continuously replicates servers for fast failover. Backup vaults, DNS zones, and CDNs are different.

Global Accelerator uses health checks and static anycast IPs to shift traffic from unhealthy endpoints. Storage, DNS-only, and filtering are different.

Health checks validate endpoint availability for routing and scaling decisions. Backups, firewall rules, and storage classes are different.

Multi-AZ provides zone resilience, RDS Multi-AZ handles database failover, Route 53 failover handles DNS, and AWS Backup centralizes backups.

Auto Scaling groups maintain desired capacity and scale with demand. DNS records, databases, and firewalls are different.

ALB routes HTTP and HTTPS traffic with path and host rules at layer 7. NLB is layer 4, and DNS or databases are different.

NLB handles TCP and UDP traffic at layer 4 with high throughput. WAF, DNS zones, and caches are different.

CloudFront caches content at edge locations for lower latency. Databases, VPNs, and firewalls are different.

ElastiCache provides Redis and Memcached caching. Relational databases, warehouses, and DNS are different.

DAX speeds DynamoDB reads with an in-memory cache. Databases, backups, and firewalls are different.

On-demand mode adjusts read and write capacity instantly. Fixed capacity, relational databases, and caches are different.

SQS decouples producers and consumers with durable queues. File storage, DNS, and filtering are different.

Lambda runs code without provisioning servers and scales with events. VMs, databases, and CDNs are different.

Auto Scaling adjusts instances, ALB routes HTTP, CloudFront caches at the edge, and SQS decouples messages.