A large university has adopted a strategic goal of increasing diversity among enrolled students. The data analytics team is creating a dashboard with data visualizations to enable stakeholders to…

Question

Options

• AAmazon QuickSight Standard edition configured to perform identity federation using SAML 2.0.
• BAmazon QuickSight Enterprise edition configured to perform identity federation using SAML 2.0
• CAmazon QuckSight Standard edition using AD Connector to authenticate using Active Directory.
• DAmazon QuickSight Enterprise edition using AD Connector to authenticate using Active Directory.

• A
  3% (1)
• B
  83% (25)
• C
  3% (1)
• D
  10% (3)

Explanation

Two requirements eliminate most options: (1) Microsoft Active Directory authentication via federation, and (2) encryption of all data at rest and in transit. Encryption at rest for QuickSight data (SPICE) is only available in the Enterprise edition-Standard edition does not support it, ruling out A and C. For Active Directory federation, SAML 2.0 is the correct mechanism for integrating an external IdP (Microsoft AD via AD FS) with QuickSight. AD Connector (choices C/D) is an AWS Directory Service proxy that redirects authentication requests to on-premises AD; while it can be used with QuickSight Enterprise, SAML 2.0 federation is the more standard and flexible approach for external identity providers. Enterprise edition with SAML 2.0 satisfies both the encryption-at-rest and federated authentication requirements.

No community discussion yet for this question.