Your company has recently extended its datacenter into a VPC on AVVS to add burst computing capacity as needed Members of your Network Operations Center need to be able to go to the AWSManagement Console and administer Amazon EC2 instances as necessary You don't want to create new lAM users for each NOC member and make those users sign in again to the AWS Management Console Which option below will meet the needs for your NOC members?

Your company has recently extended its datacenter into a VPC on AVVS to add burst computing capacity as needed Members of your Network Operations Center need to be able to go to the AWSManagement Console and administer Amazon EC2 instances as necessary You don’t want to create new lAM users for each NOC member and make those users sign in again to the AWS Management Console Which option below will meet the needs for your NOC members?

Your company has recently extended its datacenter into a VPC on AVVS to add burst computing capacity as needed Members of your Network Operations Center need to be able to go to the AWSManagement Console and administer Amazon EC2 instances as necessary You don’t want to create new lAM users for each NOC member and make those users sign in again to the AWS Management Console Which option below will meet the needs for your NOC members?
A . Use OAuth 2 0 to retrieve temporary AWS security credentials to enable your NOC members to sign in to the AVVS Management Console.
B . Use web Identity Federation to retrieve AWS temporary security credentials to enable your NOC members to sign in to the AWS Management Console.
C . Use your on-premises SAML 2.0-compliant identity provider (lOP) to grant the NOC members federated access to the AWS Management Console via the AWS sing le sign-on (550) endpoint.
D . Use your on-premises SAML2.0-compliam identity provider (lOP) to retrieve temporary security credentials to enable NOC members to sign in to the AWS Management Console.

Answer: D