CompTIA Tech+ — Practice Questions and Mock Exam

Read the scenario for its two ingredients: servers the company owns and operates in its own data center, plus capacity rented from a public provider for peaks. A deployment made of two or more distinct cloud infrastructures that stay separate entities while being bound together so data and applications can move between them is exactly what hybrid means, and bursting to absorb peak load is the textbook example.

Each distractor drops one ingredient. Public cloud alone would put the whole workload on someone else's infrastructure, with nothing left in the company data center. Private cloud alone is infrastructure provisioned for a single organization, which describes the on-premises half but not the rented capacity. Community cloud is shared by several organizations with common concerns, such as a consortium or a regulated sector, and the scenario never mentions another organization at all.

Exam tip: cloud deployment models are about who the infrastructure serves, not about which provider is named. Count the distinct infrastructures in the scenario and check whether they stay separate but connected, because two connected infrastructures is the hybrid signature.

The question hinges on when translation happens. In a compiled language the whole program is translated ahead of time: you compile each source module into an object file, then link those object files into a single executable, and only that executable runs. Nothing is translated while the program is running, which is why compiled programs start quickly and why a syntax error surfaces at build time rather than when a user finally reaches that line.

Interpreted languages invert this. The source is read and executed statement by statement at run time, so there is no separate build step producing a machine-code binary. Markup languages describe the structure and presentation of a document rather than instructions to execute, so nothing about them is compiled. Query languages express what data you want from a database, and the database engine plans and runs the query, which again is not ahead-of-time translation of a program.

Exam tip: the phrases before execution and at run time are doing all the work in this family of questions. Compiling means translate first and run later; interpreting means translate and run in the same pass.

The defining property is what the license permits, not what the software costs. Open source software ships with its source code available under a license that lets anyone read it, change it, and pass modified copies on to others. Access to the source is the precondition for the freedom to study and modify a program, which is why the license and the source always travel together.

The distractors describe other axes entirely. Proprietary software keeps the source closed and owned by the vendor, so you receive a binary and permission to run it. Freeware costs nothing but says nothing about the source code, and most freeware is closed source, which is the trap in this item because the word free is doing double duty for price and for permission. Subscription software describes how you pay, per period rather than per copy, and a subscription business model sits happily on top of open source code.

Exam tip: separate three independent questions before answering. What does it cost, how do you pay for it, and what are you allowed to do with the code? Only the third defines open source, and marketing copy deliberately blurs the first two into it.

The arithmetic is right; the units are not. Connection speeds are quoted in megabits per second, while file sizes are quoted in megabytes, and there are eight bits in one byte. So a 200 Mbps link delivers about 25 megabytes per second, and a 100 MB file needs roughly four seconds, which is exactly what the user observed. The half-second expectation came from silently treating megabits and megabytes as the same unit.

The other explanations invent a cause where the units already account for the result. Throttling would produce a rate below the advertised one, but this link is delivering its advertised rate once you convert correctly. Latency is round-trip delay measured in milliseconds; it affects how quickly a transfer starts, not a fixed multi-second tax on every download. Compression, if anything, makes a transfer finish sooner, and decompressing on a modern machine is far faster than a 200 Mbps link can feed it.

Exam tip: watch the capitalization in the unit itself. A lowercase b means bits and an uppercase one means bytes, so Mbps and MB/s differ by a factor of eight. Convert the units before reasoning about anything else.