Classes are still very important to know. All CIDR did was make it so you didn't have to use a /8 /16 or /24. It allows you to move freely through the classes /10, 14, 27 ect. Therefore making them "classless"
Classes are still taught, they are kind of needed to explain CIDR. Classes are not a real world limitation anymore, but simply a conceptual rule that many still follow.
use this video for network engineering interviews you want to fail. because this makes you sound like someone who doesn’t know anything but wants to pass an interview
he is giving very generic answers, name dropping buzz words. for example Q1: he says how hackers can shut down a network, gives examples of ddos attack which is rarely dependent on your ability as an engineer to block thousands of ip addresses, you have to work with your isp. then he doesn’t get into detail about what hackers target, he talks about firewall but doesn’t talk specific, makes you sound like you don’t know what you’re talking about. as someone who’s worked in cybersecurity and designed cybersecurity frameworks this is not something i could type here in a simple comment. but i’ll try i guess. firewall is one thing, but what about it? i’d say employ zero trust fundemantals in strict bidirectional ACLs to control traffic. deep packet inspection, monitor periodically paired with a EDR solution to monitor endpoints. more to say on firewalls but moving on to network principles he doesn’t talk about NAC, or 802.1x which is essential for organizations to control access to their corporate networks, additionally having network segregation for their guests q2: in future replies
he provides buzz words without going into specifics, answering this way will just make it look like you prepared for interview and cutting corners, the questions may be relevant to an actual interview but the answers are scratching the surface. start with the first question about network security. he mentions DDOS but doesn’t say how you protect against it, such as having 0 trust fundamentals on your firewall through bidirectional strict ACLs, deep packet inspection, paired with a valid EDR solution. doesn’t talk about 802.1x or NAC which is important for corpnet security. protecting your external facing services via DNS filtering as to never expose public IPs, and isolating management, guest and corp networks
30 GREAT ANSWERS for your NETWORK ENGINEER INTERVIEW ----> www.mockquestions.com/position/Network+Engineer/YT/
There are 5 classes..
Good information for any N/W engineer, Your voice is great with good BG music. Thank you it really helped :)
Thanks Anand! We appreciate the feedback.
This was great, very well thought out and practical!
Thanks!
Very good video. It is professional and precise to the point. Thank you
And also, in Clear English
It's soothing listening to you! I enjoyed watching it ❤
Are classes still taught? I thought after cidr, classful (class a,b,c) was obsolete?
Classes are still very important to know. All CIDR did was make it so you didn't have to use a /8 /16 or /24. It allows you to move freely through the classes /10, 14, 27 ect. Therefore making them "classless"
Classes are still taught, they are kind of needed to explain CIDR. Classes are not a real world limitation anymore, but simply a conceptual rule that many still follow.
@@XrayTheMyth23 So it's like how OSI model has been obsolete but we wouldn't know TCP/IP suite if we don't learn it
thanks sir, it was very smooth answers
Thank you for sharing this video it will helps a lot.
Glad it was helpful!
Thank u so much sir. It helped me a lot. 😍❤️
I'm glad it was helpful!
music to loud in the background...
Thanks for the feedback. We'll work on that for future videos.
Thank you..
thanks, Bradley Cooper's brother
Questions seem quite basic for an engineering role...
Agreed.
100%
the music making noise
use this video for network engineering interviews you want to fail. because this makes you sound like someone who doesn’t know anything but wants to pass an interview
Why is that?
he is giving very generic answers, name dropping buzz words. for example Q1: he says how hackers can shut down a network, gives examples of ddos attack which is rarely dependent on your ability as an engineer to block thousands of ip addresses, you have to work with your isp. then he doesn’t get into detail about what hackers target, he talks about firewall but doesn’t talk specific, makes you sound like you don’t know what you’re talking about. as someone who’s worked in cybersecurity and designed cybersecurity frameworks this is not something i could type here in a simple comment. but i’ll try i guess. firewall is one thing, but what about it? i’d say employ zero trust fundemantals in strict bidirectional ACLs to control traffic. deep packet inspection, monitor periodically paired with a EDR solution to monitor endpoints. more to say on firewalls but moving on to network principles he doesn’t talk about NAC, or 802.1x which is essential for organizations to control access to their corporate networks, additionally having network segregation for their guests
q2: in future replies
@@HansaGBByou need specific examples
looks like my previous reply as to the “why” was removed. trying this again
he provides buzz words without going into specifics, answering this way will just make it look like you prepared for interview and cutting corners, the questions may be relevant to an actual interview but the answers are scratching the surface. start with the first question about network security. he mentions DDOS but doesn’t say how you protect against it, such as having 0 trust fundamentals on your firewall through bidirectional strict ACLs, deep packet inspection, paired with a valid EDR solution. doesn’t talk about 802.1x or NAC which is important for corpnet security. protecting your external facing services via DNS filtering as to never expose public IPs, and isolating management, guest and corp networks