You are looking for a dynamic, runtime, solution because like you wrote a static analyzer can only go so far.
A good solution, but not 100% accurate (*), could be mutation testing combined with a dynamic code coverage tool. Descartes: A Mutation Engine for PIT is such a solution but it is Java only and might not work well in high performance systems.
When you say "dead code" you are meaning unreachable code or simply code not covered by your automated checks?
For the first case, your compiler usually already indicates such blocks of code. Most text editors do it on the fly.
For the second case, most code coverage analysis tools indicate uncovered code by highlighting it. Since most tools also ...
there is a way named MECE(Mutual Exclusive and Collectively Exhaustive )
To cover all the test scenario as more as possible , you need a thinking map.
for example, ISO9000 quality standard
it has 6 big-categories, and 24 sub-categories under that.
take your login page for example:
can we login with correct username and password
can we not able to login ...
I like to answers questions with questions during interviews.
My first response would be that the question "How to test AWS?" is very broad.
My first question would be: Which part of AWS should I test?
As of 2020, AWS comprises more than 175 products and services
including computing, storage, networking, database, analytics,
application services, ...