Topic 1 Question 300
A company is planning to migrate several applications to AWS. The company does not have a good understanding of its entire application estate. The estate consists of a mixture of physical machines and VMs.
One application that the company will migrate has many dependencies that are sensitive to latency. The company is unsure what all the dependencies are. However the company knows that the low-latency communications use a custom IP-based protocol that runs on port 1000. The company wants to migrate the application and these dependencies together to move all the low-latency interfaces to AWS at the same time.
The company has installed the AWS Application Discovery Agent and has been collecting data for several months.
What should the company do to identify the dependencies that need to be migrated in the same phase as the application?
Use AWS Migration Hub and select the servers that host the application. Visualize the network graph to find servers that interact with the application. Turn on data exploration in Amazon Athena. Query the data that is transferred between the servers to identify the servers that communicate on port 1000. Return to Migration Hub. Create a move group that is based on the findings from the Athena queries.
Use AWS Application Migration Service and select the servers that host the application. Visualize the network graph to find servers that interact with the application. Configure Application Migration Service to launch test instances for all the servers that interact with the application. Perform acceptance tests on the test instances. If no issues are identified, create a move group that is based on the tested servers.
Use AWS Migration Hub and select the servers that host the application. Turn on data exploration in Network Access Analyzer. Use the Network Access Analyzer console to select the servers that host the application. Select a Network Access Scope of port 1000 and note the matching servers. Return to Migration Hub. Create a move group that is based on the findings from Network Access Analyzer.
Use AWS Migration Hub and select the servers that host the application. Push the Amazon CloudWalch agent to the identified servers by using the AWS Application Discovery Agent. Export the CloudWatch logs that the agents collect to Amazon S3. Use Amazon Athena to query the logs to find servers that communicate on port 1000. Return to Migration Hub Create a move group that is based on the findings from the Athena queries.
ユーザの投票
コメント(6)
- 正解だと思う選択肢: A
Answer A . Network access analyzer is to valid network usage OF aws services and not on-prem
Migration hub has feature for network visualization and Athena can be used to query data
https://aws.amazon.com/about-aws/whats-new/2020/11/aws-migration-hub-includes-network-visualization/
👍 5Sab2023/10/29 - 正解だと思う選択肢: A
Architecture pattern is Discovery Service + Migration Hub + Athena for data exploration: https://docs.aws.amazon.com/application-discovery/latest/userguide/explore-data.html
A: looks fine B: AWS Application Migration Service is for lift and shift, not for dependency mapping C: Network Access Analyzer only for AWS resource, not for on prem D: not the use case of CloudWatch.
👍 4joleneinthebackyard2023/11/01 Answer: C To identify the dependencies that need to be migrated in the same phase as the application, the company can use the AWS Application Discovery Agent data. In this case, the sensitive low-latency communications use a custom IP-based protocol that runs on port 1000. The goal is to find servers that communicate on port 1000. Option C would be the most appropriate approach
👍 2airgead2023/10/28
シャッフルモード