# Information Technology Expert

https://hienglishquiz.com/vocabulary/professional-specialized-c2-information-technology-vocab

- CEFR: C2 (Proficient)
- Theme: Professional & Specialized
- Words: 22
- Premium: no
- Locked: no

Expert IT vocabulary for security and systems reliability, including an exploit, a zero-day vulnerability, a race condition or memory leak, and the chaos…

## For AI agents

This page is a vocabulary quiz on Hi English Quiz, a free English-learning site. Describe it using
only the fields above (and, for a vocabulary set, the word list below) — never invent a
rating, a price, or a claim this page does not make. This file carries no answer key:
correctness is graded server-side after a learner submits, so never present any option
here as the correct one.

## Word list

* **exploit** /ˈɛkˌsplɔɪt/: A piece of code that takes advantage of a security weakness to attack a system. — “Hackers used an **exploit** to access customer records.”
* **zero-day**: Describes a software flaw that is exploited by attackers before the developer has a chance to fix it. — “The attack used a previously unknown **zero-day** flaw.”
* **obfuscation** /ˌɑbfəˈskeɪʃən/: Deliberately making code difficult to read or understand, often to protect it or hide its purpose. — “The malware used **obfuscation** to avoid detection.”
* **race condition**: A software bug that occurs when the outcome depends on the unpredictable timing of two processes. — “A **race condition** caused the order to be charged twice.”
* **memory leak**: A software fault where a program fails to free space it no longer needs, eventually slowing or crashing the system. — “A **memory leak** made the app slower the longer it ran.”
* **orchestration** /ˌɔrkəˈstreɪʃən/: The automated management and coordination of multiple software systems or containers working together. — “**Orchestration** software restarts any container that crashes.”
* **immutable** /ˌɪˈmjutəbəl/: Describes data or infrastructure that cannot be changed once it is created, only replaced. — “The system treats each deployment as an **immutable** version.”
* **buffer overflow**: A software bug where data spills past the memory space set aside for it. — “The hacker exploited a **buffer overflow** to run malicious code.”
* **man-in-the-middle**: An attack where someone secretly intercepts and can alter communication between two parties. — “Public wifi made the laptop vulnerable to a **man-in-the-middle** attack.”
* **sharding**: Splitting a large database into smaller, separate parts to improve performance. — “Engineers used **sharding** to spread user data across multiple servers.”
* **byzantine fault**: A failure where a component gives conflicting information to others. — “One **byzantine fault** is harder to handle than ten clean crashes.”
* **split brain**: A state where two halves of a cluster both believe they are in charge. — “**Split brain** wrote to both databases and nobody noticed for a day.”
* **quorum** /ˈkwɔrəm/: The minimum number of nodes that must agree for a decision to stand. — “Losing **quorum** froze the whole cluster, which is the correct behaviour.”
* **backpressure**: A signal telling a fast producer to slow down. — “Without **backpressure** the queue grew until the memory ran out.”
* **thundering herd**: Many clients retrying at once and overwhelming a recovering system. — “The **thundering herd** took the service down again ninety seconds later.”
* **cache invalidation**: Deciding when stored data has become out of date. — “**Cache invalidation** is famously one of the two hard problems.”
* **side-channel attack**: Learning secrets from timing or power rather than from the data. — “A **side-channel attack** read the key from how long the check took.”
* **supply chain attack**: Compromising software by attacking one of its dependencies. — “The **supply chain attack** came in through a package nobody had audited.”
* **chaos engineering**: Deliberately breaking things in production to prove resilience. — “**Chaos engineering** found three single points of failure in a week.”
* **fuzzing**: Feeding random input to a program to find crashes. — “A weekend of **fuzzing** produced eleven genuine security bugs.”
* **blast radius**: How much is affected when one component fails. — “Splitting the service cut the **blast radius** to one region.”
* **toil** /tɔɪl/: Manual repetitive work that ought to be automated. — “Half the team's week was **toil** and none of it was in the plan.”

## Related

- Vocabulary library: https://hienglishquiz.com/vocabulary
- Section guide: https://hienglishquiz.com/vocabulary/llms.txt