I find it hard to remember configuration parameters, default settings, metrics. These are key to many certifications. Often we focus on the problem at hand, not specific functions or code to check.
Every definition is custom to each cloud provider and the set of theoretical FAQ questions, syntax specific to language. We neither measure problem solving or domain knowledge but rely on syntax and remembering facts. This is a stark difference between product vs service companies.
Certification does not necessarily mean you have the skills to build a solution. They merely imply familiarity with a tool/infra. As long as you map your current skills to new skills find the gaps and address you can build the required solution.
Learning is a collection of observations, experiments, experiences, applying your relevant past lessons. It is a compound effect. Building a solution is easy, but thinking from a futuristic perspective marks the difference between a newbie and an experienced techie.
20 years of experience is not working on the same project. The wider you explore bigger the perspective. The more you fail, the more you are aware of different domains/roles. In the end, let it be a collective memory of different experiences. Win or lose enjoy the journey.
I keep coding my logic with a mix of syntax I recollect across SQL, C, Python, R, C#. First, pseudo logic comes to mind. Later the logic is corrected based on StackOverflow answers. Every language has its own way of defining constructs and separators. Am I a bad programmer, mmm maybe... Always there is more to learn :)
Anyways value addition needs to be quantified so you need to pass this too :)
