These questions are the kind an interviewer asks to check you understand Jira's moving parts before going deeper. They are original scenarios, not questions from any company's interview.
Answer each one the way you would out loud: name the concept, say what it controls, and add the trap you would check. A good short answer often has three parts: what it is, how it differs from the thing people confuse it with, and what you would test. The explanations after each answer give that shape.
Easy does not mean trivial. Many failed changes in real sites start with one of these basics: a board that hides a status, a search that drops blanks, a filter shared without browse rights.
Explain Jira basics clearly and name the trap behind each.