Do you want to get your first cloud architect job? Learn how in our FREE webinar! Register for the FREE Cloud Architect Career Webinar here www.gocloudarchitects.com/free-cloud-webinar
0:44 What is the difference between IOPS and THROUGHPUT? 2:56 What is the difference between a Network ACL and a Security group? 4:29 Describe the levels of RAID 9:10 Describe the AWS shared responsibility model 10:43 Tell me about a major contribution you made to your last employer 12:12 Tell me about a major challenge at work and what you did to get past it
First question is implicit trick instead of knowledge testing. There is no rule that "throughput" should be measured in bytes instead of operations, for example you can measure "network throughtput" in packets, and of course you always consider block-size when you're talking about IOPS. Second question is in fact about "how AWS terminology doesn't care about their users much". Of course everybody understands that there should be ACL rule for network, and ACL rule for specific node in that network, who cares (or even remembers) how it's called in AWS interface? You will forgot this names after 10 minutes you close your AWS console tab. Didn't saw next questions, I guess they are pretty much "give me mouse coordinates related to left top corner of aws console web-interface to navigate to Elastic Beanstalk settings". For what it's worth, I was interviewed a lot on searching job lately, and I don't recommend taking jobs with such interview questions - if it's not related to solving real engineering problems - you should not expect that your performance will be measured by solving engineering problems after all.
Network throughout is not measured in packets it’s megabits or gigabits per second. My CCIE number is 7147 and I have spent a decade working as a network architect for Cisco. Packet count is not relevant as we don’t know if it’s a 64 byte packet or a 1500 byte packet. These are architect questions not engineering questions. Architects and engineers have very different jobs. Architects are not doing engineering things like being hands on they design, present and sell. Cloud architects need to focus on the big picture and solving business problems and not engineering. You can’t focus on digital transformation and deep engineering. Over 100 people have gotten solution architect jobs using these questions and answers since this video was made as this is what companies are looking for. The companies don’t want the architects to do deep engineering work. If you want to do deep engineering work we suggest cloud engineering as a career. In this manner you will get to do technical work as opposed to meetings, presentations, entertaining clients, responding to RFIs, RFPs and RFQs etc and client facing sales. That’s what we architects do not engineering.
A cloud architect is someone who takes customer requirements business goals, tech requirements, legal requirements and regulatory requirements and designs an architecture to the customers needs. The architecture is all of the systems that work together, processes etc.
![I.N "HALLUCINATION" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/n5B5q1Hwt_U/mqdefault.jpg)
Do you want to get your first cloud architect job? Learn how in our FREE webinar! Register for the FREE Cloud Architect Career Webinar here www.gocloudarchitects.com/free-cloud-webinar
wow! i really love how you broke down IOPS vs THROUGHPUT. 3mins in and I'm already learning so much!
Thank you Richard.
Gud content
0:44 What is the difference between IOPS and THROUGHPUT?
2:56 What is the difference between a Network ACL and a Security group?
4:29 Describe the levels of RAID
9:10 Describe the AWS shared responsibility model
10:43 Tell me about a major contribution you made to your last employer
12:12 Tell me about a major challenge at work and what you did to get past it
Thank you
This video will help so many people who have the chance to view it. Keep up the good work!
I am only 3 minutes in and I am screaming this is awesome. GOD bless you for me. Thank you, Thank you, Thank youuuuuu.
Hi Convos,
Thank you so much for your kind feedback. It means so much to us.
Interview technical questions explained in a very simple way - love it
Thank you very much!
You are a God send. Thank you so much . I learned more in 3 days then I have in 2 months
Thank you so much. Your feedback means so much to us.
These are great specific examples. Thanks for sharing!
Thank you
This is awesome
Thank you for your support.
Excellent questions to study and learn.
Thank you very much
Great questions and strategies for your next job.
Thank you Data_Dave!
This is just fantastic. I love the information and the engagement opportunities. Liked and subscribed!
Thank you Leavon. Welcome. We are very happy to have you here!
Makeing video like that take a lot of time but it really worth
Thank you Ezz. We want to give the cloud architect community as much help as possible!
I enjoyed the breakdown of the interview questions, definitely does build a base to start at by identifying some of the questions.
Thank you Eric. We are trying to help people prepare for cloud architect interviews but also add a training component to these videos.
Thank you
Thank you!
#cloudhired
Thank you, Mike. That interview questions are excellent.
Thank you Ahmed.
Too Good and very nice way to conveyed the message. Thank you. Keep it up will wait for more videos to come on AWS and othet cloud technology.
Thank you very much
Awesome video, really engaging.
Thank you so much!
Very interesting and simple questions. Thanks Mike and GoCloud Architects for these resources
Thank you Agbor!
Looking forward to our interview.
Thank you very much!
I look forward to these interview questions. They are extremely valuable and helpful. Keep them coming
Rich, thank you. We are doing everything we can to help the cloud architect community.
Very informative video, keep making these great videos. Thank you very much for your help
Thank you, Andy!
I'm glad you enjoyed it!
#cloudhired
Thank you Michael for these insights
Thank you very much Tolani.
Very nice explanation
Thank you Arvind.
Keep the knowledge coming, Mike!!
Thank you Jide!
These videos are great!
Thank you George. We try to do everything we can for the cloud architect community!
Great video very informational!
Thank you very much!
please make a video on how multi cloud architect jobs will look in the future.
and how building your own cloud (from experience course) would help.
Excellent Idea. I will make in the next few weeks
AWESOME explanation!
Thank you very much Cesar!
Thank you Mike.
Thank you Ayodeji.
Amazing!
Thank you Karthika
Thanks for your dedication to this field of knowledge. You have helped my online business so muc!
Thank you
You videos are amazing. Thank you
Thank you Louie!
First question is implicit trick instead of knowledge testing. There is no rule that "throughput" should be measured in bytes instead of operations, for example you can measure "network throughtput" in packets, and of course you always consider block-size when you're talking about IOPS.
Second question is in fact about "how AWS terminology doesn't care about their users much". Of course everybody understands that there should be ACL rule for network, and ACL rule for specific node in that network, who cares (or even remembers) how it's called in AWS interface? You will forgot this names after 10 minutes you close your AWS console tab.
Didn't saw next questions, I guess they are pretty much "give me mouse coordinates related to left top corner of aws console web-interface to navigate to Elastic Beanstalk settings".
For what it's worth, I was interviewed a lot on searching job lately, and I don't recommend taking jobs with such interview questions - if it's not related to solving real engineering problems - you should not expect that your performance will be measured by solving engineering problems after all.
Network throughout is not measured in packets it’s megabits or gigabits per second. My CCIE number is 7147 and I have spent a decade working as a network architect for Cisco. Packet count is not relevant as we don’t know if it’s a 64 byte packet or a 1500 byte packet.
These are architect questions not engineering questions. Architects and engineers have very different jobs. Architects are not doing engineering things like being hands on they design, present and sell.
Cloud architects need to focus on the big picture and solving business problems and not engineering. You can’t focus on digital transformation and deep engineering.
Over 100 people have gotten solution architect jobs using these questions and answers since this video was made as this is what companies are looking for.
The companies don’t want the architects to do deep engineering work. If you want to do deep engineering work we suggest cloud engineering as a career. In this manner you will get to do technical work as opposed to meetings, presentations, entertaining clients, responding to RFIs, RFPs and RFQs etc and client facing sales.
That’s what we architects do not engineering.
Wonderful more videos will release with the new program " Ask Mike "
Ezz, Yes i will be making more videos!
what is cloud technology architect?
A cloud architect is someone who takes customer requirements business goals, tech requirements, legal requirements and regulatory requirements and designs an architecture to the customers needs.
The architecture is all of the systems that work together, processes etc.