SNS notification types (email, SMS, Lambda) in AWS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create an SNS topic named 'MyTopic'.

AWS

aws sns create-topic --name [1]

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

ANotificationTopic

BTopicName

CSNS_Topic

DMyTopic

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different topic name than 'MyTopic'.

Omitting the --name option.

The command aws sns create-topic --name MyTopic creates an SNS topic named 'MyTopic'.

2fill in blank

medium

Complete the code to subscribe an email endpoint to the SNS topic 'MyTopic'.

AWS

aws sns subscribe --topic-arn arn:aws:sns:us-east-1:123456789012:MyTopic --protocol [1] --notification-endpoint [e-mail]

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

Alambda

Bhttp

Cemail

Dsms

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'sms' or 'lambda' instead of 'email' for email subscriptions.

Misspelling the protocol name.

To subscribe an email endpoint, the protocol must be 'email'.

3fill in blank

hard

Fix the error in the command to subscribe an SMS endpoint to the SNS topic.

AWS

aws sns subscribe --topic-arn arn:aws:sns:us-east-1:123456789012:MyTopic --protocol [1] --notification-endpoint [phone]

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

Asms

Blambda

Cemail

Dsqs

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'email' or 'lambda' as protocol for SMS subscription.

Forgetting the '+' sign in the phone number.

The correct protocol for SMS subscriptions is 'sms'.

4fill in blank

hard

Fill both blanks to subscribe a Lambda function to the SNS topic.

AWS

aws sns subscribe --topic-arn arn:aws:sns:us-east-1:123456789012:MyTopic --protocol [1] --notification-endpoint arn:aws:lambda:us-east-1:123456789012:function:[2]

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

Alambda

BMyLambdaFunction

Cemail

Dsms

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'email' or 'sms' as protocol for Lambda subscription.

Incorrect Lambda function name in the ARN.

To subscribe a Lambda function, use protocol 'lambda' and specify the Lambda function name in the ARN.

5fill in blank

hard

Fill all three blanks to create an SNS topic, subscribe an email endpoint, and publish a message.

AWS

aws sns create-topic --name [1]
aws sns subscribe --topic-arn arn:aws:sns:us-east-1:123456789012:[2] --protocol [3] --notification-endpoint [e-mail]
aws sns publish --topic-arn arn:aws:sns:us-east-1:123456789012:[2] --message "Hello from SNS!"

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

AMyTopic

Cemail

DNotificationTopic

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatch between topic name in create-topic and ARN.

Wrong protocol for email subscription.

The topic is created with name 'MyTopic'. The subscription and publish commands use the topic ARN with 'MyTopic'. The protocol for email subscription is 'email'.

Practice

1. Which of the following is NOT a valid protocol for an AWS SNS subscription?

easy

A. email

B. sms

C. lambda

D. ftp

Solution

1. Step 1: Review SNS supported protocols

   AWS SNS supports protocols like email, sms, and lambda for subscriptions.

2. Step 2: Identify unsupported protocol

   FTP is not supported as a protocol for SNS subscriptions.

3. Final Answer:

   ftp -> Option D

4. Quick Check:

   Supported protocols exclude ftp [OK]

Hint: Remember SNS supports email, sms, lambda but not ftp [OK]

Common Mistakes:

• Confusing FTP as supported protocol
• Thinking HTTP is the only protocol
• Mixing SNS with S3 protocols

2. Which is the correct way to specify an SMS subscription protocol in AWS SNS?

easy

A. Protocol: 'sms', Endpoint: '[e-mail]'

B. Protocol: 'email', Endpoint: '[phone]'

C. Protocol: 'sms', Endpoint: '[phone]'

D. Protocol: 'lambda', Endpoint: '[phone]'

Solution

1. Step 1: Understand protocol and endpoint types

   For SMS, protocol must be 'sms' and endpoint is a phone number with country code.

2. Step 2: Match correct protocol and endpoint

   Protocol: 'sms', Endpoint: '[phone]' correctly uses 'sms' protocol and a phone number endpoint.

