Indeed. My last onsite with apple concluded with a couple hours of grilling on how to write performant synchronization primitives on various real architectures. I was not interviewing for the relevant teams.
I know its Apple but I'd definitely be prepared to walk out. In that situation that gives you the freedom to clarify the job description -- if they say it is in the description, I'd save everyone time and say I don't have that knowledge, thank them for their time, and wish them luck on their next n months of searching for their unicorn.
If it isn't, I'd probably go full stick-in-the-mud and explain that I could find the answers to those questions but it would be a waste of everyone's time: I'm an A player and I don't focus on irrelevant things that dilute abilities and ultimately the product (basically throw Steve Jobs at them).
Your strategy would be an epic failure for me. Granted, nearly any strategy would be.