lambda_flows_intermediate_flashcardsv3

Question 1

Synchronous Lambda Invocation

Answer 1

Flow invokes Lambda function and waits until function completes processing before moving to next step. Flow uses result to determine next action.

Question 2

Lambda Timing Constraint

Answer 2

Amazon Connect flow block waits maximum of 8 seconds for Lambda to return result. Timeout value is configurable but cannot exceed 8 seconds.

Question 3

Flow Timeout vs Lambda Timeout

Answer 3

Amazon Connect flow timeout and Lambda function timeout need to match. If flow times out before Lambda completes

Question 4

Asynchronous Invocation Need

Answer 4

If function requires more than 8 seconds to complete

Question 5

CloudWatch REPORT Log

Answer 5

Contains unique request identifier

Question 6

Lambda Duration Testing

Answer 6

Test function in Lambda console or check CloudWatch log group for duration. REPORT log shows exact processing time in milliseconds.

Question 7

Query Data Sources Use Case

Answer 7

Query internal and external data sources to retrieve system or contact information. Use to personalize interaction

Question 8

Self-Service Implementation Use Case

Answer 8

Interact with other AWS services and third-party applications to implement self-service options for customers.

Question 9

Update Data Sources Use Case

Answer 9

Update internal and external data sources using information collected during contact interaction with the flow.

Question 10

DynamoDB Lookup Pattern

Answer 10

Lambda function performs DynamoDB lookup to retrieve configuration settings. Returns data like language and line of business name for branded greeting.

Question 11

Synchronous Response Speed

Answer 11

When Lambda runs successfully it returns response within milliseconds. Flow waits for response before continuing and contact experience is not affected.

Question 12

Error Path Timeout

Answer 12

If Lambda does not return response within 8 seconds

Question 13

Fallback Strategy

Answer 13

Experience designer implements fallback that selects default language and offers generic greeting if Lambda times out or errors.

Question 14

Retry Logic

Answer 14

Implement retry logic in code to handle intermittent errors. Helps ensure function completes successfully despite temporary issues.

Question 15

Error Information Return

Answer 15

Return information about any error so flow can use this to fall back on default behavior. Enables graceful degradation.

Question 16

Processing Time Testing

Answer 16

Time test Lambda function processing time under different conditions. Ensures function completes within allotted timeout.

Question 17

Asynchronous Lambda Pattern

Answer 17

Flow invokes first Lambda synchronously which immediately invokes second Lambda asynchronously and returns. Second Lambda handles long running process while flow continues.

Question 18

Process Tracker Record

Answer 18

First Lambda creates tracker record in DynamoDB table to monitor asynchronous process status. Later Lambda function checks this tracker for results.

Question 19

Multi-Step Process Orchestration

Answer 19

Multi-Step Process Orchestration uses Lambda with custom state machines or Step Functions workflows to coordinate multiple AWS services in sequence. Unlike simple Lambda functions, this approach manages complex workflows with conditional logic, parallel processing, and error handling. It updates process status quickly throughout execution, allowing you to track progress and handle failures gracefully across multiple service calls.

Question 20

Get Results Lambda

Answer 20

Third Lambda function verifies results of asynchronous process by checking tracker status. Returns status back to flow for decision making.

Question 21

20 Second Sequence Limit

Answer 21

Amazon Connect limits duration of sequence of Lambda functions to 20 seconds. Break up sequences to invoke multiple functions lasting longer than threshold.

Question 22

Voice Contact Silence

Answer 22

Contact experiences silence when flow runs Lambda function. If total runtime exceeds timeout contact receives error message.

Question 23

Money Transfer Use Case

Answer 23

Lambda starts transfer request with third-party application and immediately returns. Process runs to completion with continuous status updates checked by different Lambda.

Question 24

Loop Logic Pattern

Answer 24

Flow implements loop logic so long process can complete without affecting contact experience. Checks status periodically while keeping customer engaged.

Question 25

Transaction Verification Use Case

Answer 25

High-value transactions use Step Functions to perform security checks asynchronously, allowing customers to receive status confirmation via text or callback instead of waiting on line. This pattern is perfect for processes that take several minutes - like fraud verification, credit checks, or large payment authorizations - where keeping customers on hold would be a poor experience. Emphasize that asynchronous processing improves customer experience by eliminating hold times, Step Functions handles all the orchestration and retry logic automatically, and status updates via SMS/callback keep customers informed without them having to check manually.​​​​​​​​​​​​​​​​

Question 26

Step Functions State Machine

Answer 26

Orchestrates workflow by invoking multiple Lambda functions in sequence. Evaluates conditions and routes to different functions based on results.

Question 27

Compliance Check Pattern

Answer 27

State machine first invokes compliance check Lambda. If approved invokes tax verification Lambda. Routes to approved or rejected transaction Lambda based on results.

Question 28

Follow-Up Confirmation Methods

Answer 28

For completed transactions send SMS message or create task for agent callback. Based on customer's preferred method of contact.

Question 29

Asynchronous Use Cases

