AWS Certified Cloud Practitioner
Get started today
Ultimate access to all questions.
Deep dive into the quiz with AI chat providers.
We prepare a focused prompt with your quiz and certificate details so each AI can offer a more tailored, in-depth explanation.
A company is building a chatbot using Amazon Lex and wants to execute custom business logic—such as validating user input or checking inventory—during the conversation. Which AWS service should they integrate with Lex?
Real Exam
Community
RRitesh
0
A
Amazon Aurora
B
Amazon Lambda
C
Amazon OpenSearch
D
Amazon SNS
Explanation:
Explanation
Amazon Lambda is the correct service to integrate with Amazon Lex for executing custom business logic during chatbot conversations.
Key Reasons:
-
AWS Lambda Integration: Amazon Lex has native integration with AWS Lambda functions, which allows you to run custom code in response to user inputs.
-
Business Logic Execution: Lambda functions can:
- Validate user input data
- Check inventory levels in databases
- Perform calculations or data transformations
- Integrate with other AWS services
- Execute conditional logic based on conversation context
-
Event-Driven Architecture: When a user interacts with the Lex chatbot, Lex can trigger Lambda functions to process the input before returning a response.
-
Serverless Benefits: Lambda provides serverless compute, meaning you don't need to manage servers and only pay for the compute time you consume.
Why Other Options Are Incorrect:
- A. Amazon Aurora: This is a relational database service, not designed for executing custom business logic in chatbot conversations.
- C. Amazon OpenSearch: This is a search and analytics service, useful for search operations but not for executing custom business logic during conversations.
- D. Amazon SNS: This is a messaging service for sending notifications, not for executing custom code logic.
Best Practice:
When building chatbots with Amazon Lex, Lambda functions are commonly used for:
- Input validation and sanitization
- Database queries (DynamoDB, RDS, etc.)
- External API calls
- Complex decision-making logic
- State management across conversation turns
Comments
Loading comments...