A+ Core 1 Section 2: Networking, Ports, Protocols, and Hardware

The guide(s) referenced in this material can be found at the following link: https://www.etsy.com/shop/MountainRangeMedia

15% off at the shop on orders $25 or more! https://mountainrangemedia.etsy.com?coupon=MRMPODS15

New episodes release every Wednesday!

This podcast, based on the Mountain Range Production Sectional Study Guides, serves as a technical primer for the networking domain of the CompTIA A+ certification, prioritizing the practical knowledge required to manage and troubleshoot modern systems. It systematically breaks down the digital landscape into foundational protocols like TCP and UDP, essential hardware components such as routers and switches, and the physical media that connects them. By emphasizing well-known port numbers and the specifics of IP addressing, the text provides a roadmap for diagnosing connectivity issues and understanding how data traverses a network. Ultimately, the guide functions as a strategic resource for identifying the optimal standards for cabling and wireless configurations to ensure efficient and secure communication.

Intro & Outro info:
Music Licensor's Username: paulyudin-27739282
Licensee: u_x32f6b3u3b
Audio File Title: Tech Corporate
Provided courtesy of: https://pixabay.com

Voice provided courtesy of: venice.ai voice - Callum

Podcast audio hosts provided courtesy of: Notebook LM

Transcript

Copy Transcript Copied

Speaker 1 0:18

Imagine this, right? You are uh you're out in the field, you plug in a network cable, and all the lights on the switch are blinking a happy green.

Speaker 0:27

Always a good feeling.

Speaker 1 0:28

Right. But your computer still absolutely refuses to connect to the internet. And you're wondering, like, why? Well, the answer usually isn't in the hardware. It's hiding in a nearly invisible layer of digital translation.

Speaker 0:41

Yeah, that logical layer is where things get really tricky.

Speaker 1 0:45

Exactly. So welcome back. If you're joining us today, you are right on time for the second of our five very special deep dives. We've designed these specifically to help you absolutely crush the CompTIA A plus Core One exam.

Speaker 1:00

Which is no small task, by the way.

Speaker 1 1:02

No, definitely not. And we're pulling all our facts today from a comprehensive study guide put together by Mountain Range Media. Uh you can actually find it on their Etsy shop. It's just a fantastic resource.

Speaker 1:11

It really is, yeah.

Speaker 1 1:12

So today our mission is to conquer the networking domain. Now, networking makes up a massive 23% of the Core One exam. It is by far the single heaviest topic you're going to face.

Speaker 1:21

It really is. And there is a very specific reason why it carries so much weight, you know. This section of the exam rewards deep reasoning over simple rote memorization. Right.

Speaker 1 1:30

They're not just looking for vocabulary words.

Speaker 1:32

Exactly. They aren't just going to ask you to regurgitate a definition. The exam will give you a scenario and ask you to reason out exactly why two specific devices can or cannot talk to each other. You really have to understand the underlying layers of communication.

Speaker 1 1:48

Okay, let's unpack this. Because before devices can send data over cables, they have to agree on how they're going to communicate in the first place.

Speaker 1:56

Right. When data moves across a network, it primarily uses one of two transport protocols. You've got TCP or you've got UDP. Let's start with TCP, the transmission control protocol. Okay. So TCP is connection-oriented, and its defining feature is reliability. Before a single drop of actual data flows, TCP performs this strict three-way handshake to establish a connection.

Speaker 1 2:19

A handshake, like setting the ground rules first.

Speaker 2:21

Yeah, exactly. The initiating device sends a synchronized packet, or SYN. Then the receiving device responds with a synchronized acknowledge, which is S Y-N-A-C-K. And finally, the first device confirms with an acknowledge, or ACK.

Speaker 1 2:35

Got it. S Y-N, S Y N, A C K.

Speaker 2:38

Precisely. And once that connection is established, TCP numbers every single segment of data and waits for an acknowledgement that it was actually received.

Speaker 1 2:47

Oh wow. So it's tracking everything.

Speaker 2:49

Every single piece. If something gets lost along the way, TCP automatically retransmits it. It prioritizes accuracy over absolute speed.

Speaker 1 2:56

So TCP is like sending a certified letter where you absolutely need a signature upon delivery to prove it got there safely. Yes. But UDP, uh UDP is like firing a t-shirt cannon into a crowded stadium. Like you just blast it out there and hope someone catches it.