Answer 29

Updating contact information to external data sources

Question 30

Status Update Pattern

Answer 30

Asynchronous Lambda updates tracker status every time process status changes. Allows flow to check progress without blocking contact.

Question 31

Avoiding Abandoned Transactions

Answer 31

Use asynchronous pattern with SMS or callback for long processes. Prevents customers from abandoning while waiting on line for 18-22 minute processes.

Question 32

Flow Block Error Handling

Answer 32

Experience designers implement default behavior when Lambda fails. Example: set default language if Lambda can't retrieve preference.

Question 33

Success Branch

Answer 33

Indicates Lambda invocation was successful. Invocation event with request body and metadata was emitted and Lambda function runs.

Question 34

Error Branch Scenarios

Answer 34

Lambda didn't return result within timeout

Question 35

Lambda Retry Behavior

Answer 35

Lambda Retry Behavior refers to what happens when a function returns an error after running. By default, Lambda automatically retries failed asynchronous invocations (from services like EventBridge, SNS, or SQS) twice with delays between attempts. For synchronous invocations (like from API Gateway or Connect), there’s no automatic retry - the error is immediately returned to the caller. Understanding this behavior is crucial for building resilient systems.

Question 36

Retry Mechanism Pattern

Answer 36

When Invoke block takes error branch

Question 37

Error Context in Response

Answer 37

Include context information when formatting Lambda response. Pass back error information so flows can implement actions based on response.

Question 38

Flow Actions from Error Info

Answer 38

Retry Lambda invocation

Question 39

Operation Property

Answer 39

Determines which operation the Lambda function performed. Example values: verifyLimit and updateBalance.

Question 40

Result Property

Answer 40

Determines if the operation was successful. Indicates success or error status.

Question 41

Error Property

Answer 41

Short description of the error. Values can be timeout

Question 42

Resilient Flow Design

Answer 42

Handle errors in Lambda code and send error context back to flow. Creates seamless user experience despite function failures.

Question 43

Response Size Limit

Answer 43

Lambda function response that is too large triggers error branch. Keep responses within size limits.

Question 44

Invalid Response

Answer 44

Lambda function returns response that doesn't match expected format. Triggers error branch in flow block.

Question 45

Graceful Error Handling

Answer 45

Implement logic to handle failed transactions without impacting contact experience. Sometimes retry is appropriate

Question 46

Error Information Benefits

Answer 46

Experience designers create dynamic flow behaviors based on error types and reasons for failure. Enables appropriate response to different error conditions.

Question 47

CloudWatch for Amazon Connect

Answer 47

Monitors AWS resources and applications in real time. Collects

Question 48

Flow Logs Storage

Answer 48

Flow logs stored in CloudWatch log group in same AWS Region as Amazon Connect instance. Log group automatically created when flow logs enabled.

Question 49

Flow Logs Requirements

Answer 49

Enable Flow logs setting in instance configuration and include Set logging behavior block with logging enabled in flow. Both conditions must be met.

Question 50

Flow Log Group Path

Answer 50

Logs available at /aws/connect/ in CloudWatch Logs section under Log groups.

Question 51

Successful Lambda Log Event

Answer 51

Shows ContactId

Question 52

Failed Lambda Log Event

Answer 52

Starts with Results property indicating error. Contains ContactId

Question 53

Filter Patterns

Answer 53

Extract only log events of interest. Example: { $.ContactFlowModuleType = "InvokeExternalResource" } lists all Invoke Lambda block events.

Question 54

ContactFlowErrors Metric

Answer 54

Number of times the error branch for a flow was run. Helps identify errors raised by Amazon Connect flows including Lambda invocation errors.

Question 55

ContactFlowFatalErrors Metric

Answer 55

Number of times a flow failed to run because of a system error. Indicates critical flow failures.

Question 56

CloudWatch Alarms

Answer 56

Setup alarms for flow error metrics to get notified when errors exceed thresholds. Part of operational excellence for contact center.

Question 57

CloudWatch Dashboards

Answer 57

Add flow error metrics to operational dashboard. Provides visual overview of all errors in flows.

Question 58

Logs Insights

Answer 58

CloudWatch functionality to query log streams for specific events. Monitor only Lambda invocation errors instead of all flow errors.

Question 59

Invocation Errors Query

Answer 59

Filters all Results log events that indicate Lambda function invocation in flows. Shows all Lambda invocations regardless of success.

Question 60

Failed Lambda Query

Answer 60

Selects all log events with properly formatted result where result property value is failed. Identifies Lambda functions that returned failure status.

Question 61

Endpoint Timeout Query

Answer 61

Lists log events where result is failed and error property is endpointTimeout. Identifies specific failure type from external provider timeouts.

Question 62

Proactive Monitoring Approach

Answer 62

Monitor overall flow errors

Question 63

Chart and Alert Configuration

Answer 63

Add query data to operational dashboard as Chart. Create alerts based on identified thresholds for proactive monitoring.

Question 64

Error Response Benefits

Answer 64

Format Lambda error responses with operation