I sat the AWS Certified SysOps Administrator - Associate this morning.   That makes two exams this week in 3 days.

The exam was a little bit harder than the two other Associate exams as it went a level deeper.   It focused on CloudFormation, CloudWatch, and deployment strategies.      There were nine questions I struggled with the right answer, as all nine had two good answers.     There were about 35 questions I knew cold.    There were three questions duplicated on the other associate exams.   All of the network questions I was over-thinking, probably based on the networking exam this week.    Given this, I wasn’t worried when I ended the test.   However,  it’s always a relief when you get the Congratulations! You have successfully completed the AWS Certified SysOps Administrator - Associate.

Within 10 minutes I got my score email:

Congratulations again on your achievement!

Overall Score: 84%

Topic Level Scoring:

The score reflected over thinking the networking questions.    I wouldn’t recommend sitting two different exams in the same few days.

That make 4 AWS certifications in 3 weeks:

• AWS Certified SysOps Administrator - Associate
• AWS Certified Advanced Networking - Specialty
• AWS Certified Developer - Associate
• AWS Certified Solutions Architect - Associate (Released February 2018)

Guess now it’s time to focus on the last of the Amazon Certifications I’ll work on for now which is the  AWS Certified Solutions Architect – Professional.

Is DevOps the most overused word in technology right now?

The full definition from Wikipedia.  Here what DevOps really is about.   It about taking monolithic code with complex infrastructure supported by developers, operational personnel, testers, system administrators and simplifying it, monitoring it and taking automated corrective actions or notification.

It’s really about reducing resources who aren’t helping the business grow and using that headcount toward a position which can help revenue growth.

It’s done in 3 pieces.

Piece 1. The Infrastructure

It starts by simplifying the infrastructure build-out, whether it in the cloud where environments can be spun up and down instantly based on some known configuration like AWS CloudFormation,  using Docker or Kubernettes.   Recently, Function as a Service (FaaS), AWS Lambda,  Google Cloud Functions or Azure Functions. This reduces reliance on a DBA, Unix or Windows System Administrator and Network Engineers.   Now the developer has the space they need instantly.   The developer can deploy their code quicker, which speeds time to market.

Piece 2.  Re-use and Buy vs. Build

Piece 2 of this is the Re-use and Buy vs. Build.   Meaning if someone has a service re-use it, don’t go building your own.    An example is Auth0 for authentication and Google Maps for mapping locations or directions.

Piece 3.  When building or creating software do it as Microservices.

To simplify it you are going to implement microservices.   Basically, you create code that does one thing well.  It’s small, efficient and manageable.    It outputs JSON which can be parsed by upstream Services.   The JSON can extend without causing issues to upstream Services.   This now reduces the size of the code base a developer is touching, as it one service.   It reduces regression testing footprint.      So now the number of testers, unit tests, regression tests and integration tests have been shrunk.   This means faster releases to production, and also means a reduction in resources.

You’re not doing DevOps if any of these conditions apply?

1. You have monolithic software you’ve put some web services in front of.

2. Developers are still asking to provision environments to work.

3. People are still doing capacity planning and analysis.

4. NewRelic (or any other system)  is monitoring the environment, but no one is aware of what is happening.

5. Production pushes happen at most once a month because of the effort and amount of things which break.

Doing DevOps

1. Take the monolithic software and break it into web services.

2. Developers can provision environments per a Service Catalog as required.

3. Automate capacity analysis.

4. Automatic SLAs which trigger notifications and tickets.

5. NewRelic is monitoring the environment, and it providing data to systems which are self-correcting issues, and there are feedback loops on releases.

6. Consistently (multiple times a week)  pushing to production to enhance the customer experience.

The material for the AWS Certified SysOps Administrator – Associate seems to be a lot of the material cover under the Associate Architect and Associate Developer.   I would have thought the material more focus on setting up and troubleshooting issues with EC2, RDS, ELB, VPC etc.    It also spends a lot of time looking at CloudWatch, but doesn’t really provide strategies for leveraging the logs.  Studying was a combination of the acloud.guru and the official study guide, and the Amazon Whitepapers.

I took the AWS supplied practice test using a free test voucher and score the following:

It interesting the networking score was so low as I just passed the Network Speciality.

This is the last Associate exam to pass for me.    If I successfully pass it, I will begin the process of studying for the Certified Solution Architect - Professional.    That will probably be my last AWS certification as I’ll look at either starting on something like  TOGAF certification,  Redhat or Linux Institute, Cisco, GCP  or Azure, depending on where my interest lies in a few weeks.

I passed the AWS Certified Advanced Networking – Specialty Exam this morning.    The exam is hard.   My career started with a  networking as I had multiple Nortel and Cisco Certifications and was studying to the CCIE Lab back then.  But over the last 12 years,  I got away from networking.    Doing this exam was going back to something I loved for a long time, as  BGP, Networking, Load Balancers, WAF makes me excited.

My exam results

Topic Level Scoring:
1.0  Design and implement hybrid IT network architectures at scale: 75%
2.0  Design and implement AWS networks: 57%
3.0  Automate AWS tasks: 100%
4.0  Configure network integration with application services: 85%
5.0  Design and implement for security and compliance: 83%
6.0  Manage, optimize, and troubleshoot the network: 57%

I have limited experience with AWS networking prior to this exam.   I had the standard things likes load balancers, VPCs, Elastic IPs and Route 53.   This exam tests your knowledge of these areas and more.      To prepare I used the acloud.guru course, also the book  AWS Certified Advanced Networking Official Study Guide: Specialty Exam and the Udemy Practice Tests.    With the course and book, I set up VPC peers, Endpoints, nat instances, gateways, CloudFront distributions.    I put about 50 hours into doing the course, reading the book, doing various exercise, and studying etc.

Based on my experience the acloud.guru course is lacking the details on the ELBs, the WAF, private DNS, and implementation within CloudFormation.     The book comes closer to the exam, but also doesn’t cover CloudFormation, WAF or ELBs as deep as the exam.   The Udemy practice tests were close to the exam, but lack some of the more complex scenario questions.

I plan to sit the AWS Certified SysOps Administrator - Associate exam later this week.

What’s up with interviewers asking about kubernetes experience lately?   Two different interviewers raised the question today.

Kubernetes Is only 4 years old .   GCP has supported it for a while. AWS released it in beta at Re:invent 2017 and it went general release June 5 2018.   Azure went GA June 13, 2018.

So how widely deployed is it?     Also if it is supposed to speed deployments, how complex can it be?   How many hours to learn it?

Next week I will be learning it.  Looking forward to answering these questions.

The pdf provided this:

The AWS Certified Solutions Architect - Associate (Released February 2018) (SAA-C01) has a scaled score between 100 and 1,000. The scaled score needed to pass the exam is 720.

I got a 932….