Your company plans to host its development, test, and production applications on EC2 Instances in AWS. The team is worried about how access control would be given to relevant IT Admins for each of the above environments. As an architect, what would you suggest to manage the relevant accesses?

Answer options:

A.Add tags to the instances marking each environment and then segregate access using IAM Policies.
B.Add Userdata to the underlying instances to mark each environment.
C.Add Metadata to the underlying instances to mark each environment.
D.Add each environment to a separate Auto Scaling Group.

Correct Answer - A
AWS Documentation mentions the following to support this requirement.
Tags enable you to categorize your AWS resources differently, for example, by purpose, owner, or environment. This is useful when you have many resources of the same type — you can quickly identify a specific resource based on the tags you`ve assigned to it.
Each tag consists of a key and an optional value, both of which you define. For example, you could define a set of tags for your account`s Amazon EC2 instances that help you track each instance`s owner and stack level.
We recommend you to devise a set of tag keys that will meet your needs for each resource type. Using a consistent set of tag keys makes it easier for you to manage your resources. You can search and filter the resources based on the tags you add.
For more information on using tags, please visit the link below.
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html