Skip to main content

AWS Certified Developer - Associate Exam - (DVA-C01) Cheat Sheets – Part #1

AWS Certified Developer - Associate Exam - (DVA-C01) Cheat Sheets – Part #1

Please note, this post assumes the reader is having the basic understanding about AWS Services, so that we will jump directly into exam related content.

Introduction:

This is one of the preliminary exams for AWS, the aspiring cloud programmers can take up this exam to level up their career.

Exam Question Format:

Question Type

Need to Answer

Distractors

Result

Multiple Choice

1

Rest of the Questions

Will get marks if correct

Multiple Response

2 or More

Rest of the Questions

Will get marks if correct,
Not get marks if any single answer is not correct (Even if other selected answers are correct)

Content:

There are 5 domains and the questions will be distributed based on the weightage as follows

Domain

Weightage

Deployment

22 %

Security

26 %

Development with AWS Services

30 %

Refactoring

10 %

Monitoring & Troubleshooting

12 %

 #1 Deployment

1.1            Deploy the code in AWS using CI/CD Pipelines, Processes and Patterns

CI/CD à Continuous Integration / Continuous Deployment

Tools available for CI/CD in AWS

1.1.1    AWS Codestar à Code editor with project management tools, collaborate with the team through this tool,  https://aws.amazon.com/codestar/

1.1.2    AWS CodeDeploy à Deploy the code to Amazon S3 Bucket / Github or any repos, configurable, fallback options available https://aws.amazon.com/codedeploy/

1.1.3    AWS CodeCommit à AWS version of Github repo, Similar to Github, can use the same Github Commands https://aws.amazon.com/codecommit/

1.1.4    AWS CodeBuild à Once committed this service will build the code and test the various configured scenarios https://aws.amazon.com/codebuild/

1.1.5    AWS CodePipeline à Staging step wise movement of the code automatically when configured, Build / Test / Release / Rollback all can be done automatically when triggered via AWS CodeCommit https://aws.amazon.com/codepipeline/

 

Links:

https://aws.amazon.com/certification/certified-developer-associate/

Download the exam guide »

Download the sample questions »

 

Comments

Popular posts from this blog

Using of global variables in C# - Drawbacks & Solutions

How using global variables can have implications on the design, maintainability, and test-ability of C# code: Harder to understand and reason about the code:       class Program     {         public static int globalCounter = 0;         static void Main()         {             globalCounter++;             Console.WriteLine(globalCounter);         }     }   In this example, the global variable globalCounter is accessible from anywhere in the program, including the Main method. It's not clear where the value of the globalCounter is updated, it could be updated in other methods or classes, making it harder to trace the flow of data and understand the source of bugs.   More prone to errors:       class Program     {         public static string globalString;         static void Main()         {             globalString = "Hello" ;             Method1();             Method2();         }         static void Method1()         {

Task Parallel Library (TPL) and Akka.NET Alternatives

Task Parallel Library (TPL) and Akka.NET are among the most commonly used libraries for parallel and concurrent programming in the .NET ecosystem. However, there are also several other options available, depending on your specific needs: Parallel Language Integrated Query (PLINQ) is a parallel programming feature of .NET that provides an easy and efficient way to perform operations on collections in parallel. LINQ (Language Integrated Query) is a powerful feature in .NET that allows developers to work with data in a more declarative and language-integrated manner. While LINQ queries are inherently sequential, PLINQ extends LINQ by providing parallel versions of the query operators, allowing some queries to execute faster by utilizing multiple processors or cores on a machine. PLINQ is great when you are working with large collections where operations might be CPU-intensive or I/O-bound and could potentially be sped up by parallel execution. Here is a simple example of a PLI

SOLID Principles with Real World examples in C#

  SOLID Principles with Real World examples in C#   SOLID principles are formed by using S Single Responsibility Principles (SRP) O Open Closed Principle (OCP) L Liskov’s Substitution Principle (LCP) I Interface Segregation Principle (ISP) D Dependency Inversion Principle (DIP)   S Single Responsibility Principles (SRP) There should never be more than one reason for a class to change, to be precise one class should have only one responsibility Single Responsibility Principles (SRP) Real world example, A perfect match for SRP is Microservices , a Microservice will not contain functionalities other than the one it is designated to do,  Example ·                   Order Processing Service, ·                   Shipment Management Service, ·                   User Authentication Service, ·                   Catalogue List Service       class OrderProcessor     {         public void Process(Order order)         {             // Check inven