Handling “dead” (double-spent) transactions in my mempool

Question

Say I receive transaction A and it is in my node's mempool and unconfirmed.

Then a block gets mined directly, which spends one of transaction A's inputs, rendering transaction A invalid.

What can I expect my node to respond with, when I ask: getrawtransaction <transaction A's txid>?

Answer 1

A will be kicked out of the mempool when that block is received, and getrawtransaction will subsequently fail for it.