This is a strong question.
I’d look less at whether they can name the tools and more at whether they can explain trade-offs.
For example:
Why this workflow?
Why this sequence?
What breaks if volume doubles?
What would they simplify if the team had no ops maturity?
How do they decide what not to automate?
Paid projects help, but the real signal is not just the output. It is how they diagnose, prioritise, explain constraints and recover when the build is messy.
That usually shows more than a resume or polished interview answer.