Skip to main content

AWS Solution Architect Certification :: Reflections

AWS Solution Architect Certification

Thoughts and Reflections

Just received a AWS Solution Architect Certificate and want to share some of my observations of the test (in no particular order):


  • If you used AWS for a few projects, passing the test will be easy. Compare to the amount of time and effort that it took me to pass Sun Enterprise Architect, it is probably 1/100 or 1/1000 
  • To my surprise, almost all questions were around S3, IAM, and EC2. It is much more to AWS, and I was thinking that they have more questions around RDS/EMR/Redshift
  • Tricky questions were "select 3 correct answers out of 6" or "2 out of 5" and it feel more like a lottery. It was almost half all questions that are in "multiple correct choice" category. When answering these questions, please read every word of it as they often put "sort-of-right answer" and "right answer" and unless all options are read fully it is easy to choose "sort-of-right" answer.
  • Learn when EBS volumes are deleted
  • No need to remember AWS command line syntax 
  • No need to remember IOPS rates, write capacity limits, and maximum sizes of anything in AWS
  • "Kinesis" was correct answer to 3 questions about the best solution for given scenario
  • "Spot Instance" was correct answer to more then one question that started with "what is the most cost-effective solution..."
  • VPC was the source of the most "tricky" questions for me, may be just because of my limited experience with VPC
  • It is plenty of time to answer questions, and to come back to them later, and to stair at the window, and to think about answers to these important questions (not given on the test): "Why do I want another certification?",  "Would this time be better spent somewhere else?" and "What do I want?"

Good luck on your test!

Comments

Popular posts from this blog

Amazon Simple Email Service (Amazon SES) and PHP

This morning Amazon announced availability of a bulk email delivery service called " Simple Email Service ". Anyone who knows how much pain is it to set-up scalable email solution (and it is not just spammers who need it!) should celebrate the occasion. I know of a company that spent several years cleaning ip addresses it sends email and found itself locked into the contract with internet provider since it would take forever to reach required level of email deliver ability anywhere else. Anyway, this evening I decided to check the Amazon claim that the service is "simple". Found out that it is indeed simple! Since there is not much in terms of the documentation yet, here is my code where I used AWS PHP library : // Enable full-blown error reporting. http://twitter.com/rasmus/status/7448448829 error_reporting (- 1 ); // Set plain text headers header ( "Content-type: text/plain; charset=utf-8" ); // Include the SDK require_once '../sdk.class.php&#

"Hello World" from Solidity

How to say "Hello World" in the era of blockchain? Reflections Once upon a time, I worked in CTO role of a great startup, and in order to find talented code developers, we ran a competition for the most creative "Hello World" application. It was a lot of fun! I was not able to participate in the competition back then, but here is my delayed entry. Step 1. Environment Configuration # Installing Truffle framework (http://truffleframework.com/) $ sudo npm install -g truffle # Creating project $ mkdir solidity-experiments $ cd solidity-experiments/ $ truffle init # Installing and starting Etherium local test network $ sudo npm install -g ethereumjs-testrpc $ testrpc & Step 2. Point truffle framework to the test network Update truffle.js file created by the init to point to your test network. File content should look like this: module.exports = { networks: { development: { host: "localhost", port: 8545, network_id: "*"

"Hello World" with counter

Friend of mine pointed out that the "Hello World" contract described in my previous post does not keep state. Reading and writing data to the blockchain is important and can be challenging. In this post I will add a counter to count number of times the sayHello() function was called.    Step 1. Create  a new contract Let's create a file HelloWithCounter.sol and put it into the "contracts" directory. pragma solidity ^0.4.4; contract HelloWithCounter { uint private helloCounter; function Hello() public { // constructor helloCounter = 0; } function sayHello() public returns (string) { helloCounter = helloCounter+1; return strConcat('I say Hello #', uintToString(helloCounter)); } function getHelloCounter() constant public returns (string) { return uintToString(helloCounter); } function uintToString(uint v) internal pure returns (string str) { uint maxlength = 100; bytes memory reversed = new byt