Global Infrastructure Quiz
Quiz
Question 1 of 39
(0 answered)
Question 1
Why are AWS Regions geographically separated?
Why are AWS Regions geographically separated?
Geographic Separation Provides Three Core Benefits:
- Fault isolation and disaster recovery: A failure in one Region does not affect others — protects against natural disasters, power outages, and infrastructure failures
- Reduced latency: Serving users from a nearby Region minimizes round-trip time and improves application performance
- Data residency and compliance: Enables GDPR and data localization law compliance — AWS never moves data between Regions without explicit customer action
Did you get it right?
✓
Correct!
✗
Incorrect
Question 2
Which factors should you consider when choosing an AWS Region for your application?
✓
Correct!
The five key factors for choosing a Region are: latency/user proximity, data sovereignty/compliance, service availability, cost, and disaster recovery requirements. The number of AZs and proximity to edge locations are not primary Region selection criteria — AZ count matters for architecture design within a chosen Region, and edge locations serve CloudFront content delivery, not core application deployment.
✗
Incorrect
The five key factors for choosing a Region are: latency/user proximity, data sovereignty/compliance, service availability, cost, and disaster recovery requirements. The number of AZs and proximity to edge locations are not primary Region selection criteria — AZ count matters for architecture design within a chosen Region, and edge locations serve CloudFront content delivery, not core application deployment.
The content lists five specific factors to consider when selecting a Region.
Question 3
Availability Zones within a Region are connected via the public internet to ensure maximum accessibility.
✓
Correct!
False. Availability Zones within a Region are connected via low-latency, high-bandwidth, redundant fiber optic networks—not the public internet. This provides single-digit millisecond latency and enables synchronous replication.
✗
Incorrect
False. Availability Zones within a Region are connected via low-latency, high-bandwidth, redundant fiber optic networks—not the public internet. This provides single-digit millisecond latency and enables synchronous replication.
Consider what type of network would provide the best performance and security.
Question 4
Complete the ARN for an EC2 instance in the us-east-1 Region:
Fill in the missing partition identifier
arn:___:ec2:us-east-1:123456789012:instance/i-1234567890abcdef0✓
Correct!
The partition for standard AWS Regions is ‘aws’. Other partitions include ‘aws-cn’ for AWS China Regions and ‘aws-us-gov’ for AWS GovCloud (US) Regions.
✗
Incorrect
The partition for standard AWS Regions is ‘aws’. Other partitions include ‘aws-cn’ for AWS China Regions and ‘aws-us-gov’ for AWS GovCloud (US) Regions.
Question 5
How many data centers does an Availability Zone contain?
✓
Correct!
An Availability Zone consists of one or more discrete data centers within an AWS Region. The minimum is one, but most AZs contain multiple data centers. ‘Two or more’ is a common near-miss — it applies the redundancy-requires-at-least-two logic incorrectly; the actual minimum per the definition is one.
✗
Incorrect
An Availability Zone consists of one or more discrete data centers within an AWS Region. The minimum is one, but most AZs contain multiple data centers. ‘Two or more’ is a common near-miss — it applies the redundancy-requires-at-least-two logic incorrectly; the actual minimum per the definition is one.
The definition mentions ‘one or more’ data centers.
Question 6
What is the typical inter-AZ latency within a Region (in milliseconds)?
✓
Correct!
Typical inter-AZ latency within a Region is single-digit milliseconds. This low latency enables synchronous replication for databases and storage systems.
✗
Incorrect
Typical inter-AZ latency within a Region is single-digit milliseconds. This low latency enables synchronous replication for databases and storage systems.
Think about the order of magnitude—less than 10ms.
Question 7
Which of the following are characteristics of AWS Local Zones?
✓
Correct!
Local Zones are designed for ultra-low (single-digit millisecond) latency, are associated with a parent AWS Region, and connected via AWS’s private network. However, not all services are available in Local Zones (only select compute, storage, and database services), and they are not independent from Regions.
✗
Incorrect
Local Zones are designed for ultra-low (single-digit millisecond) latency, are associated with a parent AWS Region, and connected via AWS’s private network. However, not all services are available in Local Zones (only select compute, storage, and database services), and they are not independent from Regions.
Local Zones extend AWS infrastructure but have limitations compared to full Regions.
Question 8
What does Multi-AZ deployment provide?
What does Multi-AZ deployment provide?
High Availability and Fault Tolerance
Did you get it right?
✓
Correct!
Multi-AZ deployment provides high availability by distributing compute and data across multiple isolated Availability Zones. This enables fault tolerance through redundancy, load balancing, and automatic failover, ensuring the system continues to operate even if an entire AZ goes down.
✗
Incorrect
Multi-AZ deployment provides high availability by distributing compute and data across multiple isolated Availability Zones. This enables fault tolerance through redundancy, load balancing, and automatic failover, ensuring the system continues to operate even if an entire AZ goes down.
Question 9
Arrange these AWS Global Infrastructure components from largest to smallest scope:
Drag to arrange in order from broadest to most specific
⋮⋮
AWS Region
⋮⋮
Availability Zone
⋮⋮
Data Center
⋮⋮
AWS Global Infrastructure
✓
Correct!
The hierarchy is: AWS Global Infrastructure (worldwide) → Region (geographic location) → Availability Zone (isolated location within Region) → Data Center (physical facility).
✗
Incorrect
The hierarchy is: AWS Global Infrastructure (worldwide) → Region (geographic location) → Availability Zone (isolated location within Region) → Data Center (physical facility).
Question 10
Given this S3 bucket ARN, what can you determine about the bucket?
arn:aws:s3:::my-application-bucketWhat will this code output?
✓
Correct!
S3 bucket ARNs do not include region or account ID because bucket names are globally unique across all AWS accounts. However, buckets themselves exist in a specific Region—the ARN format simply doesn’t show it. Objects stay in their Region unless explicitly replicated.
✗
Incorrect
S3 bucket ARNs do not include region or account ID because bucket names are globally unique across all AWS accounts. However, buckets themselves exist in a specific Region—the ARN format simply doesn’t show it. Objects stay in their Region unless explicitly replicated.
S3 bucket names must be globally unique, which affects the ARN format.
Question 11
Which statement about IAM (Identity and Access Management) is most accurate?
✓
Correct!
IAM is a global service, but it has regional dependencies. IAM uses AWS STS (Security Token Service) for temporary credentials, which has regional endpoints. If a region hosting STS fails, IAM operations in that region may be affected. IAM does not have a per-account home region — credential data replicates globally. Option A confuses IAM with regional services like EC2; option B misses the STS dependency; option D incorrectly applies the ‘home region’ concept (used by some other services) to IAM.
✗
Incorrect
IAM is a global service, but it has regional dependencies. IAM uses AWS STS (Security Token Service) for temporary credentials, which has regional endpoints. If a region hosting STS fails, IAM operations in that region may be affected. IAM does not have a per-account home region — credential data replicates globally. Option A confuses IAM with regional services like EC2; option B misses the STS dependency; option D incorrectly applies the ‘home region’ concept (used by some other services) to IAM.
Consider the relationship between IAM and Security Token Service (STS).
Question 12
Amazon S3 bucket names must be globally unique, but the data in buckets is always stored regionally.
✓
Correct!
True. S3 bucket names are globally unique (cannot be reused across accounts), but buckets exist in a specific Region and objects remain in that Region unless Cross-Region Replication (CRR) is configured. Note: With the new account-regional namespace feature, users no longer need to manually ensure global uniqueness, as AWS appends account and region identifiers to guarantee it. However, bucket names remain globally unique under the hood.
✗
Incorrect
True. S3 bucket names are globally unique (cannot be reused across accounts), but buckets exist in a specific Region and objects remain in that Region unless Cross-Region Replication (CRR) is configured. Note: With the new account-regional namespace feature, users no longer need to manually ensure global uniqueness, as AWS appends account and region identifiers to guarantee it. However, bucket names remain globally unique under the hood.
Think about the difference between naming and storage location.
Question 13
Which AWS services are global in scope?
✓
Correct!
Global services include IAM, Route 53, CloudFront, and AWS Organizations. Regional services include EC2, RDS, and S3. S3 is a common misconception — because bucket names must be globally unique and buckets are accessible via global URLs, learners often assume S3 is a global service. However, S3 buckets exist in a specific Region and data stays there unless explicitly replicated via Cross-Region Replication.
✗
Incorrect
Global services include IAM, Route 53, CloudFront, and AWS Organizations. Regional services include EC2, RDS, and S3. S3 is a common misconception — because bucket names must be globally unique and buckets are accessible via global URLs, learners often assume S3 is a global service. However, S3 buckets exist in a specific Region and data stays there unless explicitly replicated via Cross-Region Replication.
Global services typically relate to identity, DNS, or content delivery — not compute, storage, or databases.
Question 14
What is the minimum recommended number of Availability Zones for production workloads?
✓
Correct!
Best practice recommends using at least 2 Availability Zones for production workloads, with 3 or more preferred. Running multiple instances in a single AZ does not achieve the same fault tolerance — a power, network, or physical failure affecting that AZ would take down all instances simultaneously. Fault tolerance requires physical isolation across AZs, not just instance count.
✗
Incorrect
Best practice recommends using at least 2 Availability Zones for production workloads, with 3 or more preferred. Running multiple instances in a single AZ does not achieve the same fault tolerance — a power, network, or physical failure affecting that AZ would take down all instances simultaneously. Fault tolerance requires physical isolation across AZs, not just instance count.
Think about the minimum needed for redundancy versus the ideal setup.
Question 15
Traffic between AWS Regions stays on AWS’s private ________ network and does not traverse the public internet.
✓
Correct!
Regions are interconnected via AWS’s private, high-speed global backbone network. Traffic between Regions stays on this AWS backbone and doesn’t traverse the public internet, enabling secure, low-latency inter-region communication.
✗
Incorrect
Regions are interconnected via AWS’s private, high-speed global backbone network. Traffic between Regions stays on this AWS backbone and doesn’t traverse the public internet, enabling secure, low-latency inter-region communication.
It’s a term referring to the main high-capacity network infrastructure.
Question 16
Complete the IAM role ARN:
Fill in what belongs in the region field for IAM resources
arn:aws:iam:___:123456789012:role/MyApplicationRole✓
Correct!
IAM is a global service, so the region field is left empty (represented by ::). The ARN format shows two colons with nothing between them where the region would normally appear.
✗
Incorrect
IAM is a global service, so the region field is left empty (represented by ::). The ARN format shows two colons with nothing between them where the region would normally appear.
Question 17
When would you use AWS Local Zones instead of standard Availability Zones?
✓
Correct!
Local Zones are designed for applications requiring single-digit millisecond (sub-10ms) latency to end users in geographic areas not served by nearby AWS Regions. They’re ideal for latency-sensitive workloads like media rendering and real-time gaming, though they have limited service availability.
✗
Incorrect
Local Zones are designed for applications requiring single-digit millisecond (sub-10ms) latency to end users in geographic areas not served by nearby AWS Regions. They’re ideal for latency-sensitive workloads like media rendering and real-time gaming, though they have limited service availability.
Local Zones prioritize one specific performance characteristic.
Question 18
What information can you extract from this ARN:
arn:aws:lambda:eu-west-1:123456789012:function:my-function✓
Correct!
From the ARN, you can determine: it’s a Lambda function (service: lambda), located in eu-west-1 region, owned by account 123456789012, and named ‘my-function’. The runtime language and execution role are not part of the ARN — they are separate configuration attributes stored in the function’s settings, not encoded in its identifier.
✗
Incorrect
From the ARN, you can determine: it’s a Lambda function (service: lambda), located in eu-west-1 region, owned by account 123456789012, and named ‘my-function’. The runtime language and execution role are not part of the ARN — they are separate configuration attributes stored in the function’s settings, not encoded in its identifier.
ARNs contain structural information (where, what, whose) but not runtime configuration details.
Question 19
Resources in one AWS Region automatically replicate to other Regions for disaster recovery purposes.
✓
Correct!
False. Resources in one Region do not automatically replicate to another. Regions are designed to be completely independent and isolated. Cross-region replication must be explicitly configured using services like S3 Cross-Region Replication, DynamoDB Global Tables, or Aurora Global Database.
✗
Incorrect
False. Resources in one Region do not automatically replicate to another. Regions are designed to be completely independent and isolated. Cross-region replication must be explicitly configured using services like S3 Cross-Region Replication, DynamoDB Global Tables, or Aurora Global Database.
Think about the principle of regional independence and isolation.
Question 20
What are the key components of an AWS ARN?
What are the key components of an AWS ARN?
ARN Format: arn:partition:service:region:account-id:resource
- Partition: aws, aws-cn, or aws-us-gov
- Service: The AWS service (ec2, s3, iam, lambda, etc.)
- Region: AWS Region (omitted for global services)
- Account ID: 12-digit AWS account (omitted for globally unique names)
- Resource: Resource type and identifier (format varies by service)
Did you get it right?
✓
Correct!
✗
Incorrect
Question 21
Arrange these deployment patterns from least resilient to most resilient:
Drag to order by increasing fault tolerance
⋮⋮
Multi-Region with Cross-Region Replication
⋮⋮
Single Region, Multi-AZ
⋮⋮
Single Region, Single AZ
⋮⋮
Multi-Region without data replication
✓
Correct!
Resilience increases with geographic distribution and data availability: Single AZ (single point of failure) → Multi-AZ (protects against AZ failures, data is local) → Multi-Region without replication (infrastructure exists in multiple regions but data is not replicated, so a region failure means data loss or unavailability) → Multi-Region with Cross-Region Replication (full protection: infrastructure and data survive region-wide failures).
✗
Incorrect
Resilience increases with geographic distribution and data availability: Single AZ (single point of failure) → Multi-AZ (protects against AZ failures, data is local) → Multi-Region without replication (infrastructure exists in multiple regions but data is not replicated, so a region failure means data loss or unavailability) → Multi-Region with Cross-Region Replication (full protection: infrastructure and data survive region-wide failures).
Question 22
Which architectural pattern provides protection against both AZ failures and region-wide failures?
✓
Correct!
Multi-Region deployment with replication (CRR, Global Tables, Aurora Global Database) protects against both AZ-level and region-wide failures. Single Region Multi-AZ protects only against AZ failures. Cross-Region backups (option A) are a tempting near-miss — they provide data durability across regions but require manual failover with significant RTO/RPO, and do not provide automatic failover the way live replication does.
✗
Incorrect
Multi-Region deployment with replication (CRR, Global Tables, Aurora Global Database) protects against both AZ-level and region-wide failures. Single Region Multi-AZ protects only against AZ failures. Cross-Region backups (option A) are a tempting near-miss — they provide data durability across regions but require manual failover with significant RTO/RPO, and do not provide automatic failover the way live replication does.
Think about what’s needed to survive a complete regional outage with automatic failover.
Question 23
What does this IAM policy statement allow?
{
"Effect": "Allow",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::my-bucket/*"
}What will this code output?
✓
Correct!
This policy grants read access (GetObject) to all objects (
/*) in the specific bucket ‘my-bucket’. The wildcard (*) after the bucket name matches all object keys. It does not grant write access or access to other buckets.✗
Incorrect
This policy grants read access (GetObject) to all objects (
/*) in the specific bucket ‘my-bucket’. The wildcard (*) after the bucket name matches all object keys. It does not grant write access or access to other buckets.Focus on the Action (GetObject) and the Resource ARN with the wildcard.
Question 24
Each AWS Availability Zone has independent power, cooling, and networking infrastructure to provide fault isolation.
✓
Correct!
True. Each AZ is designed with independent power, cooling, and networking infrastructure. This independence means that a failure in one AZ (power outage, network issue, etc.) should not affect other AZs within the same Region.
✗
Incorrect
True. Each AZ is designed with independent power, cooling, and networking infrastructure. This independence means that a failure in one AZ (power outage, network issue, etc.) should not affect other AZs within the same Region.
This is a core design principle of Availability Zones.
Question 25
Which services offer features for global distribution despite being regional by default?
✓
Correct!
S3 (via Cross-Region Replication), DynamoDB (via Global Tables), and Aurora (via Global Database) are regional services with explicit global distribution features. IAM is already global (though it has regional STS dependencies, not a global distribution ‘feature’). RDS Multi-AZ is a common trap — Multi-AZ means high availability within a single Region across multiple AZs, not global distribution across Regions.
✗
Incorrect
S3 (via Cross-Region Replication), DynamoDB (via Global Tables), and Aurora (via Global Database) are regional services with explicit global distribution features. IAM is already global (though it has regional STS dependencies, not a global distribution ‘feature’). RDS Multi-AZ is a common trap — Multi-AZ means high availability within a single Region across multiple AZs, not global distribution across Regions.
Look for services that explicitly mention cross-region or global replication capabilities.
Question 26
What is the naming pattern for an AWS Local Zone in Boston associated with the us-east-1 Region?
✓
Correct!
Local Zone identifiers follow the pattern:
<parent-region>-<metro-code>-<zone-id><letter>. For Boston associated with us-east-1, it would be ‘us-east-1-bos-1a’. Other examples include us-west-2-lax-1a (Los Angeles) and us-west-2-phx-1a (Phoenix).✗
Incorrect
Local Zone identifiers follow the pattern:
<parent-region>-<metro-code>-<zone-id><letter>. For Boston associated with us-east-1, it would be ‘us-east-1-bos-1a’. Other examples include us-west-2-lax-1a (Los Angeles) and us-west-2-phx-1a (Phoenix).The format includes the parent region, a city abbreviation, and zone identifier.
Question 27
What are best practices for using Availability Zones?
What are best practices for using Availability Zones?
AZ Best Practices:
- Deploy resources across multiple AZs for high availability
- Design for AZ failure—applications should gracefully handle outages
- Use at least 2 AZs for production (3+ preferred)
- Distribute workloads evenly across AZs (avoid single-AZ dependency)
- Use load balancing and health checks for failover
- Replicate stateful services across AZs
- Prefer stateless services and use Auto Scaling
Did you get it right?
✓
Correct!
✗
Incorrect
Question 28
In the region code ‘us-east-1’, the number ‘1’ represents the ________ number.
✓
Correct!
In AWS Region naming (e.g., us-east-1), the components are: geographic area (us) - location within area (east) - region number (1). The number distinguishes between multiple regions in the same geographic area.
✗
Incorrect
In AWS Region naming (e.g., us-east-1), the components are: geographic area (us) - location within area (east) - region number (1). The number distinguishes between multiple regions in the same geographic area.
What does the ‘1’ distinguish from potential future regions in the same area?
Question 29
If you need to comply with GDPR data residency requirements, which Region selection factor is most critical?
✓
Correct!
Data sovereignty and compliance is the most critical factor for GDPR. GDPR requires data to remain within specific geographic boundaries (Europe) — this is a data residency requirement. AWS does not move data between Regions without explicit customer action, so choosing an EU Region is essential. Option D is a common trap: all AWS Regions hold ISO 27001 and SOC 2 certifications, but those certifications cover security practices, not where data physically resides. GDPR is about residency (which Region), not certification (how secure).
✗
Incorrect
Data sovereignty and compliance is the most critical factor for GDPR. GDPR requires data to remain within specific geographic boundaries (Europe) — this is a data residency requirement. AWS does not move data between Regions without explicit customer action, so choosing an EU Region is essential. Option D is a common trap: all AWS Regions hold ISO 27001 and SOC 2 certifications, but those certifications cover security practices, not where data physically resides. GDPR is about residency (which Region), not certification (how secure).
GDPR is a European regulation about data protection and privacy — specifically about where data must reside.
Question 30
New AWS services typically launch in all Regions simultaneously to ensure global availability.
✓
Correct!
False. New AWS services typically launch in us-east-1 first, then gradually expand to other Regions. Not all services are available in all Regions, which is why service availability is a factor to consider when choosing a Region.
✗
Incorrect
False. New AWS services typically launch in us-east-1 first, then gradually expand to other Regions. Not all services are available in all Regions, which is why service availability is a factor to consider when choosing a Region.
Think about how technology companies typically roll out new features.
Question 31
Complete the S3 object ARN for a file in a bucket:
Add the correct separator between bucket name and object path
arn:aws:s3:::my-bucket___path/to/file.txt✓
Correct!
S3 object ARNs use a forward slash (/) to separate the bucket name from the object key: arn:aws:s3:::my-bucket/path/to/file.txt. This follows standard path notation.
✗
Incorrect
S3 object ARNs use a forward slash (/) to separate the bucket name from the object key: arn:aws:s3:::my-bucket/path/to/file.txt. This follows standard path notation.
Question 32
An Amazon VPC exists within a single Availability Zone and cannot span multiple AZs within a Region.
✓
Correct!
False. A VPC is Regional — it spans all Availability Zones in a Region by default. Subnets are AZ-scoped (each subnet lives in exactly one AZ), which is the source of this misconception. Multi-AZ architecture works by creating separate subnets in each AZ inside the same VPC. The VPC is the regional container; the subnet is the AZ-specific boundary.
✗
Incorrect
False. A VPC is Regional — it spans all Availability Zones in a Region by default. Subnets are AZ-scoped (each subnet lives in exactly one AZ), which is the source of this misconception. Multi-AZ architecture works by creating separate subnets in each AZ inside the same VPC. The VPC is the regional container; the subnet is the AZ-specific boundary.
Think about what is AZ-scoped: the VPC itself, or the subnets inside it?
Question 33
List the four steps to start using an AWS Local Zone (first to last)
1
2
3
4
✓
Correct!
Local Zones require explicit opt-in before any resources can be deployed: (1) opt in via account settings, (2) create a subnet in your existing VPC associated with the Local Zone, (3) launch supported compute/storage resources in that subnet, (4) configure routing so end-user traffic is directed to the Local Zone. Unlike standard AZs, Local Zones are not automatically available — skipping step 1 means the Local Zone doesn’t appear as an option when creating subnets.
✗
Incorrect
Local Zones require explicit opt-in before any resources can be deployed: (1) opt in via account settings, (2) create a subnet in your existing VPC associated with the Local Zone, (3) launch supported compute/storage resources in that subnet, (4) configure routing so end-user traffic is directed to the Local Zone. Unlike standard AZs, Local Zones are not automatically available — skipping step 1 means the Local Zone doesn’t appear as an option when creating subnets.
Start with account-level enablement before any network or compute steps.
Question 34
What is the difference between these two IAM Resource values in an S3 policy:
arn:aws:s3:::my-bucket/* vs arn:aws:s3:::my-bucket*?✓
Correct!
ARN wildcards apply to the literal string.
arn:aws:s3:::my-bucket/* matches only object keys inside the bucket named exactly ‘my-bucket’ — the /* is part of the S3 key path. arn:aws:s3:::my-bucket* applies the wildcard to the bucket name itself, matching my-bucket, my-bucket-prod, my-bucket-dev, and any other bucket whose name starts with ‘my-bucket’. This is a common IAM misconfiguration: a developer intending to scope permissions to one bucket accidentally grants access to all similarly-named buckets across the account.✗
Incorrect
ARN wildcards apply to the literal string.
arn:aws:s3:::my-bucket/* matches only object keys inside the bucket named exactly ‘my-bucket’ — the /* is part of the S3 key path. arn:aws:s3:::my-bucket* applies the wildcard to the bucket name itself, matching my-bucket, my-bucket-prod, my-bucket-dev, and any other bucket whose name starts with ‘my-bucket’. This is a common IAM misconfiguration: a developer intending to scope permissions to one bucket accidentally grants access to all similarly-named buckets across the account.The wildcard position determines what part of the ARN string it expands — the bucket name or the object key path.
Question 35
An EC2 Amazon Machine Image (AMI) created in us-east-1 can be launched directly in eu-west-1 without any additional steps.
✓
Correct!
False. AMIs are Region-specific. To use an AMI in a different Region, you must first copy it to the target Region using the ‘Copy AMI’ action — this creates a new AMI with a different AMI ID in the destination Region. A common point of confusion: AWS Marketplace AMIs appear to be globally available, but under the hood AWS provides a per-region copy when you subscribe — you cannot take a us-east-1 AMI ID and use it directly as a launch parameter in eu-west-1.
✗
Incorrect
False. AMIs are Region-specific. To use an AMI in a different Region, you must first copy it to the target Region using the ‘Copy AMI’ action — this creates a new AMI with a different AMI ID in the destination Region. A common point of confusion: AWS Marketplace AMIs appear to be globally available, but under the hood AWS provides a per-region copy when you subscribe — you cannot take a us-east-1 AMI ID and use it directly as a launch parameter in eu-west-1.
Think about what happens when you try to specify a us-east-1 AMI ID in an eu-west-1 launch template.
Question 36
Which AWS services are typically available in Local Zones?
✓
Correct!
Local Zones provide a subset of AWS services focused on compute and networking close to end users: EC2 (compute), EBS (block storage), VPC (networking), ELB (load balancing), and FSx (file storage). RDS and Lambda are not available in Local Zones — managed databases and serverless compute require the full Region infrastructure. S3 is also not available directly in Local Zones; applications in Local Zones access S3 through the parent Region over the private backbone. The limited service set is why Local Zones are suited for latency-sensitive compute workloads, not full-stack deployments.
✗
Incorrect
Local Zones provide a subset of AWS services focused on compute and networking close to end users: EC2 (compute), EBS (block storage), VPC (networking), ELB (load balancing), and FSx (file storage). RDS and Lambda are not available in Local Zones — managed databases and serverless compute require the full Region infrastructure. S3 is also not available directly in Local Zones; applications in Local Zones access S3 through the parent Region over the private backbone. The limited service set is why Local Zones are suited for latency-sensitive compute workloads, not full-stack deployments.
Local Zones support compute, block storage, and networking — not managed databases or serverless.
Question 37
Your application has an RDS primary database in us-east-1. You want European users to experience lower read latency without modifying your write path. What should you configure?
✓
Correct!
Cross-region Read Replicas replicate asynchronously from the primary to a replica in another Region, letting European users query eu-west-1 at local latency while writes still go to us-east-1. Option A is the most common trap: Multi-AZ standby instances cannot serve reads — they exist solely for automatic failover. More fundamentally, AZs are within a single Region, so there is no such thing as a ‘European AZ’ inside us-east-1. Option C creates an isolated cluster with no automatic replication. Option D swaps the database technology entirely, which is out of scope.
✗
Incorrect
Cross-region Read Replicas replicate asynchronously from the primary to a replica in another Region, letting European users query eu-west-1 at local latency while writes still go to us-east-1. Option A is the most common trap: Multi-AZ standby instances cannot serve reads — they exist solely for automatic failover. More fundamentally, AZs are within a single Region, so there is no such thing as a ‘European AZ’ inside us-east-1. Option C creates an isolated cluster with no automatic replication. Option D swaps the database technology entirely, which is out of scope.
Multi-AZ is for fault tolerance within one Region; cross-region read scaling is a different feature entirely.
Question 38
What does this S3 bucket policy grant?
{
"Version": "2012-10-17",
"Statement": [{
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::987654321098:role/DataProcessingRole"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::shared-data-bucket/*"
}]
}What will this code output?
✓
Correct!
The Principal ARN
arn:aws:iam::987654321098:role/DataProcessingRole precisely identifies one specific role in one specific account — the 12-digit account ID makes it unambiguous. The Action is s3:GetObject (read-only) and /* scopes it to all objects in the bucket. Option A is wrong because IAM role names are not globally unique — without the account ID, the same role name could exist in thousands of accounts; the account ID in the ARN removes that ambiguity. Option C confuses the specific Action (GetObject) with full access. Option D confuses a specific role ARN with a whole-account principal, which would be arn:aws:iam::987654321098:root.✗
Incorrect
The Principal ARN
arn:aws:iam::987654321098:role/DataProcessingRole precisely identifies one specific role in one specific account — the 12-digit account ID makes it unambiguous. The Action is s3:GetObject (read-only) and /* scopes it to all objects in the bucket. Option A is wrong because IAM role names are not globally unique — without the account ID, the same role name could exist in thousands of accounts; the account ID in the ARN removes that ambiguity. Option C confuses the specific Action (GetObject) with full access. Option D confuses a specific role ARN with a whole-account principal, which would be arn:aws:iam::987654321098:root.The Principal ARN contains both an account ID and a specific role — both matter for what is granted.
Question 39
Your RDS instance has Multi-AZ enabled with a synchronous standby in AZ-B. The primary in AZ-A experiences a complete failure. What happens next?
✓
Correct!
RDS Multi-AZ failover is automatic and requires no manual action — AWS detects the primary failure and promotes the synchronous standby within roughly 60-120 seconds, after which your DNS endpoint resolves to the new primary. Option A describes the most common Multi-AZ misconception: the standby is not a read replica and serves no traffic during normal operation. It exists purely as a hot standby for failover; if you want read scaling, you need a Read Replica. Option C is wrong — manual failover exists as an option but is not required for automatic recovery. Option D confuses AZ-level isolation: each AZ has independent networking; an AZ-A failure does not cascade to AZ-B, which is the entire design goal of Multi-AZ.
✗
Incorrect
RDS Multi-AZ failover is automatic and requires no manual action — AWS detects the primary failure and promotes the synchronous standby within roughly 60-120 seconds, after which your DNS endpoint resolves to the new primary. Option A describes the most common Multi-AZ misconception: the standby is not a read replica and serves no traffic during normal operation. It exists purely as a hot standby for failover; if you want read scaling, you need a Read Replica. Option C is wrong — manual failover exists as an option but is not required for automatic recovery. Option D confuses AZ-level isolation: each AZ has independent networking; an AZ-A failure does not cascade to AZ-B, which is the entire design goal of Multi-AZ.
The key word in ‘Multi-AZ’ is automatic — what does that mean for the DBA during an outage?
Quiz Results
Score
0/0
Accuracy
0%
Right
0
Wrong
Skipped
0
Last updated on