How to Collect Migration Evaluator Assessment and VM Dependencies with Least Overhead?
Answer
Correct answer: D — Use the Migration Evaluator Collector for the Quick Insights report and install the Application Discovery Agent on each VM so Migration Hub can map dependencies.
A company plans to migrate many VMs from an on-premises environment to AWS. The company requires an initial assessment of the on-premises environment before the migration, a visualization of the dependencies between applications that run on the VMs, and a report that provides an assessment of the on-premises environment. To get this information, the company has initiated a Migration Evaluator assessment request. The company has the ability to install collector software in its on-premises environment without any constraints Which solution will provide the company with the required information with the LEAST operational overhead?
Community Insight
The question tests the division of labor between Migration Evaluator's Quick Insights report and Application Discovery Service's dependency mapping; the trap is assuming Migration Hub can produce the Quick Insights report from Discovery Agent data alone.
Migrating numerous on-premises VMs requires both a Migration Evaluator assessment report and AWS Application Discovery Service data for dependency visualization. This page establishes that option D provides both through the Migration Evaluator Collector and per-VM Discovery Agents with the least manual integration.
The most common wrong answer is A, because installing only the Discovery Agent looks like the lowest-effort path, but it leaves out the Migration Evaluator Collector needed for the Quick Insights assessment report.
Community Discussion (23 comments)
wmp7039
👍 1
Selected: D
Why D: - Migration Evaluator Collector (agentless, deployed once in the environment) is what feeds the Migration Evaluator assessment the company already initiated — it produces the Quick Insights report. That report is a Migration Evaluator artifact, not a Migration Hub one. - Application Discovery Agent on each VM is the only option that captures network connection data needed for application dependency visualization in Migration Hub. The question explicitly says installing collector software is unconstrained, which is the hint that per-VM agents are acceptable.
Amac1979
👍 1
Selected: D
Migration Evaluator Collector → collects resource utilization data → generates Quick Insights assessment report (cost, right-sizing recommendations) Application Discovery Agent on each VM → captures network connections, process info → sends to Migration Hub → visualizes dependencies between applications
AlexD332
👍 2
Selected: D
Steps: Migration Evaluator Collector Collects infrastructure data for assessment & TCO Application Discovery Agent on VMs Captures application dependency mapping View dependencies in Migration Hub Generate Quick Insights report from Migration Evaluator This solution: Provides assessment + dependency mapping Uses standard AWS migration workflow Minimal manual integration
DANMUSO
👍 2
Selected: D
D. Set up the Migration Evaluator Collector in the on-premises environment. Install the AWS Application Discovery Agent on each VM. After the data collection period ends, use AWS Migration Hub to view the application dependencies. Download the Quick Insights assessment report from Migration Evaluator. ✅ Fulfills the Migration Evaluator requirement (assessment and Quick Insights). ✅ Fulfills the dependency mapping requirement (via Application Discovery Agent). ✅ Uses Migration Hub to visualize dependencies. ✅ Provides a Quick Insights assessment report, as the question requires. ✅ Minimal operational overhead, since you're allowed to install software freely
zhen234
👍 1
Selected: B
The Migration Evaluator Collector is better for high-level assessment and cost planning, while the Application Discovery Agentless Collector is suited for detailed dependency analysis between applications and VMs.
BeyondCoder
👍 1
Selected: C
Option C is correct. https://aws.amazon.com/about-aws/whats-new/2024/11/network-connections-aws-application-discovery-service-agentless-collector/?nc1=h_ls
TomTom
👍 1
Selected: B
The solution that provides the company with the required information with the least operational overhead is B: Install the Migration Evaluator Collector on each on-premises VM. This method allows for efficient data collection, enabling the use of Migration Evaluator to visualize application dependencies and download the Quick Insights assessment report easily. This approach minimizes complexity compared to options that require multiple software installations or data transfers between services, thus reducing operational overhead significantly
AzureDP900
👍 1
This solution requires minimal operational overhead as it only involves installing a small agent (AWS Application Discovery Agent) on each VM, which can be done without disrupting the environment. The AWS Application Discovery Service is an agentless collector that can discover resources in your organization without requiring any configuration or agent installation. However, in this case, the company has already initiated a Migration Evaluator assessment request and can use the built-in capabilities of Migration Hub to collect information about their on-premises environment.
AzureDP900
👍 1
A is correct
0b43291
👍 2
Selected: A
Option A is the answer with the least operational overhead because it leverages the AWS Application Discovery Agent, which can be installed on each on-premises VM to collect configuration data, performance metrics, and application dependencies. AWS Migration Hub integrates with Application Discovery Service, providing a centralized view of discovered servers, dependencies, and migration status. Migration Hub allows visualizing application dependencies and provides the Quick Insights assessment report, fulfilling all requirements. By using a single agent and Migration Hub's built-in capabilities, Option A minimizes operational overhead and provides a streamlined solution for the required information.
Danm86
👍 1
I think option A is correct
JoeTromundo
👍 3
Selected: A
"AGENT-BASED discovery can be performed by deploying the AWS Application Discovery Agent on each of your VMs and physical servers. The agent installer is available for Windows and Linux operating systems. It collects static configuration data, detailed time-series system-performance information, INBOUND AND OUTBOUND NETWORK CONNECTIONS, and processes that are running."
Syre
👍 3
Selected: A
The question clearly states, "The company has the ability to install collector software in its on-premises environment without any constraints"
Chungies
👍 1
They have the capability of accepting installs on their VM so I will go with A. It can not be the agent less because there is no mention that they can not allow installs on their VMs
asquared16
👍 1
Selected: C
the key word here is "many" VMs, hence C.
Russs99
👍 9
Selected: A
Option C is not the least operation overhead. it requires Application Discovery agentless Collector + Export & Upload of the report. also, Discovery agentless will not gather data for all dependencies.
toma
👍 2
it should be A, as you can see on this link: https://aws.amazon.com/migration-evaluator/ agentless collector should be used, it is simple.
toma
👍 1
sorry i wanted to say C
5ehjry6sktukliyliuliykutjhy
👍 9
Selected: C
For VMs use agentless unless you need to track network
Spike2020
👍 3
requirement is to discover application dependency. So that needs to track network. So it should be A.
5ehjry6sktukliyliuliykutjhy
👍 1
Option C: Use Agentless for VMs
mifune
👍 7
Selected: A
"To get this information, the company has initiated a Migration Evaluator assessment request. The company has the ability to install collector software in its on-premises environment without any constraints", so I understand from the question that the next step would be installing the AWS Application Discovery Agent on each on-premises VM, so for me the answer is A.
zapper1234
👍 4
B is the correct answer becuase you would use migration evaluater
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D is the only choice that explicitly supplies both data sources the scenario requires. The Migration Evaluator Collector feeds the Migration Evaluator assessment and produces the Quick Insights report that the company requested when it initiated the Migration Evaluator assessment request. Separately, the AWS Application Discovery Agent runs on each VM and collects inbound and outbound network connections and process data, which AWS Migration Hub uses to visualize application dependencies. Combining those managed AWS workflows avoids manual export/upload or QuickSight steps, so it has the least operational overhead among the options that actually satisfy all three requirements. The no-constraint statement also makes per-VM agent installation acceptable.Why the Other Options Are Wrong
Option A installs the Discovery Agent and uses Migration Hub for dependencies, but it omits the Migration Evaluator Collector and misattributes the Quick Insights report to Migration Hub; Quick Insights is a Migration Evaluator deliverable. Option B incorrectly installs the Migration Evaluator Collector on each VM, while the collector is an on-premises data collector, and it adds QuickSight and export steps while still not providing the required dependency mapping. Option C relies on agentless discovery for dependencies and then requires exporting the ADS server list and uploading it to Migration Evaluator, adding manual overhead and risking incomplete network-connection data for application dependency visualization. Those defects make A, B, and C incomplete or more operationally heavy than D.Community Comment Notes
Russs99 argued that option C is not least overhead because it requires an agentless collector plus export and upload, and noted that agentless discovery may not gather all dependencies; that point supports using the ADS Agent for dependency data, but it does not remove the need for Migration Evaluator to generate the Quick Insights report. Another commenter observed, "For VMs use agentless unless you need to track network," which is exactly why this scenario's dependency visualization requirement points to agent-based discovery. AlexD332 described the same split as option D: Migration Evaluator Collector for the assessment report and ADS Agent on the VMs for dependency mapping viewed in Migration Hub. The A-leaning comments correctly emphasize least overhead but overlook that the Quick Insights report must come from Migration Evaluator, not Migration Hub alone.Official Reference
Exam Strategy
When an option claims a report comes from a different service than the one named in the stem, verify the service integration before choosing the 'least overhead' path. Here, dependency visualization requires ADS network-connection data, while the Quick Insights assessment is a Migration Evaluator output, so the complete solution needs both.
Frequently Asked Questions
Why can't AWS Migration Hub alone generate the Quick Insights report?
Quick Insights is produced by Migration Evaluator; Migration Hub visualizes ADS discovery data but does not replace the Migration Evaluator Collector or its assessment workflow.
Is agentless Application Discovery enough for VM dependency mapping?
Agentless collection is useful for inventory, but application dependency visualization often needs agent-based inbound/outbound network connection data, especially when the scenario permits installing agents on every VM.
Related Analysis
Practice All SAP-C02 Questions
Access 85 questions with complete answers and detailed explanations.
View Full SAP-C02 Practice Test →