Likely C is the way to go. Disconnecting the hypervisor cuts off attacker access right away, which matches IR best practices for containment. D trips some folks up since patching is important, but it doesn't stop what's already happening. Open to corrections if I missed something.
Smartcards are all about securely storing private keys in PKI, so D.
Official guide and those end-of-chapter practice exams both call out that DSS doesn’t provide encryption, only signature, integrity, and authentication. If you’re reviewing, focus on which NIST/FIPS standards pair which features with each crypto tool. Pretty sure A is what they want here but chime in if you've seen different in the official book.
I don't think it's D. A is correct here. DSS doesn't actually do encryption, just handles signatures for integrity and authentication. I remember a similar question came up in my practice set. Let me know if anyone picked something else, but pretty sure it's A.
I was thinking B here, since async TDM does adjust time slots based on traffic, so it feels like bandwidth could be dynamically assigned. Saw similar phrasing on a practice test. Might be mixing up statistical and async TDM though! If anyone's got the official guide handy, let me know if I'm off.
It's gotta be C for this one. Statistical multiplexing is the approach that handles variable bit-rate and allocates bandwidth only to channels with data to send. Saw similar wording pop up on practice exams lately. Pretty sure that's what they're asking for, but open to pushback if anyone thinks otherwise.
RARP is the one that actually maps MAC to IP directly, so A fits best for this legacy scenario. I remember a similar question on an older exam. Pretty sure that's what ISC2 wants here. Anyone disagree?
I was leaning toward D, partial mesh, since it also has some redundancy and seems more scalable than a full mesh. But maybe I’m missing something about the "highest" part. Wouldn’t full mesh be overkill except in tiny setups?
Wouldn't tree topology (B) actually create several single points of failure at the higher nodes? I get why someone might pick D for scalability, but the question's all about availability, not cost. Full mesh (C) has no single points, so that's why it's usually picked for these types of questions.
C for sure. Full mesh means every device is connected to every other, so if something fails there are still tons of paths available. Partial mesh adds some redundancy but not to the same level. Pretty confident on this unless I'm misreading what they want by "highest." Agree?