SAP-C02 Practice Question 50: Directory Dependent App Migration
AWS Certified Solutions Architect – Professional (SAP-C02) · Test 5 · question 10 of 10
A utility is migrating a suite of .NET and SQL Server applications to Amazon EC2. The applications authenticate users with Kerberos and read group membership from the company's on-premises Microsoft Active Directory, and the EC2 instances must be domain-joined so that the applications keep working unchanged.
The identity team insists that user accounts stay in the on-premises directory, which remains the authoritative source. The infrastructure team has two further constraints: authentication for the AWS-hosted applications must keep working if the AWS Direct Connect link to the data centre is down for several hours, and nobody wants to patch or monitor domain controllers running on EC2.
What should the solutions architect recommend?
Show answer and explanation
Answer:
AWS Managed Microsoft AD runs actual Microsoft Active Directory as a managed service, creating a highly available pair of domain controllers across different Availability Zones in the VPC, with AWS handling host monitoring, recovery, replication, snapshots, and software updates, which satisfies the "nobody patches domain controllers" constraint. It is the option AWS recommends for running directory-aware workloads such as custom .NET and SQL Server based applications. The trust relationship is what keeps the on-premises directory authoritative: the AWS directory acts as a resource forest for the AWS-hosted resources while user identities stay in the existing domains, and users reach AWS resources with their existing credentials. Because the domain controllers for the resource forest live in the VPC, domain-joined instances authenticate locally and keep working while the Direct Connect link is down.
Option A produces the right authentication behaviour but is entirely self-managed. The utility now owns patching, monitoring, backup, and replication of two domain controllers on EC2, the operational burden the infrastructure team explicitly rejected.
Option B is a proxy, not a directory. AD Connector forwards every authentication request to the on-premises domain controllers, so an outage of the Direct Connect link stops authentication for the AWS-hosted applications, which fails the stated constraint directly.
Option D is a Samba-based directory that does not support trust relationships with an existing Active Directory, so the on-premises directory cannot remain authoritative, and it lacks the schema and features that .NET and SQL Server workloads expect.
Reference: AWS Managed Microsoft AD