Free 220-1102 flashcards

Which file system lets a removable drive carry files larger than 4 GB with native read/write on both Windows and macOS?

exFAT. It was designed for flash media, removes the 4 GB per-file limit that FAT32 imposes, and is natively read/write on modern Windows and macOS, so it meets all three constraints at once.

True or false: FAT32 is the safe pick for a USB drive because it is the most widely supported removable-media format.

False for large files. FAT32 is broadly compatible, but it caps individual files at 4 GB, so a 6 GB video will not fit. Use exFAT when files exceed 4 GB.

When storage media must stay functional for reuse, which sanitisation approach protects the old data?

Choose a controller-level Secure Erase rather than physical destruction or a superficial format. ATA Secure Erase resets every flash cell, including spare blocks, so the previous user's data is unrecoverable while the drive remains fully usable for reissue.

True or false: degaussing an SSD reliably erases its data because the field wipes the storage.

False. An SSD stores data in flash cells, which a magnetic field cannot erase. Degaussing only works on magnetic media; on an SSD the data survives, so use a controller Secure Erase instead.

An app force-closes at launch right after an update while every other app runs fine. What is the least-destructive first fix?

Clear only that app's cache. An update can leave incompatible cached temporary files that make it fail at launch; clearing the cache forces those files to be rebuilt while leaving accounts and saved data untouched, so it comes before clear-data or reinstall.

A banking app crashes after an update. Should you clear its storage and data first to give it a fresh start?

No. Clearing storage often fixes a corrupt-state crash, but it also wipes saved logins and in-app data, so it is not the first step when that data must be kept. Clear only the cache first, which preserves accounts and saved data.

When first logging a support ticket, which two details must always be captured?

The affected user's name and contact details plus a clear description of the reported problem. These are the core of a ticket: they let any technician triage it, contact the caller, reassign it, and track it to closure. Without them the ticket cannot be matched to the requester or reassigned.

Should the resolution steps be written into a ticket at the moment it is first logged?

No. The fix cannot be known before diagnosis, so writing resolution notes at intake records a solution that has not happened. Resolution notes matter, but they belong at closure, not at logging time.