Are you currently learning AWS and cloud computing? Do you want to pass the SSA-C03 exam and ace your cloud architect interviews and get hired?
Or perhaps you've seen the growth of AWS and are curious about what it takes to become a Cloud Architect?
Well either way, you’ve come to the right place!
I'm Amber Israelsen and I've been a developer and technical trainer for almost 20 years (that's scary to write)!
In this post, I'll walk you through the Cloud Architect role, outline what they actually do, and then break down the Cloud Architect job interview.
Most importantly, I've provided 25 interview questions and answers to help you prep for your interviews (or just test yourself to see if you're ready).
As a little bonus, I've also included some of tips and tricks on how to ace your cloud architect interview and secure your new role.
Sound good? Alright, go grab your favorite beverage and let’s get started!
Unless you’ve been living under a rock, you know that cloud computing is everywhere these days.
Companies have been making the move to the cloud for many years to get better performance, reliability, and global reach - all at a lower cost than what they could do with their own data centers.
And thanks to this rise in cloud computing, there are now a lot of new jobs specializing in cloud services and applications.
Given this growth is projected to only continue, it also makes this a great future-proof career option (at least for the foreseeable future... you just never know about those robots right?!).
Sidenote: The three main players providing cloud computing services are Amazon Web Services, (otherwise known as 'AWS' and has the largest market share), Azure from Microsoft, and Google's 'Google Cloud' Platform.
Although I'm going to be giving you examples focused on the AWS Cloud Architect role, broadly speaking, the role is the same across each of the cloud providers, just the names of the services change.
The Cloud Architect role is both a lucrative and prestigious position.
According to ZipRecruiter, the average salary for a Cloud Architect in the U.S. is over $155,000 per year.
Not bad right?
As for job opportunities, there are currently over 70,000+ Cloud Architect openings in the US alone.
So, it pays well and it’s in demand, but what exactly does the role look like?
Simply put, a Cloud Architect designs architecture for new systems in the cloud, or for systems that are being migrated to the cloud.
Still confused? Fair.
It basically means they figure out how all the pieces fit together in a way that fulfills business requirements:
Other potential tasks could be:
The Cloud Architect role is typically not an entry-level role.
Because a Cloud Architect is required to understand so many pieces of the technical puzzle, it’s helpful to have a few years experience, along with a varied background in tech, before pursuing the architect role.
That’s why most Cloud Architects usually start their career as a Software Developer, a Systems Engineer, a DevOps Engineer, a Network Administrator or even other roles like Database management or Cyber Security.
Joking aside though, you don’t need a background in all of these to get hired.
But having a background and experience in one (maybe two) of these will be a huge boost to your chances.
Then having a general working knowledge of the other areas is helpful but not the best use of your time. Just learn the rest of these things when you're on the job, getting paid to learn 😉.
Like any other kind of interview, it’s always good to:
It’s not just about the tech. In addition to technical know-how, interviewers will also be looking at soft skills.
In the Cloud Architect role, you’ll have frequent interactions with senior leaders, you’ll lead and consult teams, and collaborate with other key roles across the company. Be ready to give examples of how you’ve done this effectively in the past.
Because Cloud Architect positions are in high demand, you’ll likely face some stiff competition when applying for jobs.
To stack the odds in your favor, prepare as much as you can through training, certifications, and getting a lot of hands-on experience!
The more you apply what you learn (ie: building your own projects or working on other real-world projects), the faster you’ll learn and remember. And better still, you'll also be building a project portfolio to help land those interviews.
My advice is simple. Build as many projects as you can, while piecing together as many services as you can!
If you’re thinking of working with AWS, a great start for inspiration is the Well-Architected Labs.
They have some great advice on building cloud architecture.
Okay, enough of the obvious prep! Let’s get to some interview questions and answers.
Generally speaking, questions for this role are going to involve a lot of scenarios that you will need to adapt your answers to.
What like?
Well, you’ll need to show a deep understanding of the various options, pros, cons, and trade-offs for your plan, as well as being able to justify any approach you would take.
It’s good to know the best possible way, but it’s also important to know how to build 'good enough' so that you can also meet the company's specific criteria.
Just be sure to explain your choices and why you suggest each option. Interviewers generally care about your thought process and reasoning than they do about the specific answer you give.
It's possible you could get “basic” questions such as how a specific feature or service works.
But you'll almost certainly get more difficult scenario based questions that present you with a problem you have to solve.
The questions I've provided below contain a mix of question types. The answers I've provided are answered specifically towards how things work on AWS but most of the answers are still relevant for other service providers.
If the company you're applying for uses something other than AWS (or uses multiple providers), google the question + {cloud provider} and research to see how the answer for the specific cloud services provider might change.
I'd also recommend that rather than just reading the questions and answers below, you read the question and write out your answer before looking at the answer.
Ok, let's dive into some questions you might get:
Use a Cluster placement group strategy.
With this strategy, instances are physically close together (the same rack) in a single Availability Zone. This will achieve the requirements stated in the question.
However, it should be noted that this strategy is not highly available, as instances only reside in a single AZ.
Throughput Optimized HDD.
This volume type makes sense when you need to read large “chunks” of files at once. Common use cases include Big Data/data warehousing and log processing.
Spot instances.
With a Spot Instance, you can bid (specify the price you want to pay) on unused EC2 capacity. This can provide savings of up to 90% over On-Demand Instances.
With this model, instances can be shut down at any time. However, because the identified workloads are interruptible, this would still be a valid solution.
Network access control list (NACL). This is a firewall that controls traffic in and out of a subnet.
You might be tempted to say Security Group, but that controls traffic at the instance level.
Use Direct Connect.
Direct Connect offers a dedicated physical connection from an on-premises data center to AWS. It does not go over the public internet. However, it does take more time and expertise to set up and operate, as opposed to something like Site-to-Site VPN (but this option goes over the public internet).
Systems Manager (SSM) Parameter Store.
SSM Parameter Store is a valid way to store secrets and other information such as IDs in AWS.
For data that is NOT encrypted (like mentioned in the question), this is the only option (AWS Secrets Manager requires encryption).
Also, Parameter Store is free, up to 10,000 parameters, so this would be the most cost-effective option.
AWS Config. his is used to inventory, record and audit the configuration of your AWS resources.
VPC Endpoint, type Interface.
VPC endpoints, powered by PrivateLink, allow you to access other AWS services through a private network (vs. going across the public internet).
The “Interface” type is for all services except S3 and DynamoDB.
To enable internet access from a private subnet, you should create a NAT Gateway in a public subnet, add a route from the private subnet to it, and then add a route from the NAT Gateway to the Internet Gateway (which lives at the VPC level).
VPC Peering.
VPC peering allows you to connect one or more VPCs to make them behave like a single network. This can be done in the same account or across accounts.
You should allow inbound traffic on Port 80 and outbound traffic on Ports 1024-65535. Ports 1024-65535 will cover ephemeral ports for common clients.
This one can be a bit tricky.
A subnet mask of /24 will give you 256 IP addresses (which seems to be sufficient).
However, AWS reserves the first four and last IP addresses in every subnet.
So 256 minus 5 is only 251, which isn’t enough to cover the requirements in the question.
Therefore, you would have to go to the next number down, which is /23 (the smaller the number, the more IP addresses).
Server-side encryption with customer-provided keys (SSE-C).
The question states that the customer has keys on-premises, which means they should use server-side encryption with customer-provided keys (SSE-C).
With this option, the key is uploaded along with the object (via HTTPS only), and then encryption happens in AWS with the key that was uploaded.
SSE-C can only be done programmatically, which the development team is prepared to do.
To prevent deletion/overwriting for 7 years, you should use object lock with the Retention Period setting, set to 7 years, and in Compliance mode so nobody (not even root) can delete/overwrite objects.
S3 Intelligent-Tiering.
This option makes the most sense when data is changing or the access patterns are unknown. AWS will determine the most cost-effective way to store the data based on patterns it detects.
From the S3 portal, block public access for all buckets in the account. This would be the fastest and most efficient way to accomplish the requirements in the scenario.
Use Route 53 to route traffic across regions, and then use an Application Load Balancer with an Auto Scaling Group to route traffic and scale within a single region.
It is possible to use Route 53 in combination with an Application Load Balancer to distribute traffic globally across regions, and then also distribute it within regions. The Auto Scaling Group would also meet the scaling requirements mentioned in the question.
Create a read replica in a second region for the read traffic.
The scenario in the question is actually the ideal use case for a read replica.
By creating a read replica, the users who are only viewing videos (read-only traffic) can be directed to the replica, thereby reducing the load on the primary database.
Read replicas can also be cross-region, which would fulfill the requirements in the question.
Enable CloudWatch high resolution metrics.
With CloudWatch high resolution metrics, you can drill into metrics with a granularity of 1 second. With Standard resolution, you can only get granularity of 1 minute.
Service Control Policies allow you to manage permissions in an AWS organization. This reduces the administrative overhead of managing privileges for an entire account.
Apply a Service Control Policy to the Prod account denying permissions to create resources outside of us-west-1 and us-west-2.
The Lambda function has not been allocated enough memory.
Lambda memory size can range from 128 MB to 10,240 MB, and it is configurable. This value also affects the CPU resources.
If you notice poor performance on the function, a very likely cause is too little memory.
By enabling Sticky Sessions on the target group.
Enabling sticky sessions on the target group will set a cookie that enables future requests to be routed to the same instance.
How did you do?!
Did you get 25/25 correct? If so, I'd say you should stop studying and start interviewing!
Two tips to remember:
Didn't get them all? Got tripped up on some? Don't sweat it, I'm here to help.
If you want to fast-track your cloud architect interview prep and get as much hands-on practice as you can, check out my AWS Certified Solutions Architect training course.
Either way, I hope these interview questions help you land that $100K+ job as a Cloud Architect.
Good luck, you got this!