Speaker 3:11

That is a brilliant analogy, yeah. UDP, the user datagram protocol, is completely connectionless. It's incredibly lightweight.

Speaker 1 3:17

So no handshake then.

Speaker 3:18

No handshake, no numbering, and absolutely no guarantee of delivery. It just fires the packets. You use UDP when a little bit of data loss is better than waiting around for retransmissions.

Speaker 1 3:30

So on the exam, if we see a scenario involving web pages, email, or file transfers where every bit of data has to be perfect, we choose TCP. Right. But if the scenario is about real-time streaming, voice over IP, DNS lookups, or DHESP, we are looking for UDP because speed is the priority. Like you don't want a phone call buffering because it's waiting for a lost syllable.

Speaker 3:54

You've got it. That distinction alone will save you multiple times on the test.

Speaker 1 3:58

All right. So those are the broad transport protocols.

Speaker 4:00

Yeah.

Speaker 1 4:00

But once data reaches a server, it needs to know which specific application to talk to.

Speaker 4:05

Right. Which means we have to talk about ports.

Speaker 1 4:07

Yeah. And memorizing network ports can be super dry. So let's chunk these out by what they actually do. If I'm trying to browse the web, what logical doors am I using?

Speaker 4:15

So for standard unencrypted web traffic, you're using HSGTP on port 80, but honestly, you rarely see that anymore.

Speaker 1 4:22

Right, because of security.

Speaker 4:23

Exactly. Today almost everything uses HTTPS on port 443. , Jr.

Speaker 1 4:28

And the S is for secure, right? It wraps that web traffic in encryption. I think the study guide mentioned TLS here.

Speaker 4:34

Trevor Burrus, Jr. Yes, transport layer security. TLS is the cryptographic protocol that scrambles the data so nobody intercepting it can read your passwords or your credit card numbers. It's what makes port 443 secure.

Speaker 1 4:45

Okay. What about the digital mail room? If I'm dealing with email, what ports do I need to know?

Speaker 4:51

If you are sending an email out, your device uses SMTP, the simple mail transfer protocol, on port 25.

Speaker 1 4:57

Port 25 for sending. Got it.

Speaker 4:59

But receiving email is different. If you want to download an email and delete it from the server, which is the older way of doing things, you use POP3 on port 110.

Speaker 1 5:07

Okay.

Speaker 5:07

However, if you are checking email on your phone, your tablet, your laptop, and you want them all to stay synced up, you use IMAP on port 143.

Speaker 1 5:16

That makes total sense. SMTP sends it out, IMAP syncs it down on 143. What about getting under the hood? Like if I'm an IT admin and I need to securely access a remote service command line or transfer files, what am I using?

Speaker 5:28

For secure encrypted command line access, you use SSH, secure shell, on port 22. It's also used for SFTP, which is the secure file transfer protocol.

Speaker 1 5:39

Okay, so port 22 is the secure one.

Speaker 5:41

Right. Historically, people use Telnet on port 23 for remote access, or FTP on ports 20 and 21 for files, but those are completely unencrypted. Anyone listening on the network can see everything you type in plain text.

Speaker 1 5:53

Which is terrifying.

Speaker 5:54

Very terrifying. Don't use them.

Speaker 1 5:55

Okay, what about background infrastructure, like the invisible stuff making the network run?

Speaker 5:59

Well you have DNS, the domain name system, on port 53. It resolves human readable names to IP addresses.

Speaker 1 6:05

Right.

Speaker 6:06

And then DHCP, which automatically hands out IP addresses, uses port 67 and 68.

Speaker 1 6:12

Okay, last group. Give me the enterprise networking stuff.

Speaker 6:14

Sure. So SMB, server message block, uses port 445 for Windows file and printer sharing. For querying network directories, like Active Directory, you use LDAP on port 389, or the secure version LDAPS on port 636. Okay. And finally, RDP, Microsoft's remote desktop protocol, sits on port 3389.

Speaker 1 6:35

Man, okay, that is a massive list to memorize, but the study guide makes it clear you just kind of have to know them cold.

Speaker 6:41

What's fascinating here is the psychological trick the exam writers love to play with these ports.

Speaker 1 6:46

Oh, a trick like what?

Speaker 6:47

