Build fluency in the vocabulary of I2C vs SPI buses.
0 / 5 completed
1 / 5
A teammate explains that a microcontroller talks to several onboard sensors using either I2C, a two-wire multi-drop bus where every device shares the same two lines and is selected by a unique address, or SPI, a four-wire full-duplex bus that runs faster but needs its own dedicated chip-select line to each device instead of an address. What is being described?
The I2C and SPI bus protocols is exactly what is described here. A DNS zone transfer is an unrelated concept about replicating name server records. Understanding I2C vs SPI buses is exactly why it comes up so often in real engineering discussions of this kind of problem.
2 / 5
During a design review, the team adopts I2C vs SPI buses, specifically to gain a concrete benefit. Which capability does this provide?
I2C vs SPI buses here provides multiple sensors sharing a small number of wires, since I2C multiplexes many devices onto just two address-selected lines and SPI multiplexes many devices onto shared data lines distinguished by a per-device chip-select. Wiring a separate dedicated set of data lines from the microcontroller to every single sensor, with no shared bus at all is the alternative this avoids. This behavior is exactly why I2C vs SPI buses is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a system relies on wiring a separate dedicated set of data lines from the microcontroller to every single sensor, with no shared bus at all, instead of using I2C vs SPI buses. What does this represent?
This is a missed I2C vs SPI buses-opportunity, since I2C vs SPI buses would provide multiple sensors sharing a small number of wires, since I2C multiplexes many devices onto just two address-selected lines and SPI multiplexes many devices onto shared data lines distinguished by a per-device chip-select. A cache eviction policy is an unrelated concept about discarded cache entries. This pattern is exactly the kind of gap a reviewer flags once the tradeoffs are understood.
4 / 5
An incident report shows a board ran out of microcontroller pins because the design wired a separate dedicated data line to every sensor instead of sharing a bus among them. What practice would prevent this?
Moving the sensors onto a shared I2C bus, distinguished by address, or a shared SPI bus, distinguished by chip-select, instead of a dedicated wire set per sensor. Continuing the prior approach regardless of the risk it has already caused is exactly what led to the incident described here. This fix is the standard remedy once the root cause is confirmed.
5 / 5
During a PR review, a teammate asks why the team reaches for I2C vs SPI buses instead of wiring a separate dedicated set of data lines from the microcontroller to every single sensor, with no shared bus at all. What is the reasoning?
I2C trades some speed for needing only two shared wires regardless of device count, while SPI trades one extra chip-select wire per device for higher throughput and full-duplex transfer, while a dedicated wire set per device avoids any bus-arbitration complexity but consumes far more pins as the number of devices grows. This is exactly why I2C vs SPI buses is favored in scenarios that call for it, while the alternative remains acceptable in simpler cases that don't.
What does the "I2C vs SPI buses Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to i2c vs spi buses vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.