DAS-C01 · Question #156
A company hosts an Apache Flink application on premises. The application processes data from several Apache Kafka clusters. The data originates from a variety of sources, such as web applications…
The correct answer is D. Create an Amazon Kinesis Data Analytics application by uploading the compiled Flink jar file. To migrate an on-premises Apache Flink application to AWS with the least operational overhead, the best solution is to use Amazon Kinesis Data Analytics for Apache Flink. This fully managed service supports uploading existing Flink JAR files and can process data from various…
Question
A company hosts an Apache Flink application on premises. The application processes data from several Apache Kafka clusters. The data originates from a variety of sources, such as web applications mobile apps and operational databases. The company has migrated some of these sources to AWS and now wants to migrate the Flink application. The company must ensure that data that resides in databases within the VPC does not traverse the internet. The application must be able to process all the data that comes from the company's AWS solution, on-premises resources and the public internet. Which solution will meet these requirements with the LEAST operational overhead?
Options
- AImplement Flink on Amazon EC2 within the company's VPC
- BImplement Flink on Amazon EC2 within the company's VPC
- CCreate an Amazon Kinesis Data Analytics application by uploading the compiled Flink jar file
- DCreate an Amazon Kinesis Data Analytics application by uploading the compiled Flink jar file
How the community answered
(19 responses)- A11% (2)
- B5% (1)
- C5% (1)
- D79% (15)
Why each option
To migrate an on-premises Apache Flink application to AWS with the least operational overhead, the best solution is to use Amazon Kinesis Data Analytics for Apache Flink. This fully managed service supports uploading existing Flink JAR files and can process data from various sources including on-premises and within a VPC without internet traversal.
Implementing Flink on Amazon EC2 requires manual management of EC2 instances, Flink cluster setup, scaling, patching, and monitoring, which entails significant operational overhead.
Implementing Flink on Amazon EC2 requires manual management of EC2 instances, Flink cluster setup, scaling, patching, and monitoring, which entails significant operational overhead.
This option is effectively the same as D but is indicated as a wrong answer in the provided question format, likely due to a subtle distinction or ordering not apparent in the text.
Amazon Kinesis Data Analytics for Apache Flink is a fully managed service that allows you to run Apache Flink applications without managing servers, greatly reducing operational overhead compared to self-managing Flink on EC2. It supports uploading existing Flink JAR files and can be configured to access data sources within a VPC using private endpoints, ensuring data does not traverse the internet.
Concept tested: Migrating Apache Flink to serverless AWS
Source: https://aws.amazon.com/kinesis/data-analytics/apache-flink/
Topics
Community Discussion
No community discussion yet for this question.