They'll give you a multiple choice scenario where a technician needs to set up a service and they will list both the secure and insecure port options as possible answers.

Speaker 1 6:56

Oh, like offering both port 80 and port 443 for web hosting or port 2012 telnet versus port 22 SSH.

Speaker 7:04

Exactly. The golden rule for the exam is if a secure version of a protocol exists, you should almost always choose the secure option. Choose HTTPS over HTTP, choose SSH over telnet, choose LDAPS over LDAP, just always default to security.

Speaker 1 7:19

That is a fantastic tip. Seriously. Okay, so those ports act like logical doors on a server, but what do the actual physical roads look like that connect those doors across the world? This brings us to the hardware, the cables, and Wi-Fi.

Speaker 7:32

To understand the hardware, you first have to grasp the difference between layer two and layer three of the network model.

Speaker 1 7:37

Okay, lay it on me.

Speaker 7:38

At layer two, you have your switches. A switch operates purely within a single local network. It forwards data frames based on physical MAC addresses. And an MAC address is effectively this permanent serial number burned into the network card of the device at the factory.

Speaker 1 7:55

Wait, if every device already has a unique physical MAC address burned into it, why isn't that enough? Like why do we need IP addresses at layer three?

Speaker 8:03

Think of it like this: an MAC address is like your social security number. It identifies exactly who you are. But an IP address is like your home street address, right? It tells the mail carrier where you are in the world.

Speaker 1 8:15

Oh my okay.

Speaker 8:15

If you want to send a message outside of your local network, knowing the device's identity isn't enough, you need to know its location. And that is where layer three routers come in. Routers connect different networks together, forwarding packets based on logical IP addresses.

Speaker 1 8:30

Got it. Your identity versus your location. Now, your typical home router usually has a few extra features built in, doesn't it?

Speaker 8:37

It does, yeah. It's usually a combination device.

Speaker 1 8:39

Right. Because it acts as an access point, broadcasting an SSID to bridge wireless devices onto the wired network. And it acts as a firewall, using a strict rule set to filter traffic based on those ports we just talked about. Of course, it connects to a modem.

Speaker 8:54

Right. A modem modulates and demodulates the signal from your internet service provider. If you have fiber internet, that modem is specifically called an ONT, an optical network terminal.

Speaker 1 9:06

Which translates the incoming pulses of light into the standard electrical Ethernet signals that your home router understands.

Speaker 9:12

Exactly.

Speaker 1 9:13

Speaking of electrical signals, we should definitely mention PoE, power over Ethernet.

Speaker 9:17

Yes. PoE is incredibly useful for enterprise setups. It allows a single Ethernet cable to deliver both data and electrical power.

Speaker 1 9:26

That's so convenient.

Speaker 9:27

It really is. This is exactly how you power access points on a high ceiling or security cameras on an outside wall where you just don't have a standard electrical outlet nearby.

Speaker 1 9:36

So a network switch can actually act as a power supply.

Speaker 9:38

That's really cool. We should also clarify VLAN and VPN really quickly because they sound super similar, and I don't want anyone getting confused on the test.

Speaker 1 9:46

Good call.

Speaker 9:47

A VLAN is a virtual local area network. It lets you take one physical switch and logically chop it up into separate isolated networks, like keeping guest Wi-Fi traffic completely walled off from employee traffic. But a VPN, on the other hand, is a virtual private network which builds a secure encrypted tunnel across the public internet.

Speaker 1 10:08

That's a vital distinction. But whether it's virtual or physical, all of this eventually relies on actual cables.

Speaker 10:14

Right. So let's talk about those tables. The great copper versus fiber debate. For the exam, you really need to know the specs for copper Ethernet. So we're talking category 5e, category 6, and category 6A.

Speaker 1 10:24

Right. So Cat 5E is the older standard. It pushes one gigabit per second up to 100 meters. But cat 6 is where people usually get tripped up. Yeah, because the study guide says cat 6 can handle 10 gigabits per second, but only up to about 55 meters. Why the drop-off? Like why can't it go the full 100 meters?

Speaker 10:44

It comes down to physics, specifically signal attenuation and crosstalk. Pushing 10 gigabits of electrical signal generates a lot of electromagnetic noise.

Speaker 1 10:53

Oh, I see.

Speaker 10:54

