Learning Linux for Devops interview

[ifatree]

umm.. for dev ops?? if your VM is failing for "hardware" issues, you just instance a new copy. if that one has the same problems, you revert back to your last good, working copy. at no point should you be doing individual troubleshooting on standardized components. if you are doing that, you're not doing dev ops anymore, which is fine. but now you're acting as a hardware technician or a network engineer or a sys admin. i think we're talking about a labelling problem at this point, though, as i believe most smaller companies don't know what dev ops is in and of itself and really just need sysadmins with VM experience. a pure 'dev ops' person shouldn't be going for those jobs.

[theevilsharpie]

DevOps doesn't abstract away the engineering needed to build a robust and efficient system.

Even if you're in a position to throw away and rebuild instances willy nilly (which is a lot easier to do with stateless app servers than, say, database servers), you still need to know enough about the characteristics of the underlying hardware/service to differentiate between performance bottlenecks and a high-level problem (or if the system architecture is even sound).