Even though this is a simple activity, you won't remember all the exact details of creating that resource unless you've written EC2 terraform scripts extensively. Besides, why would anyone memorize thousands of API details of creating something when it's readily available in the documentation? I have taken technical interviews to junior candidates and even I won't ask these things. If you know Terraform fundamentals, how it works, and how you write them, that is enough. If you don't know something, there's always documentation you can refer to. To make it simpler, I asked the interviewer if I can check the documentation since I have not written for EC2 lately, but he did not allow. I explained that I have created VSCode keyboard shortcuts in my work laptop that produces a Terraform block. On the other hand, we don't encourage new joiners to write a vanilla Terraform script by hand. We have created standard modules/templates that must be used to create anything, this helps manage time better, to prevent everyone rewriting the same piece of code, and to standardize resource management. I explained all this to the interviewer but he was not convinced. In a time where documentation is readily available, I was surprised how the interviewer was so against it. Anybody can pick up on new tools and technologies. Instead of sticking to the fundamentals, I was asked highly specific questions.