I’ve started into getting a CCNA rather than try and get the stuff for the new Azure tests that where announced right after I purchased the material. How tragic. I may pursue those after this one is over but who knows. I also started into a new job and my admin encouraged a CCNA over an Azure cert. Cool thing about the new job, I have access to all sorts of admin stuff and am currently basically one manning a project to find and replace Win7 machines and am imagining a ton of machines. Anyway, I started into questions and quickly realized that I was in over my head after a Network+ but thankfully, there are books! I even found the primary CCNA book online for free after searching for a while. Its on a google drive and I’m not going to link it here but if you cant find it, I’m really not that hard to get a hold of. Anyway, ive read about half of the book and thought that I would go through some of the questions from the book. I do have a VCE as well and I’ll get into that but I thought it might be good to go through this. Anyway, apparently this is part 1 and i may actually have to purchase part 2 but we will get to that at later point. CCNA 200-301 Official Cert Guide, Volume 1
So the book looks like this and honestly its really well written but I have a long way to go so I’ll probably go through each volume of this and like I said, im about half way through the book. Anyway, this is the first two chapters with the answers and while I highly doubt the author will read this post, hopefully he doesnt get mad haha
So I hate theses things and while I’m sure that to some extent they exist in actual code or data transmission, I have a feeling its more of a concept of encapsulation and framing. This would be much easier for me to comprehend as I have a really hard time memorizing things that I cannot associate with concepts. I don’t know why, but its true. Anyway, the answers are below and I’m not spending much time on this unless I see a bunch of questions on the subject.
Ok, so moving on to the next one, same kind of thing but honestly just because its in a book absolutly does not mean it will be on test
Anyway, at this point it might be good to take a look at this. Like I was saying, not spending a bunch of time on it. Yet, here we are with a graph. Which doesnt make much sense as adjecent would be next to each other. Not to mention the book answers tell us HTTP is an Application layer, which is the highest level of coms and that TCP is transport. I mean I suppose that makes sense in theory but here is possibly a better graph.
And at this point, I move on.
I think this one is pretty obvious as its TCP to TCP transport but it does get me at least in the mood of understanding the complicatedness of HTTP transmission as it must move through the layers and there for somehow touch each form of communication in the form of encapsulation or framing as I was saying earlier.
oh, look, here we are with encapsulation comments which seem to indicate a direction of thought.
I would think this could be frame or packet. I’m not really sure exactly what a packet is but I would think it would only contain to and from information rather than data but lets see what the answer is.
Kind of close on this one but still slightly confused by it but understanding the idea that its types of headers and footers that they call encapsulation that are the determining factors in what we are looking at.
No fucking clue on this one. I have a feeling this will be testable and it is interesting information to consume.
Ok, so this is actually interesting that since it is a data-link protocol layer 2 PDU, which stands for protocol data units. I’ve never heard that term before.
I would assume A to be true but lets find out!
I was right, amazing!
Honestly, i would be guessing but assuming B
Wrong! Fake news! This is C. Good to know….
I’m going to be shocked if this is testable but again, I had no clue on the pin numbers. I dont think I’ll have to make cables anytime soon but who fucking knows. Sorry for cuss-n
I find this answer confusing as I can absolutely use any cord from a PC to literally any switch but ok!
Thats a confusing answer. I am vaguely familiar with fiber though. The main difference is sending and receiving data with multimode. Distance, I hadn’t really considered. Somehow.
This is what I would have assumed to be true as A is extremely improbable to be possible. C seems useless as its a widely implemented technology but d is tempting as AI is crazy.
I have no idea what this is so I should probably look it up. Frame check sequence
All frames and the bits, bytes, and fields contained within them, are susceptible to errors from a variety of sources. The FCS field contains a number that is calculated by the source node based on the data in the frame. This number is added to the end of a frame that is sent. When the destination node receives the frame the FCS number is recalculated and compared with the FCS number included in the frame. If the two numbers are different, an error is assumed and the frame is discarded.
The FCS provides error detection only. Error recovery must be performed through separate means. Ethernet, for example, specifies that a damaged frame should be discarded and does not specify any action to cause the frame to be retransmitted. Other protocols, notably the Transmission Control Protocol (TCP), can notice the data loss and initiate retransmission and error recovery.
So its error detection. Which we picked up from the answer and it basically works similarly to encryption which is in no way surprising lol
The first part is interesting about the length of the address and the OUI. I mean, this is the worst sentence I’ve ever written but I have no idea what the hell else to say haha. Absolutely bonkers. Anyway, most of this seems fairly baseline in terms of big picture how traffic gets from point A to point B and is little more than “different” Network+ info but I will say there is some actually detailed information int the book. Great day at work, planning and waiting on responses. Tomorrow I’ll start bothering people on the phone to find out info about monitor adapters.