Reliability pillar principles in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to specify the AWS service that helps recover from infrastructure failures automatically.

AWS

Use AWS [1] to automatically replace unhealthy instances in your application.

Drag options to blanks, or click blank then click option'

AAuto Scaling

BLambda

CS3

DCloudFormation

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing CloudFormation which is for infrastructure as code, not automatic recovery.

Selecting S3 which is storage, not related to instance health.

Picking Lambda which is for serverless functions, not instance replacement.

AWS Auto Scaling automatically replaces unhealthy instances to maintain application availability.

2fill in blank

medium

Complete the code to choose the AWS feature that helps distribute traffic across multiple resources.

AWS

Use [1] to balance incoming traffic and improve fault tolerance.

Drag options to blanks, or click blank then click option'

AElastic Load Balancer

BCloudWatch

CCloudTrail

DIAM

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing CloudTrail which is for logging, not traffic distribution.

Selecting CloudWatch which monitors resources but does not distribute traffic.

Picking IAM which manages permissions, unrelated to traffic.

Elastic Load Balancer distributes traffic across multiple targets to increase reliability.

3fill in blank

hard

Fix the error in the code to correctly enable multi-AZ deployment for high availability.

AWS

Create an RDS instance with MultiAZ set to [1].

Drag options to blanks, or click blank then click option'

A"false"

BFalse

Ctrue

DTrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using lowercase 'true' or 'false' as strings instead of boolean values.

Using quotes around boolean values.

The MultiAZ parameter requires a boolean True (capital T) to enable multi-AZ deployment.

4fill in blank

hard

Fill both blanks to create a CloudWatch alarm that triggers when CPU usage is above 80%.

AWS

alarm = cloudwatch.put_metric_alarm(MetricName='CPUUtilization', Threshold=[1], ComparisonOperator='[2]')

Drag options to blanks, or click blank then click option'

A80

BGreaterThanThreshold

CLessThanThreshold

D70

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'LessThanThreshold' which triggers alarm when usage is below threshold.

Setting threshold to 70 instead of 80.

The threshold should be 80 and the comparison operator 'GreaterThanThreshold' to alert when CPU usage exceeds 80%.

5fill in blank

hard

Fill all three blanks to define a lifecycle policy that transitions objects to Glacier after 30 days and expires after 365 days.

AWS

lifecycle = {
  'Rules': [{
    'ID': 'ArchiveRule',
    'Status': '[1]',
    'Transitions': [{'Days': [2], 'StorageClass': '[3]'}],
    'Expiration': {'Days': 365}
  }]
}

Drag options to blanks, or click blank then click option'

AEnabled

BDisabled

CGLACIER

DSTANDARD_IA

E30

Attempts:

3 left

💡 Hint

Common Mistakes

Setting status to 'Disabled' which turns off the rule.

Using 'STANDARD_IA' instead of 'GLACIER' for archiving.

Incorrect number of days for transition.

The lifecycle rule must be 'Enabled', transition after 30 days, and use 'GLACIER' storage class for archiving.