Free AWS SOA-C03 Actual Exam Questions - Question 1 Discussion
A CloudOps engineer is using AWS Compute Optimizer to generate recommendations for a fleet of
Amazon EC2 instances. Some of the instances use newly released instance types, while other
instances use older instance types.
After the analysis is complete, the CloudOps engineer notices that some of the EC2 instances are
missing from the Compute Optimizer dashboard.
What is the likely cause of this issue?
Option A makes sense because without enough CloudWatch data, instances won’t appear in the recommendations.
Maybe B here. Since some instances use brand-new types, Compute Optimizer might not support those yet, so they wouldn’t show up in the dashboard at all. It’s less about data availability and more about compatibility with those newer instance types. This fits since older types appear but the new ones are missing.
Actually, the missing instances probably don’t have enough CloudWatch data yet, so option A makes more sense. Without enough historical metrics, Compute Optimizer can’t analyze them properly.
It’s B because some new or very old instance types might not be supported yet by Compute Optimizer, so they won’t show up in recommendations at all. That seems more likely than just data issues or OS type.
Option A makes sense since without enough historical CloudWatch data, Compute Optimizer can't analyze instances properly, especially new ones that haven't been running long enough. That would explain missing entries on the dashboard.
A imo: I think it’s more about the data than support here. Compute Optimizer needs enough CloudWatch metrics over time to analyze instances properly. New instances, especially if just launched, might not have that historical data yet, so they wouldn’t show up in recommendations. Support for new types usually follows pretty quickly anyway. Also, option D can be ruled out since OS type doesn’t affect Compute Optimizer’s ability to analyze instances. So missing data seems like the main reason some instances don’t appear on the dashboard.
B. I agree with others that new instance types might not be supported by Compute Optimizer yet, which would explain why those instances are missing from the dashboard. Even if the instances have enough CloudWatch data, the service needs to recognize the instance type to provide recommendations. So, it’s more about compatibility than data availability in this case.
A/B? I think both could play a role here. New instance types might not be supported yet by Compute Optimizer, which would explain why some are missing. At the same time, if the instances haven’t been running long enough, there won’t be enough CloudWatch data for analysis, so they wouldn’t show up either. D seems unlikely since OS shouldn't affect visibility here. C doesn’t make much sense because even optimized instances should appear in the dashboard. So it’s probably a combination of limited support for new types and lack of data for recent instances.
D imo, the OS shouldn’t really affect whether an instance appears in Compute Optimizer since it mainly looks at metrics, not the software running on the instance. Plus, Windows instances are generally supported just like Linux ones. So ruling out D makes sense here. Between A and B, A seems plausible if these instances are brand new with not enough data yet, but B fits well too because brand new instance types might not be supported by Compute Optimizer right away. But definitely not D.
Amit V.: A imo, if those instances just started recently, Compute Optimizer can’t analyze them without enough CloudWatch data. So they wouldn't appear in the dashboard yet.
B imo, new instance types often aren’t supported immediately in Compute Optimizer.
Maybe A makes sense too since without enough CloudWatch data, Compute Optimizer can’t analyze those instances, so they wouldn’t show up at all on the dashboard.
Makes sense that B is the answer since AWS services often take time to support brand-new instance types. No data or optimization status wouldn’t explain complete absence like this. So, probably B.
B/C? If some instances were fully optimized, they might not show up as recommendations, but missing support for new instance types (B) feels more likely since some are totally absent.
It’s A, new instances might lack enough CloudWatch data for Compute Optimizer to analyze.
Maybe B. If those missing instances use really new types, Compute Optimizer might just not support them yet, so they wouldn’t show up on the dashboard. A could explain it too, but then you’d expect only the newest instances to be missing, not older ones. So if the missing ones are all new types, that points towards lack of support rather than missing data.
Option A makes sense since new instances might not have enough CloudWatch data yet.
B imo. Since some instances are newer types, it makes sense that Compute Optimizer might not support them yet, which is why they don’t appear. If it was missing CloudWatch data (A), then older instances would be affected too, but only new ones are missing here. Plus, the OS (D) isn’t usually a limiting factor for Compute Optimizer’s analysis. C doesn’t fit either because it wouldn’t just hide instances; it would still show their status.
It’s B, new instance types might not be supported by Compute Optimizer yet.
B. Another angle is that Compute Optimizer doesn’t instantly support every new instance type once they’re launched. So if you have some brand-new instances, they might just not be included because the service hasn’t added support yet. Older types should show up fine, so missing instances are likely the unsupported new ones rather than a data issue. This fits with how AWS rolls out support for new features in phases.