I've been doing this for over a decade and i like to think I'm pretty good since I pass most technical assessments of the style you're putting forth. There is no way I could confidently answer either of those questions.
I'm general web developer. Rate limiting is plumbing to me. I don't tweak or read the cose that makes it up. I just configure it. I could take a decent swing, but effectively i have zero experience in such a thing.
CORS is one of those things that i know implicitly, but ask me explicitly about it and I'll probably fall on my face. You'd need to remind me what it's made up of and then I'd go, oh yeah blah blah blah. A company asked me about SOLID in this way. That's just the way I code. It's instinctual. Asking me to tell me about it without explaining each letter was pulling teeth because it was so baked in I never even thought about it that way before. CORS is likely the same way for many experienced people. You're doing it because it feels right. You could justify the action and configuration, but you don't have the idea CORS in your mind even if that's what you're doing.
So yeah, your questions are a touch ridiculous frol my POV. I'll tell you two interviews i enjoyed a lot. One was an absolutely broken codebase. It was filled with every novice mistake possible and it didn't even compile. The goal was to fix as many bugs as possible in an hour. I loved it. They were right that because of the sheer number of bugs, you'd naturally focus on the parts of the stack you were strongest and that's how they sussed out that I'm strongest middle layer and as we tend away from that I get weaker. If i ever test a full stack developer and care about language a lot, I'll do this.
Second was a question that was worked ambiguously and left out small requirements. Your goal was make all 100 tests pass. Taking the problem at face value got you 50 of them. It was for a consulting position, so it made sense. I was so delighted by the failed tests coming back with a consumer complaint that wasn't even in the original ask. It was very charming to me. I laughed about it, although I saw people hated it a lot on glassdoor. I do think it's a good test of an engineer's ability to keep shifting and many many requirements in mind.