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

Freebase Hack Day

Ripple Baby Steps

Ripple and XPR
What is Ripple for people in business and finance? Ripple is a currency exchange and payment settlement platform built using blockchain technology. Unlike Ethereum that is a more universal distributed application platform, Ripple solves a more narrow set of problems such as sending payments (similar to Bitcoin), currency remittance, payments for invoices, as well as number of other use cases related to payment in different currencies between parties that may or may not trust each other. Ripple is fast, scalable, and provides number of functions needed to support different payment scenarios. XPR is a native Ripple currency with a fixed and limited supply coins. 100 Billion XPR cryptocoins are in circulation today and the same number will be in circulation tomorrow. 
What is Ripple for a software engineer?  For a software developer, Ripple is distributed ledger platform accessible trough API. There are number of libraries to accommodate different developers's preferen…

Respect Coin

Respect I think it's time to talk about currency. Let's create a Respect Coin.
Step 1. Install OpenZeppelin library npm install zeppelin-solidity
When it comes to coins, I like to use some functions that smart people already implemented and other smart people verified. I think that Zeppelin is a nice collection of Solidity contracts that can be trusted. Let's use the StandardToken contract and use it as a parent class for our own RespectCoin contract.
Step 2. Create RespectCoin contract and store it in "contracts/RespectCoin.sol" file pragma solidity ^0.4.4; import "../node_modules/zeppelin-solidity/contracts/token/StandardToken.sol"; /** * @title RespectCoin * @dev ERC20 Token example, where all tokens are pre-assigned to th e creator. * Note they can later distribute these tokens as they wish using `transfer` and other * `StandardToken` functions. */ contract RespectCoin is StandardToken { string public constant name = "RespectCoin&quo…