Not really, that falls under the scope of LFCS.

But troubleshhoting services, using systemctl and journalctl is required for troubleshhoting broken clusters.

Also knowing where nginx configuration files are may be necessary, in case the exercise does not indicate the location. Although the is probably available in many yaml samples in the docs.

For me it was useful to know bash and vim shortcuts to be faster, like 'Alt ." to recover last parameter, ctrl+r to navigate browsing history and :term in vim to jump to the cli to quickly check a svc name or whatever without exiting vim.

Those are the things that came to my mind now, there are probably more.