Which steps should a solutions architect take to build the solution?
(Choose three.)
Establish an AWS Direct Connect connection from the on-premises data center to AWS.
Create an Amazon EC2 Auto Scaling group to pull the messages from the on-premises Kafka cluster and use the Amazon Consumer Library to put the data into an Amazon Kinesis data stream.
Create an Amazon EC2 Auto Scaling group to pull the messages from the on-premises Kafka cluster and use the Amazon Kinesis Producer Library to put the data into a Kinesis data stream.
Create a WebSocket API in Amazon API Gateway, create an AWS Lambda function to process an Amazon Kinesis data stream, and use the @connections command to send callback messages to connected clients.
Create a GraphQL API in AWS AppSync, create an AWS Lambda function to process the Amazon Kinesis data stream, and use the @connections command to send callback messages to connected clients.
Establish a Site-to-Site VPN from the on-premises data center to AWS.
Explanations:
AWS Direct Connect provides a dedicated, consistent, and low-latency network connection between the on-premises data center and AWS, ensuring reliable and high-performance data transfer.
The Amazon Consumer Library is used to pull data from Amazon Kinesis, not from Kafka. The appropriate solution would use the Kinesis Producer Library to send data into Kinesis.
The Amazon Kinesis Producer Library (KPL) is designed to efficiently push data into Amazon Kinesis data streams, which is suitable for the use case of ingesting stock market data into a scalable AWS service.
A WebSocket API in API Gateway with Lambda processing Kinesis data streams can efficiently provide real-time updates to web clients by using WebSocket connections to push data as events.
AWS AppSync, which is used for GraphQL APIs, is better suited for managing data in real-time between client apps and backend services. However, WebSocket APIs are more appropriate for stock market data due to simpler integration and lower latency needs.
A Site-to-Site VPN is suitable for secure communication between on-premises networks and AWS but does not provide the same high-throughput and low-latency benefits as AWS Direct Connect. It is less optimal for the required performance.
I sort that the answer is:
Establish an AWS Direct Connect connection from the on-premises data center to AWS.