Post by Mehrez Ben Mohamed

AWS Cloud Architect | DevOps & MLOps | Building GenAI solutions on AWS (Bedrock, SageMaker) | AWS Certified (SA Pro + 3 Associate)

Just passed the AWS Solutions Architect Professional. Barely. But I’ll take it. Honestly? I thought it would just be “Associate, but harder”. I had 3 Associates already (SA, Dev, SysOps), I figured the Pro was the next logical step. It’s not. It’s a different game. Associate asks: “Which AWS service fits here?” Pro asks: “You have 4 valid architectures. Which one wins?” All 4 answers are technically correct. Only one is right for the context. And you get about 2 minutes to figure out which. After 2 months of prep, I walked out of the exam convinced I had failed. The pass screen surprised me more than it should have. A few things I wish I’d known earlier: → The adjectives in the questions matter more than the services. “Cost-optimized” and “minimal operational overhead” lead to very different answers. → Read the last line of the question first. That’s where the real ask is. Then go back to the context. → On 4 answers, 2 can usually be eliminated in 10 seconds. The real decision is between the last two. → If you hesitate more than 90 seconds, flag it and move on. Your gut from the first read is usually right. → Migration, hybrid and multi-account scenarios are everywhere. Don’t skip Organizations, Control Tower, Transit Gateway. → Know your 4 DR strategies cold (backup & restore, pilot light, warm standby, multi-site). They show up in many forms. → Failing practice exams taught me 10x more than passing them. → Don’t start with practice exams. Start with whitepapers and real architecture diagrams. Exams are for calibration, not learning. → The most valuable thing I gained wasn’t the badge. It was a mental framework for evaluating trade-offs. Grateful for the journey, and for everyone who shared advice along the way. #AWS #CloudArchitect #Certification

Post content