The longer the cable, the more the signals on the individual copple wires bleed into each other, and the weaker the overall signal becomes. So beyond 55 meters, there's just too much noise and too much signal loss to reliably sustain 10 gigabits. So the hardware drops the speed back down to one gigabit to prevent data corruption.

Speaker 1 11:10

So if a test question asks for a cable that guarantees 10 gigabits per second over a full 100-meter run, you must choose Cat 6A.

Speaker 11:18

Exactly. Cat 6A has thicker shielding and tighter twists than the copper to eliminate that crosstalk, allowing it to handle 10 gigabits across the entire 100-meter distance.

Speaker 1 11:27

What about fiber optic cables?

Speaker 11:29

Fiber is categorized mainly into single mode or SM and multi-mode or MM.

Speaker 1 11:34

What's the difference there?

Speaker 11:34

Single mode has a very narrow glass core. It uses a highly focused laser and is designed for long distances thing connecting two buildings across a university campus.

Speaker 1 11:45

Okay, so laser means long distance.

Speaker 11:47

Right. Multi-mode, on the other hand, has a wider core, uses LED light, and because the light bounces around more inside the wider core, it loses signal faster. It's meant for shorter distances, like connecting servers within the same data center.

Speaker 1 12:01

And we have to recognize the connectors on the ends of these cables. RJ45 is your classic eight-pin copper Ethernet plug. RJ11 is a smaller copper connector used for old telephones and DSL. Yep. And for fiber, you'll often see SFP or SFP plus modules. These are hot swappable transceivers. Like you can literally slide them right into a running high-end switch without turning it off, which is pretty amazing.

Speaker 12:24

Very handy. You also need to be very comfortable ranking the wireless standards for the exam. They love to test your knowledge of 802.11 standards.

Speaker 1 12:32

Okay. The Wi-Fi Alphabet Soup, A, B, G, N, A, C, A, X, is it really just about memorizing the order?

Speaker 12:38

It's about knowing the timeline of speeds and understanding the physics of the radio bands. The golden rule of Wi-Fi is this the 2.4 gigahertz band uses lower frequency waves.

Speaker 1 12:50

Okay.

Speaker 12:50

And because the wavelengths are longer, they can bend around and penetrate solid walls much more easily, giving you great range. But the trade-off is that it's relatively slow and highly congested.

Speaker 1 13:00

Because everything uses 2.4. Right. Baby monitors, microwaves.

Speaker 13:04

Everything. Now, the 5 gigahertz and new 6 gigahertz bands use shorter, faster waves. They can carry massive amounts of data, but they have a much shorter range and they bounce off solid objects rather than penetrating them.

Speaker 1 13:16

So to pass the exam, you need to know that 802.11A and B are the oldest legacy standards. Then came G. Then 802.11N, which was Wi-Fi 4.

Speaker 13:28

Right.

Speaker 1 13:28

And that introduced MIMO, which basically means it started using multiple antennas to send and receive data at the same time. Kind of like opening up extra lanes on a highway. Exactly. Then AC, or Wi-Fi 5, brought multi-gigabit speeds purely on the 5 gigahertz band. And finally 802.11AX, which is Wi-Fi 6, handles 2.4, 5, and 6 GHz bands with massive data capacity. Just remember the chronological speed order, ABGN, ACAX.

Speaker 13:56

Right. If a question asks you to upgrade an old wireless network for the absolute fastest throughput available today, you look for AX.

Speaker 1 14:03

So we have the physical cables and the wireless ways, but if I send a packet of data into that maze, how does it know which specific device to find? We need addresses.

Speaker 14:11

We do. At the logical layer, every device needs an IKE address. For decades we used IPv4. Okay. An IPv4 address is a 32-bit address written as four decimal numbers separated by periods, you know, like 192.168.1.10. The problem is the world ran out of public IPv4 addresses years ago.

Speaker 1 14:29

Which is why we created NAT network address translation. I always think of NAT like a giant corporate office building. Like the building itself only has one public street address that the post office knows.

Speaker 14:39

I like that.

Speaker 1 14:40

But inside, there are hundreds of employees sharing that address, and the receptionist routes the mail to their specific internal extension numbers. NAT lets an entire house of devices share just one public IP address.

Speaker 14:52

That is exactly how it works. But the long-term fix to the shortage is IPv6. IPv6 is a massive 128-bit address written in hexadecimal. It provides so many addresses that we don't even need NAT anymore. Every device on Earth can have its own public address.

