SAP-C02 · Question #581
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…
The correct answer is A. Create a pool of ENIs. Request license files from the vendor for the pool, and store the license D. Edit the bootstrap automation script to read the database server IP address from the AWS. To make a legacy application highly available in AWS with MAC-address-tied licenses and static DB IP configurations, pre-provisioning licenses for a pool of ENIs and dynamically configuring the DB IP via automation are necessary.
Question
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.)
Options
- ACreate a pool of ENIs. Request license files from the vendor for the pool, and store the license
- BCreate a pool of ENIs. Request license files from the vendor for the pool, store the license files on
- CCreate a bootstrap automation script to request a new license file from the vendor .When the
- DEdit the bootstrap automation script to read the database server IP address from the AWS
- EEdit an Amazon EC2 instance to include the database server IP address in the configuration files
How the community answered
(62 responses)- A66% (41)
- B19% (12)
- C10% (6)
- E5% (3)
Why each option
To make a legacy application highly available in AWS with MAC-address-tied licenses and static DB IP configurations, pre-provisioning licenses for a pool of ENIs and dynamically configuring the DB IP via automation are necessary.
Creating a pool of Elastic Network Interfaces (ENIs) with requested licenses tied to their static MAC addresses allows new EC2 instances to attach a pre-licensed ENI upon launch, providing high availability without waiting 12 hours for a new license.
While creating a pool of ENIs is correct, storing license files 'on' ENIs is technically inaccurate; licenses are tied to the ENI's MAC address, and the file itself would typically be on the instance's storage or an attached EBS volume.
Creating a bootstrap script to request new licenses on demand would introduce a 12-hour delay for every new instance, making the solution not highly available for rapid recovery or scaling.
Editing the bootstrap automation script to read the database server IP address from an AWS service (like Systems Manager Parameter Store) ensures that newly launched EC2 instances can automatically retrieve and configure the static DB IP, making the architecture highly available and scalable.
Manually editing EC2 instance configuration files with the database server IP address does not support high availability or automation, as instances are ephemeral and manual intervention would be required upon replacement.
Concept tested: Migrating Legacy Applications (MAC-tied licenses, Static IP config, HA)
Source: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html
Community Discussion
No community discussion yet for this question.