aws_resource_deployment

Question 1

Bot (JSON file)

Answer 1

Lex Bot configuration. Deploy in Amazon Lex Console under Bots. Creates the natural language intents and utterances that contact flows reference.

Question 2

ivr-router (Python file)

Answer 2

Lambda function code. Deploy in AWS Lambda Console. Create new function | paste code | configure layers and environment variables.

Question 3

prompts (JSON file)

Answer 3

Prompt configuration file. Audio prompts upload to Amazon Connect Console under Prompts. Text-to-speech configs may be stored in S3 and referenced by Lambda.

Question 4

prompts-api-uat (JavaScript file)

Answer 4

Lambda function for prompt management. Deploy in AWS Lambda Console as Node.js runtime. Handles CRUD operations for prompts.

Question 5

routing-ddb-example-item (JSON file)

Answer 5

DynamoDB table structure. Deploy in DynamoDB Console. Create table first then use this JSON as template for items.

Question 6

Contact Flow JSON files

Answer 6

Import directly into Amazon Connect Console. Go to Flows | Create flow | Import (top menu) | select JSON file.

Question 7

Where do Lambdas get deployed?

Answer 7

AWS Lambda Console. Create function | select runtime (Python or Node.js) | paste code | configure timeout | memory | environment variables | and layers.

Question 8

Where do Lex Bots get deployed?

Answer 8

Amazon Lex Console. Create bot | define intents | add utterances | build and publish. Then reference bot in contact flow Get customer input blocks.

Question 9

Where do DynamoDB tables get deployed?

Answer 9

DynamoDB Console. Create table | define partition key and sort key | add items using JSON structure from example files.

Question 10

Where do prompts get deployed?

Answer 10

Amazon Connect Console under Prompts for audio files. Or S3 bucket for dynamic prompt content referenced by Lambda.

Question 11

Where do contact flows get deployed?

Answer 11

Amazon Connect Console under Flows. Import JSON files or create manually in flow designer.

Question 12

What is the relationship between Lambda and Contact Flow?

Answer 12

Contact flow invokes Lambda using Invoke AWS Lambda block. Lambda returns attributes that contact flow uses for routing decisions.

Question 13

What is the relationship between Lex and Contact Flow?

Answer 13

Contact flow uses Get customer input block with Lex bot. Lex interprets caller speech and returns intent to contact flow for branching.

Question 14

What is the relationship between DynamoDB and Lambda?

Answer 14

Lambda queries DynamoDB tables to retrieve routing configurations | business hours | queue assignments. Returns data to contact flow as attributes.

Question 15

What is the relationship between DynamoDB and Contact Flow?

Answer 15

No direct relationship. Contact flows cannot query DynamoDB directly. Must use Lambda as intermediary to query and return data.

Question 16

Why did Bot file error when importing to Flows?

Answer 16

Bot is a Lex configuration not a contact flow. Different resource type that deploys to Amazon Lex Console not Amazon Connect Flows.

Question 17

Why did ivr-router error when importing to Flows?

Answer 17

ivr-router is Python Lambda code not a contact flow JSON. Deploys to AWS Lambda Console not Amazon Connect Flows.

Question 18

Why did routing-ddb-example-item error when importing to Flows?

Answer 18

DynamoDB item structure not a contact flow. Used to create table items in DynamoDB Console not imported to Amazon Connect.

Question 19

Why did prompts-api-uat error when importing to Flows?

Answer 19

JavaScript Lambda code not a contact flow. Deploys to AWS Lambda Console as Node.js function.

Question 20

What AWS services make up a production Amazon Connect solution?

Answer 20

Amazon Connect for flows and routing | AWS Lambda for business logic | Amazon Lex for NLP | DynamoDB for configuration data | S3 for prompts and storage | CloudWatch for logging.

Question 21

What order should you deploy resources?

Answer 21

1 DynamoDB tables first | 2 Lambda functions second | 3 Lex bots third | 4 Contact flows last. Flows reference the other resources so they must exist first.

Question 22

Why deploy DynamoDB first?

Answer 22

Lambda functions query DynamoDB tables. Tables must exist before Lambda can be tested or contact flows can work properly.

Question 23

Why deploy Lambda before contact flows?

Answer 23

Contact flows invoke Lambda functions by ARN. Lambda must exist and be published before contact flow can reference it.

Question 24

Why deploy Lex before contact flows?

Answer 24

Contact flows reference Lex bot by name and alias. Bot must be built and published before contact flow can use it.

Question 25

What happens if you publish a contact flow before Lambda exists?

Answer 25

Flow will error when it tries to invoke Lambda. The Invoke Lambda block will fail and route to error branch.

Question 26

What happens if you publish a contact flow before Lex bot exists?

Answer 26

Flow will error when it tries to get customer input from Lex. The Get customer input block will fail.

Question 27

What happens if Lambda runs before DynamoDB table exists?

Answer 27

Lambda will throw an error when trying to query non-existent table. Returns error to contact flow which routes to error branch.

Question 28

Saved vs Published status in Flows console?

Answer 28

Saved means changes stored but not live. Published means flow is active in production. Your imported flows show Saved so they are not live yet.

Question 29

What must you do after importing contact flows?

Answer 29

Update resource references like Lambda ARNs | Lex bot names | queue names | prompt names. Then publish to make live.

Question 30

Why do imported flows need updates before publishing?

Answer 30

Flows reference resources from original environment. Your instance has different ARNs | queue names | and resource IDs that must be updated.