Friday the 13th Exam Disaster: How I Ignored My Own Advice and Passed the VCF Architect Exam Anyway
Two weeks ago I published a detailed guide about preparing for the VMware Cloud Foundation 9.0 Architect exam. I broke down the blueprint, explained AMPRS frameworks, discussed study strategies, and generally acted like someone who had a plan.
Then I did absolutely none of it.
Instead, I scheduled the exam for Friday the 13th. With zero preparation. Because apparently I enjoy tempting fate.
The YOLO Approach (or: How to Ignore Your Own Advice)
Here’s what actually happened:
Wednesday morning, I thought: “I’ll just take the exam. If I fail, I’ll see where the gaps are and fill them. Then retake it properly.”
No review. No flashcards. No reading the VMware Cloud Foundation documentation I specifically recommended in my prep guide. Just pure YOLO energy and years of designing VCF environments.
And what better day to schedule a high-stakes certification exam than Friday the 13th?
The horror movie practically writes itself: “He wrote the study guide. But he didn’t read it. Now, on the unluckiest day of the year, he faces… 60 questions of architectural terror.”
The Exam Experience (Friday the 13th Edition)
135 minutes. 60 questions. Friday the 13th. What could possibly go wrong?
Turns out: nothing.
Most questions were scenario-based design decisions exactly like I described in the prep guide. “A customer needs to deploy VCF across two sites with automated failover. They have existing network infrastructure and limited budget. Which topology do you recommend and why?”
The thing is: I’ve lived these questions. Not in study materials. In actual customer workshops. In 2am architecture debates with colleagues. In “this design almost worked but broke in production” post-mortems.
The exam wasn’t testing if I’d memorized the blueprint. It was testing if I could think like an architect. And after years of VCF design work, that thinking pattern is muscle memory.
The only scary thing about Friday the 13th? Realizing I’d spent two weeks writing a study guide I didn’t need.
The Result
I passed.
With a score high enough that I’m comfortable saying: the YOLO approach worked.
Not because studying is pointless. But because experience designing real VCF environments is the actual exam prep. The blueprint study is just mapping what you already know to how they’ll ask the questions.
What This Actually Means
Should you skip studying and wing it? Probably not.
I’ve been designing VCF since version 3.x. I’ve built stretched clusters. I’ve argued about NSX edge placement. I’ve sized management domains for multi-tenant environments. I’ve explained to stakeholders why their “just add more hosts” plan won’t work.
The exam tested exactly that knowledge. The kind you get from doing the work, not reading about it.
If you’re new to VCF architecture: read the docs, study the blueprint, practice the design patterns. That post I wrote two weeks ago? It’s good advice for someone building VCF experience.
But if you’ve been designing VCF in production for years? The exam is validating what you already know, not teaching you new things.
The Uncomfortable Truth
VMware certifications have always been weird for experienced practitioners. You know the material. You’ve lived it. But the exam format tests pattern recognition and blueprint-specific language as much as actual expertise.
The YOLO approach worked for me because I had years of context. The questions mapped directly to decisions I’ve made dozens of times. Different customer, same architectural trade-offs.
If you asked me “what’s the best topology for stretched VCF?” I’d say “it depends on latency, budget, and risk tolerance.” And then I’d ask five clarifying questions. The exam gives you those clarifications in the scenario, and you pick the pattern that fits.
That’s not luck. That’s experience.
Lessons Learned
1. The exam blueprint is a map, not the territory. Knowing the blueprint helps you navigate the exam. Actually doing VCF architecture work is the real preparation.
2. Scenario-based questions reward real-world thinking. If you’ve solved similar problems in production, the exam scenarios feel familiar. If you’ve only read documentation, they’re much harder.
3. Sometimes confidence is earned, not studied. I went YOLO because I knew I’d designed these patterns before. That confidence came from experience, not exam prep.
4. Study guides (including mine) are most valuable for people building experience. If you’re already experienced, they’re useful for calibrating your knowledge to the exam format. But the knowledge itself should already be there.
The Bottom Line
I wrote a detailed exam prep guide. Then I ignored it, scheduled the exam for Friday the 13th, and passed anyway.
This isn’t a flex. It’s a recognition that the actual preparation happened over years of VCF design work, not two weeks of studying blueprints.
If you’re taking this exam: study if you need to build knowledge. But if you’ve been doing VCF architecture in production, trust your experience. You probably know more than you think.
And maybe don’t schedule high-stakes exams for Friday the 13th. Unless you enjoy the thrill of tempting fate.
Exam Date: Friday, February 13, 2026 (because why not?) Result: Passed with a score well above the threshold Total prep time: Zero hours Years of VCF experience: Actually priceless Superstitions violated: At least one