Free AWS SOA-C03 Actual Exam Questions - Question 7 Discussion

D imo, because deploying an EC2 instance profile with the right IAM policy via a CloudFormation stack set ensures all instances have the correct permissions, both current and future. Quick Setup might help with new setups, but it’s not clear if it updates existing instance roles automatically. Also, option B’s approach with Run Command feels a bit manual and scattered compared to D’s centralized deployment. Using a stack set for the instance profile seems cleaner and more scalable across multiple accounts in the organization.

Option C seems solid because using a CloudFormation stack set allows you to centrally deploy and update the necessary Systems Manager roles across all accounts, covering both current and future EC2 instances. Unlike Quick Setup, which might focus more on configuration than role management, this approach ensures the right parameter and role are consistently applied everywhere. Also, it scales well as new accounts or instances are added since the stack set can be redeployed or updated easily from the management account.

Maybe B makes sense here since it’s about attaching the right IAM policy to every instance role via Run Command, which should cover both current and future instances. It seems more direct than A, which might just set up configs but not fix existing role permissions. C and D use CloudFormation stack sets, but B’s approach with Run Command might be easier to apply across all accounts quickly without redeploying stacks or instance profiles. This way, you ensure all instance roles across the org have the proper permissions for Systems Manager management.

A Quick Setup in the management account is built exactly for this kind of centralized Systems Manager configuration across all accounts, so it should handle both current and future instances well without extra manual steps.

A/D? Quick Setup (A) can automate config across accounts, but it’s unclear if it updates instance roles already attached. D uses stack sets to attach proper IAM policies via instance profiles, which directly handles permissions needed for SSM.

Maybe A, since Quick Setup is designed to manage Systems Manager across all accounts automatically.

I’m not sure about B either since Run Command can’t directly modify IAM roles or instance profiles—it’s more about running commands inside instances. A might work if Quick Setup updates the roles and instance profiles, but that’s kind of unclear for existing instances. D seems practical because the CloudFormation stack set can enforce the right instance profile across all accounts, so every EC2 gets the proper permissions automatically. C looks off since a parameter alone won’t set up roles or profiles. Does anyone know if Quick Setup really handles role updates on existing instances or just n

It’s D because deploying a stack set with an instance profile ensures all EC2 instances across accounts have the right SSM permissions, covering current and future instances without relying on manual role changes.

I don’t think B works because attaching IAM policies via Run Command doesn’t update instance profiles, so it won’t fully manage instances. D looks solid since it ensures all EC2 roles get the right policy through the stack set. D

Option A seems best because Quick Setup handles permissions and configuration automatically across all accounts and regions, covering current and future instances without manual role updates.

B imo since Run Command can directly update roles on all instances, covering current ones better.

A Quick Setup is designed to automate permissions and management across all accounts, covering current and future instances.

A, because Quick Setup covers all accounts and keeps future instances managed too.

It’s D because attaching the right IAM policy via stack sets ensures all instances can be managed by SSM.

A imo, Quick Setup covers new instances automatically without extra role tweaks.

A Quick Setup also ensures consistent config across accounts, which stack sets might miss.

A Quick Setup automates configuration across accounts and regions, which fits managing both current and future instances without manual role changes. B needs extra manual steps that might miss instances.

B tbh, because just setting up Quick Setup (A) doesn’t guarantee the EC2 instances have the proper IAM roles attached. Without the right permissions, Systems Manager can’t manage those instances. Running a Run Command to attach the AmazonSSMServiceRolePolicy to all IAM roles used by EC2 instances across accounts ensures the instances actually have permissions to communicate with Systems Manager. This approach directly fixes the role issue, which Quick Setup alone might miss. So B seems more thorough in making sure both current and future instances are manageable via Systems Manager.

It’s A because Quick Setup simplifies org-wide management without manual role tweaking.

It’s A because Quick Setup automatically configures Systems Manager across the organization, covering all instances now and in future accounts without extra manual steps, unlike stack sets which need updates later.