An application migration assessment for a permitting system finds hard-coded IP addresses to an on-premises file server and a legacy license host, blocking a clean early rehost. What should the assessment outcome emphasize?
Select an answer to reveal the explanation.
Short Explanation
Hard-coded IPs are tripwires. Call them blockers, fix DNS or config, and sequence the dependency—don’t assume Elastic IPs will magically keep the old street addresses alive.
Full Explanation
Application migration assessments must surface blockers such as hard-coded IP dependencies that break when networks change. Remediation via DNS, configuration externalization, or dependency sequencing should precede early rehost. Assuming Elastic IPs preserve all literals or treating IP hardcoding as cosmetic understates cutover risk.