ITEE FE flashcards
ITEE FE · Build recall with a focused review session.
31 cards. Read the term and the definition here. The deck at the top of this page is optional.
- IT governance archetype
- A pattern describing who holds decision rights over IT. Common forms are business monarchy, IT monarchy, federal, duopoly, and anarchy.
- Net present value
- The sum of all project cash flows discounted to today at the required rate of return. A positive value means the project adds value.
- Payback period
- The elapsed time until cumulative benefits equal cumulative costs. It ignores cash flows after the break-even point and ignores the time value of money.
- Risk exposure
- The product of an event's probability and its monetary impact. Mitigation actions reduce probability; contingency plans reduce or absorb impact.
- RACI matrix
- A chart mapping activities to roles marked responsible, accountable, consulted, or informed. Exactly one role should be accountable for each activity.
- Total cost of ownership
- The full lifetime cost of an asset, including acquisition, licensing, operation, support, and retirement, rather than only the initial purchase price.
- Service level agreement
- A contract stating measurable service targets such as availability, response time, and resolution time, together with remedies when targets are missed.
- Weighted scoring model
- A selection technique that assigns weights to criteria such as value, risk, and cost, scores each option, and ranks options by total weighted score.
- Strategic alignment
- The condition in which IT objectives and initiatives trace directly to stated business goals, so every funded project supports a business outcome.
- OSI model
- A seven-layer reference model: physical, data link, network, transport, session, presentation, and application. Each layer serves the layer above it.
- TCP versus UDP
- TCP is connection-oriented, sequencing segments and retransmitting lost data. UDP is connectionless, adds no delivery guarantee, and has lower overhead.
- Subnet mask
- A bit pattern that divides an IP address into network and host portions. Bits set to one identify the network part.
- IPv6 address size
- IPv6 addresses are 128 bits long, compared with 32 bits for IPv4, which greatly expands the available address space.
- Symmetric encryption
- An encryption method using a single shared key for both encryption and decryption. It is fast but requires secure key distribution.
- Asymmetric encryption
- An encryption method using a public key to encrypt and a matching private key to decrypt, which also enables key exchange and digital signatures.
- Digital signature
- A value created by hashing a message and encrypting the hash with the sender's private key, providing integrity and non-repudiation to receivers.
- RAID 5
- A storage configuration that stripes data across disks with distributed parity. It survives the failure of one disk and needs at least three disks.
- Hypervisor
- Software that creates and runs virtual machines on a physical host, isolating guest operating systems and sharing CPU, memory, and storage.
- CIA triad
- Three core security goals: confidentiality prevents unauthorized disclosure, integrity prevents unauthorized modification, and availability ensures timely authorized access.
- Domain Name System
- A hierarchical naming service, usually on port 53, that resolves human-readable host names into IP addresses used for routing.
- Waterfall model
- A sequential development approach moving through requirements, design, implementation, testing, and maintenance, with formal sign-off and costly late changes.
- Agile iteration
- A short fixed timebox that produces a potentially shippable increment. Backlog items are reordered before each iteration by business value.
- Scrum roles
- The three Scrum accountabilities are product owner, who orders the backlog; scrum master, who enables the process; and the development team.
- Sprint backlog
- The set of product backlog items selected for one sprint plus the team's plan for delivering them within the timebox.
- Continuous integration
- A practice in which developers merge changes to a shared mainline frequently, triggering automated build and test on every commit.
- Continuous delivery
- A practice keeping the mainline always in a deployable state, so release to production is a routine decision rather than a large project.
- Test pyramid
- A guideline favoring many fast unit tests, fewer integration tests, and few slow end-to-end tests to balance feedback speed and confidence.
- Trunk-based development
- A branching approach where developers commit to one shared trunk using short-lived branches, reducing merge conflicts and integration delay.
- Infrastructure as code
- Managing servers and environments through versioned declarative files, making provisioning repeatable, reviewable, and auditable.
- Incident management
- The process of restoring service quickly after disruption, then investigating root cause and recording preventive actions in a review.
- Regression testing
- Re-running selected tests after a change to confirm that existing functionality still works and that no new defects were introduced.