3. Final Answer:

   Protocol: 'sms', Endpoint: '[phone]' -> Option C

4. Quick Check:

   SMS needs phone number endpoint [OK]

Hint: SMS protocol requires phone number endpoint format [OK]

Common Mistakes:

• Using email as protocol for SMS
• Using email address as SMS endpoint
• Using lambda protocol with phone number

3. Given this AWS SNS subscription code snippet:

sns.subscribe({
  Protocol: 'lambda',
  Endpoint: 'arn:aws:lambda:us-east-1:123456789012:function:ProcessMessage'
});

What happens when a message is published to this SNS topic?

medium

A. The Lambda function 'ProcessMessage' is invoked with the message payload.

B. The message is sent as an SMS to the Lambda function ARN.

C. The message is sent as an email to the Lambda function.

D. The subscription will fail because Lambda cannot be an endpoint.

Solution

1. Step 1: Identify protocol and endpoint meaning

   Protocol 'lambda' means SNS invokes the specified Lambda function ARN when a message is published.

2. Step 2: Understand message delivery behavior

   The Lambda function 'ProcessMessage' is called with the message payload as input.

3. Final Answer:

   The Lambda function 'ProcessMessage' is invoked with the message payload. -> Option A

4. Quick Check:

   Lambda protocol triggers function invocation [OK]

Hint: Lambda protocol triggers function call, not email or SMS [OK]

Common Mistakes:

• Thinking Lambda receives email or SMS
• Assuming subscription fails
• Confusing endpoint ARN with phone/email

4. You created an SNS subscription with protocol 'email' but the subscriber never receives messages. What is the most likely cause?

medium

A. The email address was not confirmed by the subscriber.

B. The SNS topic does not support email protocol.

C. The subscription endpoint was set to a phone number.

D. Lambda function is not attached to the subscription.

Solution

1. Step 1: Understand email subscription confirmation

   Email subscriptions require the recipient to confirm by clicking a link in a confirmation email.

2. Step 2: Identify common cause of no delivery

   If the email is not confirmed, SNS will not send notifications to that address.

3. Final Answer:

   The email address was not confirmed by the subscriber. -> Option A

4. Quick Check:

   Email subscriptions need confirmation [OK]

Hint: Email subscriptions require confirmation before delivery [OK]

Common Mistakes:

• Assuming SNS does not support email
• Confusing phone number as email endpoint
• Expecting Lambda involvement in email subscription

5. You want to send an SMS notification and also trigger a Lambda function whenever a message is published to an SNS topic. How should you configure the subscriptions?

hard

A. Create one subscription with protocol 'email' and endpoint as phone number, and another with protocol 'lambda' and endpoint as Lambda ARN.

B. Create one subscription with protocol 'sms' and endpoint as phone number, and another with protocol 'lambda' and endpoint as Lambda ARN.

C. Create one subscription with protocol 'lambda' and endpoint as phone number, and another with protocol 'sms' and endpoint as Lambda ARN.

D. Create one subscription with protocol 'sms' and endpoint as Lambda ARN, and another with protocol 'lambda' and endpoint as phone number.

Solution

1. Step 1: Understand protocol and endpoint matching

   SMS protocol requires a phone number endpoint; Lambda protocol requires Lambda function ARN.

2. Step 2: Configure two subscriptions correctly

   Create one subscription with protocol 'sms' and phone number endpoint, and another with protocol 'lambda' and Lambda ARN endpoint.

3. Final Answer:

   Create one subscription with protocol 'sms' and endpoint as phone number, and another with protocol 'lambda' and endpoint as Lambda ARN. -> Option B

4. Quick Check:

   Match protocol to correct endpoint type [OK]

Hint: Match SMS to phone number, Lambda to function ARN [OK]

Common Mistakes:

• Mixing endpoints and protocols
• Using email protocol for SMS
• Assigning Lambda ARN as SMS endpoint