You are in charge of migrating a legacy application from your company datacenters to GCP before the current maintenance contract expires. You do not know what ports the application is using and no…

Question

Options

• AMigrate the application into an isolated project using a "Lift & Shift" approach. Enable all internal
• BMigrate the application into an isolated project using a "Lift & Shift" approach in a custom
• CRefactor the application into a micro-services architecture in a GKE cluster. Disable all traffic from
• DRefactor the application into a micro-services architecture hosted in Cloud Functions in an

• A
  72% (36)
• B
  8% (4)
• C
  16% (8)
• D
  4% (2)

Explanation

When you do not know what ports a legacy application uses and documentation is unavailable, the safest approach is to perform a Lift & Shift migration into an isolated GCP project and enable all internal traffic within that isolated environment. Isolation limits blast radius - any security issues are contained within the project. Enabling all internal traffic temporarily allows the application to function while you discover the actual ports in use through monitoring (e.g., VPC Flow Logs), after which you can lock down firewall rules. Refactoring (Options C and D) requires understanding the application's internals, which is not possible without documentation, and introduces additional risk and effort.

No community discussion yet for this question.