While preparing for the AWS SAP-C02, many candidates struggle with selecting the appropriate discovery and migration tooling to gather accurate server metadata. In the real world, this is fundamentally a decision about balancing operational effort versus data completeness and cost efficiency. Let’s drill into a simulated scenario.
The Scenario #
Finserv Global, a multinational financial services company, is embarking on the first phase of a large-scale cloud transformation. The company intends to migrate approximately 1000 on-premises virtualized servers running in multiple VMware clusters hosted in their own data centers, into AWS.
As part of the migration planning process, Finserv Global wants to accurately collect detailed server metrics, including CPU utilization, memory consumption, operating system details, and running processes — all critical to right-sizing instances and licensing in AWS.
Key Requirements #
Select the most cost-effective and operationally feasible method to collect and query detailed server inventory and performance data with minimal impact on existing production workloads.
The Options #
- A) Deploy the AWS Agentless Discovery Connector virtual appliance on-premises, configure it with AWS Migration Hub to collect server details; process collected data with AWS Glue ETL jobs; query data using Amazon S3 Select.
- B) Export only basic VM performance metrics locally; import this data manually into AWS Migration Hub; supplement missing information within Migration Hub; use Amazon QuickSight for querying.
- C) Manually script custom data collection on each server; invoke AWS CLI
put-resource-attributescommands to push collected metadata to AWS Migration Hub; query directly in the Migration Hub console. - D) Install AWS Application Discovery Agent on each server; configure AWS Migration Hub for data exploration; run predefined queries on the collected data stored in Amazon S3 through Amazon Athena.
Correct Answer #
Option D.
Step-by-Step Winning Logic #
Option D leverages the AWS Application Discovery Agent, installed directly on each server, providing detailed and near-real-time metrics on CPU, memory, OS, and running processes. This richness is crucial for accurate assessment of right-sizing and licensing needs, directly impacting migration cost projections and ongoing FinOps metrics.
Using Amazon Athena to query collected data stored on S3 enables flexible, scalable analysis without additional proprietary tooling overhead. The agent’s installation, while adding some operational work, minimizes errors or missing data common with manual or agentless methods.
💎 The Architect’s Deep Dive: Why Options Fail #
The Traps (Distractor Analysis) #
-
Why not Option A?
The AWS Agentless Discovery Connector runs as a virtual appliance, limiting the depth of collected data (especially process-level insight). It may miss some metrics and introduce complexity maintaining a separate appliance, potentially increasing operational cost and migration risk. -
Why not Option B?
Manual export and import of VM data is error-prone, incomplete, and lacks automation. This approach does not scale well for 1000 servers and undermines FinOps by introducing uncertainty in utilization metrics and licensing details. -
Why not Option C?
Writing custom scripts and invoking AWS CLI commands increases operational overhead and risks inconsistencies, making it unsuitable for enterprise-scale migrations where accuracy and maintainability are paramount.
The Architect Blueprint #
graph TD
OnPremServers[On-premises Servers]
AWSDiscoveryAgent[AWS Application Discovery Agent Installed]
MigrationHub[AWS Migration Hub]
S3Bucket["Amazon S3 (Discovery Data Storage)"]
Athena[Amazon Athena - Query Layer]
OnPremServers -->|Agent collects metrics| AWSDiscoveryAgent
AWSDiscoveryAgent -->|Upload detailed data| MigrationHub
MigrationHub -->|Store data| S3Bucket
Athena -->|Run SQL queries| S3Bucket
Diagram Note: The AWS Application Discovery Agent collects detailed server data on-premises, which is uploaded to Migration Hub and stored in S3. Amazon Athena allows flexible querying to analyze server inventory and performance.
The Decision Matrix #
| Option | Estimated Complexity | Estimated Monthly Cost | Pros | Cons |
|---|---|---|---|---|
| A | Medium | Medium ($500-$1000) | Agentless appliance, no server install | Less granular data, operational appliance overhead |
| B | High | Low ($100) | Simple, minimal AWS service use | Manual, incomplete, error-prone |
| C | Very High | Low ($100) | Full control via scripting | Operationally intensive, error-prone |
| D | Medium | Medium-High ($1000-$1500) | Best data completeness, supports FinOps | Agent installation overhead |
Real-World Practitioner Insight #
Exam Rule #
For the AWS SAP-C02 exam, when detailed server metrics and process-level data for large VMware migrations are required, always choose AWS Application Discovery Agent (Option D).