Yeah - those are good; I've asked variants of those and others when I've interviewed. It's interesting; you sometimes get these incredulous looks (may be a red flag), other times they look surprised but launch into describing their process, failures, places to improve, etc. Sometimes this discussion can also be a means for me as a candidate to decide if I want to work there (ie - is it a broken environment where I might become the fall guy or it will cause me heartache in the long term). Sometimes it leads to more interesting tech discussion and such.
* Version control - what kind do you use? Do you use it?
* Deploy process - how do you deploy? How often? Who can and can't deploy?
* Security - who has access to mission critical systems? how do you secure your apps and network assets? What do you use for secrets management?
* Problems - what is the burning technical problem you're having right now? If you needed something fixed immediately, what would it be?