I guess the most difficult part is when they go "by the book" e.g. asking you why customers might want to virtualize their infrastructure... If you don't give "their" answer (which has nothing to do with the sane business reasons or the extreme diversity of cases in real-life) you end up looping.
What are the architectural artifacts?
Mostly experience, previous projects, personal goals and achievements. Less hardcore tech details, more testing soft skills.
difference between stateful and stateless
How you achieve zero downtime release.
How will create a landing zone in GCP for migration.
Azure devops overall architecture and integration
What do you know about the IoTs and have you ever done any projects related to the IoTs.
ASG, Organizations, IAM, migration, lambda...
AWS presentation, general onion based security protocols regarding cloud and hybrid.
Viewing 901 - 910 interview questions