AWS Certified Solutions Architect – Professional (SAP-C02) — Question 316

A solutions architect needs to migrate an on-premises legacy application to AWS. The application runs on two servers behind a load balancer. The application requires a license file that is associated with the MAC address of the server's network adapter It takes the software vendor 12 hours to send new license files. The application also uses configuration files with a static IP address to access a database server, host names are not supported.

Given these requirements, which combination of steps should be taken to implement highly available architecture for the application servers in AWS? (Choose two.)

Answer options

• A. Create a pool of ENIs. Request license files from the vendor for the pool, and store the license files in Amazon S3. Create a bootstrap automation script to download a license file and attach the corresponding ENI to an Amazon EC2 instance.
• B. Create a pool of ENIs. Request license files from the vendor for the pool, store the license files on an Amazon EC2 instance. Create an AMI from the instance and use this AMI for all future EC2 instances.
• C. Create a bootstrap automation script to request a new license file from the vendor .When the response is received, apply the license file to an Amazon EC2 instance.
• D. Edit the bootstrap automation script to read the database server IP address from the AWS Systems Manager Parameter Store, and inject the value into the local configuration files.
• E. Edit an Amazon EC2 instance to include the database server IP address in the configuration files and re-create the AMI to use for all future EC2 stances.

Correct answer: A, D

Explanation

To bypass the 12-hour vendor delay for MAC-address-locked licenses, pre-creating a pool of ENIs (which have persistent MAC addresses) and storing their pre-approved licenses in Amazon S3 allows a bootstrap script to dynamically attach an ENI and apply its corresponding license at launch. For the database connectivity, storing the static IP in AWS Systems Manager Parameter Store and injecting it via a bootstrap script avoids hardcoding IPs in the AMI, enabling seamless updates if the database IP changes. Options B, C, and E are incorrect because they either introduce unacceptable downtime during scaling/recovery or rely on hardcoded configurations that break automation.