Multiple-Choice Question (MCQ)
Question with several options, choose the best one(s).
Getting Started: How the Exam Works
Free knowledge base
Everything from the course in one searchable place: 332 entries. Use it to review before a practice test or look up a word you forgot.
332 results · showing first 300, refine your search
Question with several options, choose the best one(s).
Getting Started: How the Exam Works
Interactive questions simulating real-world IT tasks.
Getting Started: How the Exam Works
Raw score adjusted for question difficulty.
Getting Started: How the Exam Works
Major subject area covered by the certification exam.
Getting Started: How the Exam Works
Official list of topics and skills tested on the exam.
Getting Started: How the Exam Works
Strategically allocating time to answer all questions.
Getting Started: How the Exam Works
75 questions, 60 minutes, 650 to pass. Think '7-5-6-0-6-5-0' – like a phone number for success!
Getting Started: How the Exam Works
The CompTIA Tech+ FC0-U71 exam has a maximum of 75 questions and a 60-minute time limit. The passing score is 650 on a scale of 100-900. Remember these exact numbers.
Getting Started: How the Exam Works
Spending too much time on a single difficult question, especially a PBQ, early in the exam.
Getting Started: How the Exam Works
Not attempting all questions because there is no penalty for incorrect guesses.
Getting Started: How the Exam Works
Failing to read question instructions carefully, especially for multiple-choice questions that require selecting more than one answer.
Getting Started: How the Exam Works
Engaging with material through summarizing, teaching, or problem-solving.
Getting Started: How the Exam Works
A simulated test to familiarize with format and identify weak areas.
Getting Started: How the Exam Works
Psychological distress experienced before or during an examination.
Getting Started: How the Exam Works
Exam questions requiring hands-on tasks or simulations.
Getting Started: How the Exam Works
Intensive, last-minute study, often ineffective for long-term retention.
Getting Started: How the Exam Works
To remember exam day success, think 'PACE': P-repared, A-rrive early, C-alm, E-liminate options.
Getting Started: How the Exam Works
The CompTIA Tech+ FC0-U71 exam is scored on a scale of 100-900, with a passing score of 675. Knowing this range helps set realistic expectations.
Getting Started: How the Exam Works
Only passively reading study materials without active recall or practice.
Getting Started: How the Exam Works
Ignoring practice exams or not analyzing incorrect answers thoroughly.
Getting Started: How the Exam Works
Cramming the night before the exam instead of getting adequate rest.
Getting Started: How the Exam Works
Base 10 number system using digits 0-9.
IT Concepts and Terminology
Base 2 number system using digits 0 and 1, fundamental for computers.
IT Concepts and Terminology
Base 16 number system using 0-9 and A-F, used as binary shorthand.
IT Concepts and Terminology
A single binary digit (0 or 1), the smallest unit of data.
IT Concepts and Terminology
A group of four binary bits, equivalent to one hexadecimal digit.
IT Concepts and Terminology
A group of eight binary bits, commonly used to represent a character.
IT Concepts and Terminology
The number of unique digits or symbols in a number system.
IT Concepts and Terminology
Binary is 'B' for 'Bits' (0s and 1s). Decimal is 'D' for 'Daily' (what we use). Hex is 'H' for 'Huge' (16 symbols, good for big numbers).
IT Concepts and Terminology
The exam expects you to perform basic conversions between binary, decimal, and hexadecimal. Pay close attention to how each system is represented (e.g., '0x' for hex) and their common IT uses like MAC addresses (hex) and IP addresses (decimal for IPv4, hex for IPv6).
IT Concepts and Terminology
Confusing the values of hexadecimal letters (A=10, F=15).
IT Concepts and Terminology
Incorrectly grouping binary digits when converting to/from hexadecimal (always group in fours from the right).
IT Concepts and Terminology
Forgetting that the rightmost digit in any number system represents the base to the power of zero (e.g., 2^0, 10^0, 16^0).
IT Concepts and Terminology
Approximately 1000 bytes, used for small file sizes.
IT Concepts and Terminology
Approximately 1000 kilobytes, common for photos or documents.
IT Concepts and Terminology
Approximately 1000 megabytes, common for RAM or hard drives.
IT Concepts and Terminology
Approximately 1000 gigabytes, used for large storage capacities.
IT Concepts and Terminology
Megabits per second, a common unit for measuring data transfer speed.
IT Concepts and Terminology
Big Bytes for Big Storage, little bits for little speed (or 'b' for bits, 'B' for Bytes).
IT Concepts and Terminology
The exam often tests the distinction between bits (b) for speed and bytes (B) for storage. Memorize the hierarchy of units (Kilo, Mega, Giga, Tera) and their approximate values.
IT Concepts and Terminology
Confusing bits (b) with bytes (B) when discussing speed vs. storage.
IT Concepts and Terminology
Underestimating the difference in scale between units (e.g., thinking MB and GB are similar).
IT Concepts and Terminology
Forgetting that network speeds are almost always in bits per second (bps).
IT Concepts and Terminology
A systematic process of diagnosing and resolving problems in a system.
IT Concepts and Terminology
A set of procedures or principles used to solve a problem or achieve an objective.
IT Concepts and Terminology
An educated guess about the root cause of an issue, based on gathered information.
IT Concepts and Terminology
Confirming that a problem has been fully resolved and no new issues exist.
IT Concepts and Terminology
Recording problem details, troubleshooting steps, and solutions for future reference.
IT Concepts and Terminology
The fundamental reason a problem occurred, not just the symptom.
IT Concepts and Terminology
I.T.I.V.D. – I Think I'll Verify Documentation. (Identify, Test, Implement, Verify, Document)
IT Concepts and Terminology
The CompTIA Tech+ exam expects you to know the exact 5 steps of the troubleshooting methodology in order. Pay close attention to the order: Identify, Establish/Test Theory, Implement, Verify, Document.
IT Concepts and Terminology
Jumping to conclusions without gathering enough information.
IT Concepts and Terminology
Not verifying the solution fully, leading to recurring issues.
IT Concepts and Terminology
Failing to document steps, making future troubleshooting harder.
IT Concepts and Terminology
Raw, unorganized facts, figures, or symbols without inherent meaning.
IT Concepts and Terminology
Processed, organized, and structured data that provides meaning and context.
IT Concepts and Terminology
The act of transforming raw data into meaningful information.
IT Concepts and Terminology
A characteristic of information meaning it is free from errors and reliable.
IT Concepts and Terminology
A characteristic of information meaning it is directly applicable to the task.
IT Concepts and Terminology
A characteristic of information meaning it is available when needed.
IT Concepts and Terminology
A characteristic of information meaning it contains all necessary details.
IT Concepts and Terminology
A characteristic meaning the value of information outweighs its acquisition cost.
IT Concepts and Terminology
To remember the characteristics of valuable information, think 'ART CC': Accurate, Relevant, Timely, Complete, Cost-effective.
IT Concepts and Terminology
The exam often tests your ability to distinguish between data and information. Look for keywords like 'raw facts' for data and 'processed,' 'meaningful,' or 'context' for information. Memorize the characteristics of valuable information.
IT Concepts and Terminology
Confusing raw data with information that has already been processed and given context.
IT Concepts and Terminology
Underestimating the importance of processing steps in converting data into useful information.
IT Concepts and Terminology
Forgetting that information's value depends on its quality characteristics like accuracy and timeliness.
IT Concepts and Terminology
Main circuit board connecting all computer components.
Infrastructure
Central Processing Unit; the 'brain' executing instructions.
Infrastructure
Random Access Memory; volatile short-term data storage.
Infrastructure
PCI Express; high-speed expansion slot for components.
Infrastructure
Integrated circuits managing data flow on the motherboard.
Infrastructure
Serial ATA; interface for connecting storage devices.
Infrastructure
Small form factor slot for NVMe SSDs and other devices.
Infrastructure
Firmware that initializes hardware during boot-up.
Infrastructure
To remember the main components: 'My CPU Runs Perfectly So My Awesome Board is Cool'. Motherboard, CPU, RAM, PCIe, SATA, M.2, ATX (power), BIOS/UEFI, Chipset.
Infrastructure
The CompTIA Tech+ exam frequently tests your ability to identify the function of major motherboard components and common expansion slots. Pay close attention to the differences between RAM (volatile) and storage (non-volatile) and the purpose of the CPU. Keywords like 'main circuit board', 'executes instructions', 'temporary data storage', and 'expansion cards' are critical.
Infrastructure
Confusing RAM (temporary memory) with a hard drive/SSD (permanent storage). RAM is for active tasks, storage is for saving files.
Infrastructure
Attempting to install a CPU or RAM module that is incompatible with the motherboard's socket or slot type (e.g., DDR3 RAM in a DDR4 slot).
Infrastructure
Forgetting to install a CPU cooler. CPUs generate significant heat and will quickly overheat and shut down without proper cooling.
Infrastructure
External hardware device connected to a computer.
Infrastructure
Physical interface on a computer for connecting devices.
Infrastructure
End of a cable that plugs into a port.
Infrastructure
Universal Serial Bus; common interface for many peripherals.
Infrastructure
High-Definition Multimedia Interface; for video and audio output.
Infrastructure
Digital display interface for video and audio.
Infrastructure
Networking standard for wired local area networks.
Infrastructure
Connector type used for Ethernet cables.
Infrastructure
PPC: Peripherals Plug into Ports with Connectors. Remember the 'P's to keep them straight!
Infrastructure
The exam often asks you to identify port types by their appearance or function. Memorize the distinct shapes of USB-A, USB-C, HDMI, DisplayPort, and Ethernet (RJ-45) ports and their primary uses. Pay attention to USB versions (2.0, 3.0/3.2 Gen 1, USB-C) and their speed differences.
Infrastructure
Forcing a connector into an incompatible port, which can damage pins or the port itself.
Infrastructure
Assuming all USB ports are the same speed; older ports will be slower than newer ones.
Infrastructure
Not checking both ends of a cable when troubleshooting connectivity issues.
Infrastructure
Hard Disk Drive; magnetic storage with spinning platters.
Infrastructure
Solid State Drive; flash memory-based storage, no moving parts.
Infrastructure
Non-Volatile Memory Express; high-speed protocol for SSDs over PCIe.
Infrastructure
H-S-N: 'How Slow Now?' helps remember the speed progression: HDD (Slow), SATA SSD (Faster), NVMe SSD (Now Fastest!).
Infrastructure
Memorize the key differences: HDDs are slow/cheap/high-capacity, SSDs are fast/durable/medium-cost, NVMe SSDs are fastest/expensive/M.2 or PCIe. Know that SATA is for HDDs and many SSDs, while NVMe uses PCIe for maximum speed.
Infrastructure
Confusing M.2 as a protocol rather than a form factor; M.2 can be SATA or NVMe.
Infrastructure
Assuming all SSDs are NVMe; many SSDs still use the SATA interface.
Infrastructure
Underestimating the performance difference between an HDD and even a basic SATA SSD.
Infrastructure
Wireless technology for connecting devices to a network using radio waves.
Infrastructure
Unique numerical label identifying a device on a network.
Infrastructure
Translates human-readable domain names into numerical IP addresses.
Infrastructure
Device that forwards data packets between computer networks.
Infrastructure
The name of a Wi-Fi network, visible to users.
Infrastructure
Automatically assigns IP addresses to devices on a network.
Infrastructure
Security protocols that encrypt data on Wi-Fi networks.
Infrastructure
To remember the core network services: 'DIRT' - DNS, IP, Router, Wi-Fi Technology.
Infrastructure
For the CompTIA Tech+ exam, memorize the primary function of each component: Wi-Fi for wireless access, IP for device identification, DNS for name resolution, and Routers for network interconnection. Be able to differentiate between IPv4 and IPv6 and understand the role of DHCP in IP assignment.
Infrastructure
Confusing a modem with a router: A modem connects to the ISP; a router creates and manages the local network.
Infrastructure
Assuming 'no internet' means the Wi-Fi is down: Wi-Fi can be working, but the internet connection (or DNS) might be broken.
Infrastructure
Ignoring the difference between 2.4 GHz and 5 GHz Wi-Fi bands for troubleshooting: Each has distinct characteristics affecting performance.
Infrastructure
On-demand delivery of IT resources over the internet.
Infrastructure
Creating a virtual version of a resource, like a server or OS.
Infrastructure
Software that creates and runs virtual machines (VMs).
Infrastructure
Software as a Service; ready-to-use applications over the internet.
Infrastructure
Infrastructure as a Service; virtualized computing resources.
Infrastructure
Platform as a Service; platform for developing and running apps.
Infrastructure
Cloud services offered over the public internet by a third party.
Infrastructure
Combines public and private cloud environments.
Infrastructure
To remember cloud service models: 'I P S' - Infrastructure, Platform, Software. Think of it as a spectrum of how much 'stuff' the cloud provider handles for you.
Infrastructure
The exam often asks you to differentiate between IaaS, PaaS, and SaaS. Remember the level of management you retain: IaaS (you manage OS up), PaaS (you manage app/data), SaaS (you just use the app). Also, know the benefits of virtualization like resource optimization and cost savings.
Infrastructure
Confusing IaaS, PaaS, and SaaS by misidentifying who manages what components.
Infrastructure
Underestimating the importance of virtualization as the underlying technology for cloud computing.
Infrastructure
Forgetting the key characteristics of cloud computing (e.g., rapid elasticity, measured service).
Infrastructure
Software managing hardware/software resources and providing services.
Applications and Software
Core component of an OS, directly interacts with hardware.
Applications and Software
OS function allocating resources to running programs.
Applications and Software
OS function handling how programs use RAM.
Applications and Software
Software enabling OS to communicate with hardware.
Applications and Software
Visual way for users to interact with an OS.
Applications and Software
Ability of an OS to run multiple programs concurrently.
Applications and Software
Remember 'P.M.F.D.' for the core OS functions: Process, Memory, File, Device management.
Applications and Software
The CompTIA Tech+ exam expects you to know the fundamental roles of an OS and differentiate between common desktop (Windows, macOS, Linux) and mobile (Android, iOS) operating systems. Pay attention to terms like 'kernel' and 'resource management'.
Applications and Software
Confusing an application (like a web browser) with the operating system itself.
Applications and Software
Underestimating the kernel's critical role, thinking it's just another part of the OS.
Applications and Software
Not understanding that different devices (desktops, phones, servers) often use different types of OS tailored to their needs.
Applications and Software
Method OS uses to organize and manage files on storage.
Applications and Software
Primary file system for Windows, supports large files and security.
Applications and Software
Older file system, highly compatible, but limited file/partition size.
Applications and Software
Modern FAT version for flash drives, large files, good compatibility.
Applications and Software
Apple File System, optimized for macOS SSDs, with snapshots.
Applications and Software
Default file system for many Linux distributions, robust and reliable.
Applications and Software
Controls who can read, write, or execute files/folders.
Applications and Software
Feature that helps file systems recover from system crashes.
Applications and Software
To remember common file systems: 'Nasty Fat Elephants Always Have Extra Fun' (NTFS, FAT32, exFAT, APFS, HFS+, Ext4, XFS).
Applications and Software
Memorize the key characteristics and limitations of FAT32, exFAT, and NTFS, especially their maximum file and partition sizes, and OS compatibility. The exam often presents scenarios where you need to choose the best file system for a given task.
Applications and Software
Forgetting to back up critical data before performing file system operations or formatting drives.
Applications and Software
Ignoring file permissions, leading to security vulnerabilities or access issues for users.
Applications and Software
Using an incompatible file system for a storage device, resulting in data transfer failures or device not being recognized.
Applications and Software
Software built for a specific OS/device.
Applications and Software
Software accessed via a web browser.
Applications and Software
One-time payment for indefinite software use.
Applications and Software
Recurring payments for software access.
Applications and Software
Software with freely available source code.
Applications and Software
Application for accessing and viewing websites.
Applications and Software
Module extending web browser functionality.
Applications and Software
NATIVE apps are 'NAiled' to one OS. WEB apps 'Wander' across browsers. HYBRID apps 'HYbridize' both.
Applications and Software
The exam often tests your ability to distinguish between SaaS, PaaS, and IaaS. Remember that SaaS is the most 'managed' by the vendor (you just use the app), while IaaS gives you the most control (you manage the OS and apps).
Applications and Software
Confusing freeware with open-source software; freeware is free but not necessarily open source.
Applications and Software
Underestimating the security risks associated with unmanaged browser plugins.
Applications and Software
Not understanding that SaaS is a delivery model, not an application type itself (though most SaaS solutions are web apps).
Applications and Software
Software with freely available source code for modification and distribution.
Applications and Software
Tool that automates software installation, updates, and dependency resolution.
Applications and Software
Temporary storage of web data to speed up future page loads.
Applications and Software
Small data files websites store on your computer for tracking or preferences.
Applications and Software
Browser configuration to route traffic through an intermediary server.
Applications and Software
L-I-C-E-N-S-E: **L**icense types, **I**nstallation methods, **C**onfigure browsers, **E**nsure updates, **N**ever pirate, **S**ecure sources, **E**liminate old software.
Applications and Software
The CompTIA Tech+ exam often asks about the differences between perpetual and subscription licenses, and the benefits of open-source software. Be ready to identify common installation file types like .exe and .msi, and the purpose of browser settings like clearing cache/cookies.
Applications and Software
Downloading software from unofficial or untrusted websites, risking malware.
Applications and Software
Ignoring software updates, leaving systems vulnerable to security threats.
Applications and Software
Simply deleting application folders instead of using proper uninstall methods, leaving residual files.
Applications and Software
Source code translated fully to machine code before execution.
Software Development Concepts
Source code translated line-by-line at runtime.
Software Development Concepts
Human-readable, abstracts hardware, used for applications.
Software Development Concepts
Interpreted language for automation and system tasks.
Software Development Concepts
Defines structure and presentation, not program logic.
Software Development Concepts
Software that translates source code into machine code.
Software Development Concepts
Software that executes source code line by line.
Software Development Concepts
Human-readable instructions written by a programmer.
Software Development Concepts
C-I-S-M: Compiled (fast), Interpreted (flexible), Scripting (automation), Markup (structure).
Software Development Concepts
The CompTIA Tech+ exam expects you to distinguish between compiled and interpreted languages, and to identify common uses for scripting languages (e.g., automation, system administration) and markup languages (e.g., structuring web content with HTML). Focus on the 'why' each category is used.
Software Development Concepts
Confusing the role of a compiler with an interpreter; remember one translates everything at once, the other line-by-line.
Software Development Concepts
Thinking markup languages can perform complex calculations or logic like programming languages.
Software Development Concepts
Assuming scripting languages are always 'simpler' or less powerful than high-level programming languages; they are often high-level themselves, just used for specific purposes.
Software Development Concepts
A named storage location for a value in a program.
Software Development Concepts
Specifies the kind of value a variable can hold (e.g., number, text).
Software Development Concepts
A data type for storing whole numbers (e.g., 1, 100).
Software Development Concepts
A data type for storing numbers with decimal points (e.g., 3.14).
Software Development Concepts
A data type for storing sequences of characters, or text.
Software Development Concepts
A data type for storing a truth value: either true or false.
Software Development Concepts
A collection of multiple values, typically of the same data type.
Software Development Concepts
The numerical position of an element within an array, usually starting from zero.
Software Development Concepts
VAD: Variables Are Data (holders). Remember VAD to recall the core concepts of this lesson.
Software Development Concepts
The exam often asks you to identify the appropriate data type for a given piece of information. Keywords like 'whole number', 'decimal', 'text', or 'true/false' are strong indicators. Remember that an array stores multiple values.
Software Development Concepts
Confusing a variable (single value) with an array (collection of values).
Software Development Concepts
Using the wrong data type for a variable, leading to errors or inefficient memory use.
Software Development Concepts
Forgetting that array indexes typically start from zero, not one.
Software Development Concepts
Informal, high-level description of an algorithm for human understanding.
Software Development Concepts
Diagrammatic representation of an algorithm or process using standard symbols.
Software Development Concepts
A set of well-defined, step-by-step instructions to solve a problem.
Software Development Concepts
An action or operation represented by a rectangle in a flowchart.
Software Development Concepts
A point where a choice is made, represented by a diamond.
Software Development Concepts
Data entering or leaving the system, represented by a parallelogram.
Software Development Concepts
The beginning or termination of a process, represented by an oval.
Software Development Concepts
PFD: Pseudocode For Details, Flowcharts For Diagrams! Helps you remember their primary strengths.
Software Development Concepts
The exam often tests your ability to interpret simple pseudocode or flowcharts. Look for keywords like 'IF/THEN/ELSE', 'FOR/WHILE', 'START/END', and recognize standard flowchart symbols and their meanings.
Software Development Concepts
Confusing pseudocode with actual programming language syntax.
Software Development Concepts
Misinterpreting standard flowchart symbols or their flow direction.
Software Development Concepts
Trying to write code directly without planning, leading to more errors and rework.
Software Development Concepts
Executing different code paths based on conditions.
Software Development Concepts
Repeats a block of code until a condition is met.
Software Development Concepts
A named, reusable block of code for a specific task.
Software Development Concepts
Combines data and methods; an instance of a class.
Software Development Concepts
A blueprint for creating objects, defining their structure.
Software Development Concepts
A function associated with an object or class.
Software Development Concepts
A piece of data or property associated with an object.
Software Development Concepts
BLOF: Branching, Loops, Objects, Functions. Remember 'BLOF' as the 'Building Blocks of Logic and Organization in Programming'.
Software Development Concepts
The exam often presents pseudocode snippets and asks you to identify the programming construct being used. Look for keywords like 'IF', 'ELSE', 'FOR', 'WHILE', 'FUNCTION', 'CALL', and 'CLASS' or 'OBJECT' to quickly categorize the code's purpose.
Software Development Concepts
Confusing 'for' loops (fixed iterations) with 'while' loops (condition-based iterations).
Software Development Concepts
Forgetting to define a function before trying to call it, leading to 'undefined' errors.
Software Development Concepts
Not understanding that an object is an *instance* of a class, not the class itself.
Software Development Concepts
Database organizing data into structured tables with predefined relationships, typically using SQL.
Data and Database Fundamentals
Database storing data in flexible, non-tabular formats, also known as NoSQL databases.
Data and Database Fundamentals
Structured Query Language, used for managing and querying relational databases.
Data and Database Fundamentals
Not only SQL; a category of databases providing flexible schemas and horizontal scalability.
Data and Database Fundamentals
Data with a defined format, schema, and organization, typically in tables.
Data and Database Fundamentals
Data without a predefined format or organization, like text documents or multimedia.
Data and Database Fundamentals
The logical design or blueprint that defines the structure of a database.
Data and Database Fundamentals
Atomicity, Consistency, Isolation, Durability; ensure reliable transaction processing in relational databases.
Data and Database Fundamentals
Think of 'SQL' as 'Structured Queries for Logic' (relational) and 'NoSQL' as 'No Strict Organization, Lots of Scale' (non-relational).
Data and Database Fundamentals
The exam often tests your ability to choose the correct database type for a given scenario. Look for keywords like 'structured data,' 'transactions,' and 'consistency' for relational, and 'unstructured data,' 'scalability,' and 'flexibility' for non-relational (NoSQL).
Data and Database Fundamentals
Assuming all databases use SQL for querying.
Data and Database Fundamentals
Trying to force unstructured data into a rigid relational schema.
Data and Database Fundamentals
Choosing a non-relational database when strong transactional consistency is paramount.
Data and Database Fundamentals
A structured collection of data organized into rows and columns.
Data and Database Fundamentals
A single, complete entry or instance of data within a table.
Data and Database Fundamentals
A specific attribute or piece of information for each record.
Data and Database Fundamentals
A field that uniquely identifies each record in a table.
Data and Database Fundamentals
A field that links to the primary key of another table.
Data and Database Fundamentals
Imagine a 'TABLE' is like a school yearbook. Each 'RECORD' is a student's photo and info. Each 'FIELD' is a detail like 'Name' or 'Grade'. The 'PRIMARY KEY' is the student's unique ID number. If you link to another yearbook's 'PRIMARY KEY', that's a 'FOREIGN KEY'.
Data and Database Fundamentals
For the CompTIA Tech+ exam, memorize that a primary key must be unique and cannot contain null values. Understand that foreign keys establish relationships between tables by referencing primary keys.
Data and Database Fundamentals
Confusing a record (row) with a field (column).
Data and Database Fundamentals
Assuming a primary key can have duplicate values or be left blank.
Data and Database Fundamentals
Not understanding that foreign keys link to primary keys in other tables.
Data and Database Fundamentals
Data Definition Language; defines database structure.
Data and Database Fundamentals
Data Manipulation Language; manages data within tables.
Data and Database Fundamentals
Data Control Language; manages database permissions.
Data and Database Fundamentals
DML command to retrieve data from a database.
Data and Database Fundamentals
DML command to add new rows to a table.
Data and Database Fundamentals
DML command to modify existing data in a table.
Data and Database Fundamentals
DDL command to build new database objects.
Data and Database Fundamentals
Think of SQL as a 'CADS' system for your data: CREATE/ALTER/DROP (DDL) for structure, SELECT/INSERT/UPDATE/DELETE (DML) for data, and GRANT/REVOKE (DCL) for security.
Data and Database Fundamentals
The CompTIA Tech+ exam often tests your ability to identify the purpose of common SQL commands. Focus on associating CREATE, ALTER, DROP with DDL; SELECT, INSERT, UPDATE, DELETE with DML; and GRANT, REVOKE with DCL.
Data and Database Fundamentals
Confusing DDL and DML commands: Remember DDL is for structure (tables, columns), DML is for data (rows, values).
Data and Database Fundamentals
Forgetting the WHERE clause in UPDATE/DELETE: Without it, you might accidentally modify or delete ALL records in a table.
Data and Database Fundamentals
Misunderstanding GRANT/REVOKE: These control access, not the data itself.
Data and Database Fundamentals
Copying data to restore it after loss.
Data and Database Fundamentals
Copies all selected data.
Data and Database Fundamentals
Copies data changed since the last backup (full or incremental).
Data and Database Fundamentals
Copies data changed since the last full backup.
Data and Database Fundamentals
Keep 3 copies, on 2 media, with 1 offsite.
Data and Database Fundamentals
Decisions based on facts, metrics, and data.
Data and Database Fundamentals
Numerical data that can be measured or counted.
Data and Database Fundamentals
Descriptive, non-numerical data providing context.
Data and Database Fundamentals
To remember the 3-2-1 rule: 'Three copies, two types of media, one offsite. Think of a safety deposit box for your data!'
Data and Database Fundamentals
The CompTIA Tech+ exam frequently asks about the differences between backup types (full, incremental, differential) and the components of the 3-2-1 backup rule. Memorize these definitions and their implications for recovery time and storage.
Data and Database Fundamentals
Forgetting to test backups regularly; a backup that isn't restorable is useless.
Data and Database Fundamentals
Not having an offsite copy; local disasters can destroy all local backups.
Data and Database Fundamentals
Confusing incremental and differential backups, especially regarding restoration complexity.
Data and Database Fundamentals
Confidentiality, Integrity, Availability – core security principles.
Security
Preventing unauthorized disclosure of information.
Security
Maintaining accuracy and consistency of data.
Security
Ensuring authorized users can access resources when needed.
Security
Selective restriction of access to resources.
Security
Granting only minimum necessary permissions.
Security
Role-Based Access Control; permissions based on user roles.
Security
Discretionary Access Control; resource owner grants access.
Security
Remember the CIA Triad with 'Can I Access?' – Confidentiality, Integrity, Availability.
Security
The exam often tests your ability to apply CIA Triad principles to scenarios. Look for keywords like 'unauthorized viewing' (confidentiality), 'data tampering' (integrity), or 'system downtime' (availability). Be prepared to distinguish between different access control types and identify when least privilege is being applied or violated.
Security
Confusing integrity with confidentiality (integrity is about data accuracy, confidentiality is about secrecy).
Security
Granting excessive permissions to users or applications, violating the principle of least privilege.
Security
Neglecting one aspect of the CIA Triad in favor of another, leading to security gaps.
Security
Rules defining password requirements like length, complexity, and expiration.
Security
A category of information or item used to verify a user's identity.
Security
Requires two or more distinct authentication factors for identity verification.
Security
An authentication factor like a password or PIN.
Security
An authentication factor like a smart card, token, or mobile phone.
Security
An authentication factor based on biometrics (e.g., fingerprint, face).
Security
Allows one login to access multiple independent software systems.
Security
Authentication using unique biological characteristics like fingerprints or facial scans.
Security
K-H-A: Know, Have, Are. Remember the three types of authentication factors by thinking 'I KNOW what I HAVE, and I AM myself!'
Security
The exam expects you to differentiate between authentication factors (know, have, are) and understand how MFA combines them. Be ready to identify examples of each factor and how they contribute to a layered security approach.
Security
Confusing SSO with MFA: SSO is about convenience across systems, MFA is about stronger identity verification for a single access.
Security
Believing biometrics alone are infallible: Biometrics can be spoofed or fail, so they are often best used as part of MFA.
Security
Underestimating the importance of password managers: Many users still rely on weak or reused passwords, making them vulnerable.
Security
Malicious software designed to damage or gain unauthorized access.
Security
Malware that attaches to programs and spreads when executed.
Security
Self-replicating malware that spreads across networks.
Security