Quick Answer

The answer is rehost, as this lift-and-shift migration strategy is the correct choice for an SAP system with a custom kernel because it preserves the existing kernel binaries and configuration without requiring recompilation or platform changes. When you rehost a custom kernel, you avoid the risks of incompatibility or performance degradation that could arise from replatforming to a different operating system or database version, which is critical when strict latency requirements mandate that application servers remain in the same AWS region as the database. On the AWS Certified SAP on AWS Specialty PAS-C01 exam, this question tests your understanding that rehost is the only strategy that keeps the custom kernel untouched, while replatform, refactor, or repurchase would introduce unnecessary changes or software replacement. A common trap is assuming replatform is safer, but remember: custom kernels are tightly coupled to their original environment, so any platform shift can break them. Memory tip: “Custom kernel? Keep it local—rehost, don’t roast.”