Speaker 1 15:09

Which is mind-blowing.

Speaker 15:10

It really is. On the exam, you'll recognize a local IPv6 address because it typically starts with FE801.

Speaker 1 15:18

Now, typing out these addresses manually for every single phone and laptop would be a total nightmare. So we use DHCP to hand them out automatically. To get a lease, a device goes through a four-step process. You can remember it with the acronym D-O-R-A.

Speaker 15:30

DORA.

Speaker 1 15:31

Discover, offer, request, acknowledge. The client discovers the server, the server offers an address, the client requests to use it, and the server acknowledges the lease.

Speaker 15:39

And this brings us to one of the most critical troubleshooting concepts on the entire Core One exam.

Speaker 1 15:44

Here's where it gets really interesting. Let's talk about the dreaded 169.254 IP address.

Speaker 15:50

Yes, APIPA. Automatic private IP addressing.

Speaker 1 15:55

Right.

Speaker 15:56

If a computer turns on, shouts out a DHCP discover message, and nobody answers, the computer will eventually just give up and assign itself an address that starts with 169.254.

Speaker 1 16:06

Wait, hold on. If my computer isn't talking to the DHCP server, how is it getting an IP address at all? Who is giving it that 169 number?

Speaker 16:15

That is a great question. The answer is the computer itself.

Speaker 1 16:18

Really?

Speaker 16:19

Yeah. Modern operating systems have a built-in failover mechanism. If they don't hear back from a server, they randomly pick an address in that 169 range and check the local network to see if anyone else is using it. It's a last ditch effort to at least communicate with other local devices on the same switch, even if the internet is down.

Speaker 1 16:35

So if I sit down at a break-in workstation, check the IP address, and see 169.254.anything, I shouldn't even bother looking at my DNS settings or my web browser configurations.

Speaker 16:45

Exactly. Seeing a 169 address is a massive red flag that your DHCP process has failed completely. You either have a bad cable, the switch port is dead, or the DHCP server itself is offline. You have to fix the physical link or the server first.

Speaker 1 17:01

Good to know. What about the private IP ranges we do want to see?

Speaker 17:05

You need to recognize the three main classes of private addresses that are reserved for internal networks. Class A is anything starting with a 10. Class B ranges from 172.16 up to 172.31.

Speaker 1 17:17

Okay, 16 to 31.

Speaker 17:18

Yeah, people often get tripped up on that 16 to 31 range. And class C, which you probably have at home, starts with 192.168.

Speaker 1 17:26

And these addresses are paired with a subnet mask. I like to think of the subnet mask as the divider between the area code and the local phone number.

Speaker 17:33

That's a good way to look at it.

Speaker 1 17:34

It tells the computer which part of the IP address is the neighborhood network and which part is the specific host machine. The most common one you'll see on the exam is a forward slash 24, which looks like 255.25.255.0. The 255s lock in the network, leaving that final zero, the final octet free, giving you up to 254 usable hosts on that network.

Speaker 17:57

Spot on. Now, depending on how wide that network stretches, we give it different names. A LAN is a local area network like a single office building. A WAN is a wide area network linking cities together.

Speaker 1 18:09

The internet itself is the ultimate WAN, right? Exactly. A W L A N is just a wireless LAN. A P A N is a personal area network, which is basically just your Bluetooth headphones connecting to your phone. A MAN is a metropolitan area network covering a city, and that SAN is a storage area network. The study guide specifically calls this block storage.

Speaker 18:28

Oh, that's an important keyword.

Speaker 1 18:30

Yeah, basically, instead of saving normal files, a SAN writes raw blocks of data directly to enterprise hard drives without the overhead of a traditional file system. It's like a high-speed industrial warehouse compared to a normal office filing cabinet.

Speaker 18:45

Great way to put it. Now, to connect your local LAN out to the massive WAN of the Internet, you use different connection types. Fiber is the fastest and has the lowest latency because it uses light.

Speaker 1 18:56

Makes sense.

Speaker 18:57

Cable Internet uses coaxial cable to a shared neighborhood node. DSL runs over old telephone lines, but its speed drops drastically the further you live from the phone company's central office.

Speaker 1 19:08

What if you live out in a rural area?

Speaker 19:10

You might use satellite, which reaches anywhere on Earth but suffers from high latency because the signal has to physically travel out to space and back.

