A SysOps Administrator needs to schedule a weekly task that runs a custom configuration script on a fleet of Amazon EC2 instances by using an AWS Systems Manager Automation document. The EC2 instances are tagged with the key `Env` and the value `Production`. The instances have the SSM Agent installed and running, and they are associated with an IAM instance profile containing the `AmazonSSMManagedInstanceCore` managed policy.
The Administrator is using a custom IAM service role named `SSMAutomationServiceRole` to allow Systems Manager to execute the Automation workflow. However, when the Administrator attempts to run the Automation using their own IAM user account, the execution fails with an access denied error. What combination of steps must the Administrator perform to execute the Automation and target the correct instances? (Select TWO.)
- Add a policy to the SysOps Administrator's IAM user that grants the `iam:PassRole` permission for the `SSMAutomationServiceRole` ARN.Cevap
- Define the targets for the Automation execution by specifying resource tags with the key `Env` and the value `Production`.Cevap
- CConfigure the trust policy of the `SSMAutomationServiceRole` to allow the SysOps Administrator's IAM user to perform the `sts:AssumeRole` action.
- DAssign a resource tag with the key `Patch Group` and value `Production` to the target instances, and configure the Automation document to execute against the patch group.
- EEnable the SysOps Administrator's IAM user to assume the EC2 instance profile role by granting the `sts:AssumeRole` permission on the instances.