312-50V13 Question #544: Real Exam Question with Answer & Explanation

Question

A certified ethical hacker is conducting a Whois footprinting activity on a specific domain. The individual is leveraging various tools such as Batch IP Converter and Whols Analyzer Pro to retrieve vital details but is unable to gather complete Whois information from the registrar for a particular set of data. As the hacker, what might be the probable data model being utilized by the domain's registrar for storing and looking up Who is information?

Options

• AThick Whois model with a malfunctioning server
• BThick Whois model working correctly
• CThin Whois model with a malfunctioning server
• DThin Whois model working correctly

Explanation

Explanation

Option D is correct because the Thin Whois model stores only basic registration data (such as the registrar name and nameservers) at the central registry, requiring users to query the specific registrar's database for complete information - meaning incomplete results are a normal, expected behavior of a properly functioning Thin Whois system, not a sign of failure.

Why the distractors are wrong:

• Option A & B (Thick Whois): The Thick Whois model stores all registrant data (contacts, addresses, technical details) in a single centralized database, so a working Thick Whois server would return complete information - making incomplete results inconsistent with this model.
• Option C (Thin Whois malfunctioning): While a malfunctioning Thin Whois server could also return incomplete data, the scenario describes a consistent, expected limitation rather than an error or outage - eliminating the "malfunctioning" explanation.

Memory Tip: Think of it this way - "Thin = Thin on details". A Thin Whois model gives you thin (minimal) information from the central registry and sends you elsewhere for the full picture, while "Thick = Thick with data" means everything is stored in one place. If your results are incomplete but tools are working, you're dealing with a Thin model doing its job correctly.

No community discussion yet for this question.