Speaker 1 19:17

That's quite a trip.

Speaker 19:18

Or you could use cellular 4G or 5G, which is actually getting fast enough to rival home internet. Finally, there's fixed wireless, where you mount an antenna on your roof that requires a direct, unobstructed line of sight to a provider's radio tower.

Speaker 1 19:32

With all these interconnected pieces, things are obviously bound to break. Let's talk diagnostics. Instead of just listing commands, let's walk through a scenario. A user says they have no internet. First thing I do at the command line.

Speaker 19:43

You need to check their IP address. On Windows, you type IPCON F-I-G. To see absolutely everything, including the MAC address and DNS servers, you use IPCON F-I-G space forward slash A-L-L.

Speaker 1 20:00

And for Linux or Mac?

Speaker 20:01

On Linux or a Mac, the command changes slightly. You don't use epconfig, you type IP space A-D-E-L.

Speaker 1 20:06

Okay, what if I see a valid IP address, but it's clearly from the wrong network? Like how do I force it to ask for a new one?

Speaker 20:12

You force the computer to drop its current lease with IP C O N F I G space forward slash R-E-L-E-S-C. Then you ask the DXCP server for a new one using I P C O N F I G space forward slash R-E-N-E-W.

Speaker 1 20:27

And what if the network is fine, but they can't load a specific website? Maybe the browser remembered an old outdated IP address for that site. I'd use IP C O N F-I-G space forward slash F L U S H D N S to clear out the local DNS cache, right?

Speaker 20:39

Exactly. To test raw connectivity to the web server, you use P-I-N-G. To see the exact path your data takes hop by hop across the routers, use T-R-A-C-E-R-T on Windows or the full word T R A C E R U T E on Linux.

Speaker 1 20:54

Awesome. And if I want to manually query a DNS name server to see if it's working, I use N-S-L-O-K-U-P on Windows or D-I-G on Linux. Nice. And to see every active network socket connection on the machine, I use any T S T A T space dash ANO on Windows or SS space dash T-U-N-A-P on Linux.

Speaker 21:13

But remember, a digital ping only tells you part of the story. You also need to know your physical hand tools.

Speaker 1 21:18

Right. So if a ping fails, I shouldn't just stare at the screen. I grab my physical tools. Cable testers confirm the continuity of a copper run. Crimpers are the heavy pliers you use to squeeze RJ45 plugs onto the ends of raw cable.

Speaker 21:30

Crucial for making your own cables.

Speaker 1 21:31

A punchdown tool is what you use to forcefully seat individual wires into the back of a keystone wall jack. A tone generator and probe let you inject a loud beep onto a wire so you can trace it through a messy wiring closet.

Speaker 21:43

That saves so much time.

Speaker 1 21:45

It really does. Loopback plugs trick a network card into talking to itself to see if the hardware is fried. Wi-Fi analyzers map out channel interference. And multimeters test raw voltage and resistance.

Speaker 21:57

If we connect this to the bigger picture, a truly great IT technician uses both the digital and physical tools in tandem. Software and hardware diagnostics go hand in hand. You verify the digital path, but you never fully trust it until you verify the physical link.

Speaker 1 22:14

So what does this all mean? Ultimately, networking for the Compi A is about mastering the logical layers. You have to be able to step back from a broken system and determine like, does this problem live down at the physical cable layer? Is it an IP addressing failure at the logical layer, or is it a blocked port at the protocol layer?

Speaker 22:33

That's the secret.

Speaker 1 22:34

Yeah. If you can isolate the layer, you can find the solution and you'll absolutely pass this section. You got this. Remember, this is just part two of our five-part series covering the Mountain Range Media Study Guide, so be sure to join us next time.

Speaker 22:45

Before you go though, I want to leave you with a thought to chew on.

Speaker 1 22:48

Ooh, all right.

Speaker 22:49

We spend so much time today mastering these physical cables, the crimpers, the tone probes, the meticulous layer one and layer two troubleshooting. But as the world rapidly shifts toward fully automated, AI driven, software defined networking, will understanding the physical copper and the light pulses eventually become a lost art?

Speaker 1 23:07

That's a scary thought.

Speaker 23:09

Or will that foundational physical knowledge become the only way humans can still meaningfully intervene when the automated software systems inevitably fail? Think about it.