<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>F5 - Category - Fryguy's Blog</title><link>https://hugo.fryguy.net/categories/f5/</link><description>F5 - Category - Fryguy's Blog</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Fri, 31 May 2013 15:06:35 +0000</lastBuildDate><atom:link href="https://hugo.fryguy.net/categories/f5/" rel="self" type="application/rss+xml"/><item><title>F5 Certifications – F5 Certified Administrator</title><link>https://hugo.fryguy.net/2013/05/31/f5-certifications-f5-certified-administrator/</link><pubDate>Fri, 31 May 2013 15:06:35 +0000</pubDate><author>Fryguy</author><guid>https://hugo.fryguy.net/2013/05/31/f5-certifications-f5-certified-administrator/</guid><description><![CDATA[<p align="center">

</p>
<p align="center">
Ahh, Certifications!  The thing that drives many of us to learn new things as well as show what we have learned.
</p>
<p align="center">
Recently at work there was a request for some of us to get F5 certified and I figured what the heck. I have had some exposure to F5 Load Balancers in the past and have also had some intimate times other vendors products.  So, I figured I would take the time and focus on the F5 product and obtain the certification  I was much more challenging that I thought it would be –  but it was fun!
</p>
<p align="center">
It seems as though F5 recently revamped their certification guidelines, testing procedures, and tests.   I do not know exactly when they started to revamp them, but I know it was recent based on the BIG-IP Certification Administrator going live on 3/18/13.  Based on this, the material available to study is few and far between as well many have not been exposed to the Professional Pearson Vue centeters that F5 users to administer the test.  I will cover the Pearson Professional centers as part of this post and will focus on the required tests (101 and 201) in separate posts.  There is just two much information for one post!
</p>
<p align="center">]]></description></item></channel></rss>