{"id":147,"date":"2018-11-17T22:58:04","date_gmt":"2018-11-17T22:58:04","guid":{"rendered":"https:\/\/nillsf.wordpress.com\/?p=147"},"modified":"2018-11-17T22:58:04","modified_gmt":"2018-11-17T22:58:04","slug":"i-failed-the-lfce-exam","status":"publish","type":"post","link":"https:\/\/blog.nillsf.com\/index.php\/2018\/11\/17\/i-failed-the-lfce-exam\/","title":{"rendered":"I failed the LFCE exam"},"content":{"rendered":"

Yesterday, I took the\u00a0LFCE exam<\/a>\u00a0(Linux Foundation Certified Engineer). My LFCS (Linux Foundation Certified SysAdmin) is expiring, and rather than redoing an exam I did two years ago, I decided to study and take the LFCE exam. Although I still need to wait 3 business day for the actual results, I am fairly certain I failed.
\nWith the perspective of growth mindset – I thought I’d share my experience with the exam. While studying, I found there wasn’t a lot of tribal knowledge I could find about this exam – and although my trial was a failure, I hope you’ll learn something from my experience. In sharing this, I mean to respect the NDA of the exam. If you believe I am sharing things I am not allowed to share, please let me know and I’ll adapt.<\/p>\n

My background walking into the exam<\/span><\/h2>\n

Although my desktop is a Windows 10 machine, I do roughly 80% of my server work on Linux. I achieved the LFCS certification about 2 years ago to complete my MCSA Linux on Azure – and I complemented that with the CKA Kubernetes certification this June.
\nIn terms of study material I did what I usually do: I make a list of all exam objectives and try to find relevant info online and make a personal list of commands to achieve the goals of that objective. For the LFCE, I complemted this approach with the TecMint guide for the LFCE<\/a> and some video training on LinkedIn Learning<\/a>.
\nAll in all, I believe I spent a couple hours a week for 6 weeks studying for this exam. I didn’t carve out big blocks of time – I tried to cover 1 technology aspect per evening\/down hour I spent studying.
\nAbout the exam itself<\/span>
\nThe exam itself takes 2 hours and is all console based. You take this exam from your own computer in your own space – I took it from a quiet meeting room at the office. On the exam, I got access to a master node and then some specific nodes for specific questions. All of this is perfectly configured, you can ssh to each node from the master node and you can reboot each node separately. The master node itself though isn’t supposed to be rebooted. Some nodes are used for multiple questions, so try not to kill your nodes (as I did in my first take of the LFCS exam).
\nDuring the exam, you’re only allowed to have the exam tab open with no programs (such as a text editor even). I like using the notepad of the exam environment to take notes of the questions, draft my shell commands\/config files which I then copy paste in and also to take note of questions I skipped and wish to revisit.
\nI got a total of 28 questions during the 2 hours of the exam; which meant I could roughly spend 4 minutes per question. Different questions have different weights – so you should figure out for yourself if some questions are worth spending the time on. I feel confident that I would have passed the exam if I would have had 4 hours – 28 questions in 4 hours doesn’t allow for enough time to browse MAN pages. I realized after my first 5 questions that this exam was a lost cause, I needed more training.
\nSome questions were relatively straightforward if you knew which config file to adapt – while others took a broader approach where you needed to install the relevant software and then figure out all the config file you need to write\/adapt.
\nI did the exam with the Ubuntu distribution, which is my go-to distro. You have the choice between Ubuntu, Suse or Centos for taking the exam. I assume the actual questions don’t differ at all – as at some points during the exam it was pointed out that services had a particular name in a certain distribution.
\nHow I plan to rectify<\/span>
\nI am not planning to re-take this exam very soon. I have a deadline on December 8th to refresh my LFCS – and I believe I’ll be able to study for the LFCE in the remaining time. I will re-take my LFCS very soon – as I don’t want to lose my MCSA Linux on Azure.
\nI do plan to retake this exam early next year, as I did enjoy the challenge – both of studying as of the exam itself. In the meantime, I’ll spend more time studying particular systems. I spent very little to no time on certain objective likes containers (I know Docker and I know Kubernetes) and was surprised to find LXC questions.
\nSpecific topics that I neglected in studying were PAM, LDAP, containers, software packages (you need more than apt-get install and apt-cache search apparently), iptables (I always used UFW), kernel updates\u2026
\nConclusion<\/span>
\nThe LFCE was definitely a hard exam. Time constraints meant you really need to have the relevant commands in the tips of your fingers – and you need to know where the configs files are stored to have enough time to finish all the questions. Although you have full access to man pages – if you need them too often, you’ll simply run out of time.
\nI will certainly retry the exam – but will first retake the LFCS to maintain my certification status.
\nIf you plan on taking it, good luck!<\/p>\n","protected":false},"excerpt":{"rendered":"

Yesterday, I took the\u00a0LFCE exam\u00a0(Linux Foundation Certified Engineer). My LFCS (Linux Foundation Certified SysAdmin) is expiring, and rather than redoing an exam I did two years ago, I decided to study and take the LFCE exam. Although I still need to wait 3 business day for the actual results, I am fairly certain I failed. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-147","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/147","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/comments?post=147"}],"version-history":[{"count":0,"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/posts\/147\/revisions"}],"wp:attachment":[{"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/media?parent=147"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/categories?post=147"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.nillsf.com\/index.php\/wp-json\/wp\/v2\/tags?post=147"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}