I was a sysadmin, a devops engineer, and a build/release engineer. Now a developer.
These questions are all decent. There's nothing here that would be out of the question to ask in a junior interview.
Usually for junior interviews, they want to see if you understand the fundamentals and not advanced details that a senior might need to know.
One example of this is the question "What is swap and what is it used for?"
For an intern, I'd ask if they knew what it was for.
For a junior, I'd add questions about any ways to control swap.
For a midlevel/normal, I'd add scenario questions about configuring swap and the performance effects it can have.
For a senior, I'd add troubleshooting questions.
To be honest though, I've only ever been asked the base question in interviews. I'm guessing that my answer sounded confident enough that the interviewer determined that it would be more worthwhile to explore areas I was not so strong in to see how I problem solve/deal with foreign scenarios.
Most decent interviews understand that people have different levels of understanding for different topics which might fall under the umbrella of "DevOps". A candidate could be a docker wizard, knowing all of the best practices of versioning, CI, and deployment, but could not know much about VLANs because "they never had to use it".
Keep in mind that most companies use a certain tech stack and are usually looking for people familiar with it. Interviewers always seem to be impressed when I told them I "checked it out over the weekend" and was able to answer questions decently about their stack. Skimming the documentation, setting up a vm to play around with, and finding the most popular blog posts about current best practices for a technology can go a long way towards closing the gap between your current knowledge and the ideal candidate's knowledge.
These questions are all decent. There's nothing here that would be out of the question to ask in a junior interview.
Usually for junior interviews, they want to see if you understand the fundamentals and not advanced details that a senior might need to know.
One example of this is the question "What is swap and what is it used for?"
For an intern, I'd ask if they knew what it was for. For a junior, I'd add questions about any ways to control swap. For a midlevel/normal, I'd add scenario questions about configuring swap and the performance effects it can have. For a senior, I'd add troubleshooting questions.
To be honest though, I've only ever been asked the base question in interviews. I'm guessing that my answer sounded confident enough that the interviewer determined that it would be more worthwhile to explore areas I was not so strong in to see how I problem solve/deal with foreign scenarios.
Most decent interviews understand that people have different levels of understanding for different topics which might fall under the umbrella of "DevOps". A candidate could be a docker wizard, knowing all of the best practices of versioning, CI, and deployment, but could not know much about VLANs because "they never had to use it".
Keep in mind that most companies use a certain tech stack and are usually looking for people familiar with it. Interviewers always seem to be impressed when I told them I "checked it out over the weekend" and was able to answer questions decently about their stack. Skimming the documentation, setting up a vm to play around with, and finding the most popular blog posts about current best practices for a technology can go a long way towards closing the gap between your current knowledge and the ideal candidate's knowledge.
Hope that helps.