‫Okay, so we are almost done
‫but we are going to review the exam
‫and I'm going to give you tips
‫and then there's going to be a practice exam for you.
‫Overall congratulations on getting this far.
‫Let's just see where we are today.
‫So I wanna do a checkpoint.
‫I wanna see how far we've been on learning journey
‫and I wanna check back against
‫the requirements of the developer exam
‫because it's important to understand
‫that we have indeed covered everything.
‫So let's do this right now.
‫So on the URL of the AWS certified developer,
‫currently there are two exams to take
‫but we are preparing for the newer exam,
‫which is the Certified Developer released in June 2018.
‫This one, the other one can be taken
‫up until November 19th,
‫but we haven't been preparing for it.
‫We've been preparing for the newer exam.
‫So you can look at this page.
‫It has a lot of good information.
‫As you can see there's a practice exam you can use
‫but there's no symbol questions just yet
‫available for this exam.
‫There's a bunch of whitepapers.
‫I'll be discussing those really
‫but you should read a little bit about them.
‫Skim through them.
‫We've been covering all the content
‫in these whitepapers overall.
‫Now we can look at the exam fee, et cetera.
‫But what I want to look at,
‫more importantly, is the requirements of the exam
‫and what we've been acquiring so far.
‫So this exam will judge your ability
‫to understand the core services,
‫the use and the basics
‫of the AWS architecture best practices.
‫I think in this course we have explored
‫a lot of different architectures.
‫We've then explored traditional architectures with EC2,
‫but also less traditional architecture using serverless.
‫So we're fine.
‫We've also developed, deployed and debugged
‫a bunch of cloud-based applications in AWS.
‫We've learned the functions EC2,
‫Elastic Beanstalk and we've set up some CICD pipelines.
‫So overall, you should have now the ability
‫to validate these two core points.
‫Now there's some recommended AWS knowledge
‫and all this list is pretty big
‫but I believe we've also covered it.
‫The one thing that I can't guarantee you have
‫is one or more years of hands-on experience
‫developing and maintaining an AWS-based application.
‫So this is something that you need to acquire.
‫Obviously if you're new to AWS,
‫you don't have one year of experience
‫and this course probably will allow you
‫to have a huge jumpstart into understanding AWS
‫but what you need to do is go a little bit hands-on
‫before doing the exam.
‫There's nothing new you're going to learn
‫but you're just going to solidify
‫all this learning into your head,
‫it's going to start making more sense to you
‫and hopefully, you've already starting applying this
‫at your job using AWS.
‫So this is something that you may want to wait.
‫If you don't feel too confident about AWS yet,
‫try to get a bit more experience.
‫Review this course one more time
‫and then you're ready to pass the exam.
‫A high level programming language you need to know
‫for this we've been using Python 3.6 all around this course
‫but no JS, Go Java, all of these work.
‫Usually when you know a programming language,
‫you can understand all the things
‫I've been doing in this course so you're fine.
‫Remember, the exam will not ask you
‫programming questions but understanding
‫how programming works is really important
‫because this is a developer certificate.
‫Now, let's look at the AWS specific stuff.
‫We have the understanding of core services for sure
‫and we know the basic AWS architecture best practices
‫for example load balancer or the scaling groups.
‫We definitely know how to do development,
‫deployment now with CICD
‫and debugging we can use CloudWatch,
‫we can use X-Ray, there's a lot of things we can do here.
‫We know how to use the AWS services API.
‫We've seen the main ones,
‫we've done a lot of stuff with the CLI
‫and we've used the SDK numerous times
‫when using AWS Lambda.
‫Now we know the key features
‫of each AWS services that we've seen.
‫I had a lot of slides on them
‫so hopefully, you had a lot of learning.
‫The AWS shared responsibilities model
‫is something I haven't explicitly mentioned
‫but what this means is that AWS takes care of the security
‫of their infrastructure but you're responsible
‫for your own security.
‫So that means that your security groups
‫are your responsibility,
‫enabling encryption is your responsibility, etc, etc.
‫AWS does not guarantee that your application
‫will be secure because it is your application
‫so it is your responsibility.
‫What you have the guarantee is that AWS will not be hacked
‫hopefully by hackers.
‫Now, the application lifecycle management,
‫for sure we've seen this.
‫We've seen how to do dev tests prod.
‫We've had CD Pipeline,
‫we've seen how to do Lambda aliases
‫to point to different versions as well as API Gateway stages
‫so we can see the application lifecycle management for sure.
‫We have used a CICD Pipeline
‫to build and deploy applications
‫all the way from CodeCommit, CodeBuild,
‫CodePipeline and we've seen an overview of CodeDeploy
‫and we've seen Elastic Beanstalk as the deployment platform.
‫We know how to interact AWS services using the CLI
‫and the console, that's for sure.
‫We know the basic understanding
‫of writing cloud native applications
‫so this is pretty easy but that means that
‫either it's a Lambda function
‫or it's going to be something like ECS and docker.
‫We know how to write code using the best practices
‫so look at this.
‫Don't use secrets and access key in the code.
‫We know for that for sure.
‫AMI roles I've been really telling you all the time
‫to never use keys and always use AMI roles.
‫I've demonstrated this into EC2 roll instances,
‫CodeBuild roll instances, Lambda roll instances.
‫We've had plenty of practice with policies
‫assigning roles and modifying them
‫to go around permission issues.
‫We know how to author and maintain modules on AWS.
‫This is pretty much the same as using the SDK
‫and we know how to write code for service applications.
‫We've had Lambda functions for doing numerous things
‫and we actually also know how to use the SAM framework
‫so serverless application model
‫to write the code and deploy it on the AWS network
‫which is great.
‫Finally, the understanding of the use of container
‫in the development process.
‫This is around ECS so it doesn't ask you
‫to know how to do it.
‫It's just as an understanding of the use of container
‫so this is why I gave you more of an introduction to ECS.
‫You know enough just know that ECS equals docker,
‫equals application load balancer,
‫equals scalable model type of thing.
‫So that's it.
‫You know we have pretty much covered
‫all the AWS knowledge.
‫This is obviously high-level.
‫What we've been doing is a big drill down
‫into all the services that cover these areas.
‫You could go into the exam prep.
‫As you can see, you can do it as training,
‫you can look at some white papers but overall,
‫if you trust me, I've prepared you well hopefully.
‫So that's it.
‫You know we've learned all the things we need to learn.
‫Now I'm just going to give you some exam tips
‫in the next lecture.