This chapter covers mobile device synchronization methods, a key topic in the CompTIA A+ 220-1101 exam (Domain 1.0: Mobile Devices, Objective 1.2). You will learn the protocols, configuration steps, and troubleshooting techniques for syncing email, contacts, calendars, and files across devices and cloud services. Approximately 5–10% of exam questions touch on mobile device connectivity and synchronization, making this a high-yield area. Mastery of sync methods is essential for supporting modern mobile workforces and passing the exam.
Jump to a section
Imagine a corporate mailroom that must keep identical records at two branch offices. Each office has its own mail clerk. When a package arrives at Office A, the clerk logs it and sends a carbon copy of the log entry to Office B. Office B's clerk updates their log. If Office B's clerk is away, Office A's clerk leaves a note on the desk. Later, Office B's clerk processes the note and updates the log. This is like push synchronization—changes are actively sent. Now consider a different system: each clerk periodically checks the other's log for new entries and copies them over. This is pull synchronization. For two-way sync, both clerks send and receive updates, but they must agree on a common format (like a specific logbook layout) and handle conflicts—if both clerks receive a package for the same recipient, they must decide which entry is newer or ask a supervisor. This mirrors how mobile devices sync contacts, calendars, and files: they use protocols like Exchange ActiveSync (push), IMAP (pull), or CalDAV/CardDAV (two-way) and must resolve conflicts using timestamps or user rules.
What Are Mobile Device Sync Methods?
Mobile device synchronization (sync) refers to the process of ensuring that data—such as emails, contacts, calendars, notes, and files—remains consistent across multiple devices and cloud services. For the 220-1101 exam, you must understand the primary sync methods: Exchange ActiveSync (EAS), IMAP, POP3, CalDAV, CardDAV, and cloud-based sync (e.g., iCloud, Google Sync). The exam also covers manual sync via USB and wireless sync (Wi-Fi Sync).
Exchange ActiveSync (EAS)
EAS is a Microsoft protocol that provides push synchronization of email, contacts, calendars, and tasks between an Exchange server and mobile devices. It uses HTTPS (port 443) and XML-based commands. Key features: - Push technology: The server notifies the device immediately when new data arrives, rather than the device polling. - Direct Push: The device sends a long-lived HTTPS request (ping) to the server; the server responds only when there is new data or a timeout (default 30 minutes). - Conflict resolution: Based on last modification time; the change with the later timestamp wins. - Security: Supports SSL/TLS encryption, device wipe, and password policies.
Configuration on an iOS device: Settings > Mail > Accounts > Add Account > Microsoft Exchange. Enter email, server (e.g., outlook.office365.com), domain (optional), username, and password. The device automatically discovers settings via Autodiscover (uses DNS SRV record _autodiscover._tcp).
IMAP (Internet Message Access Protocol)
IMAP4 (RFC 3501) is a protocol for retrieving email from a server while leaving messages on the server. It syncs folder structure and message states (read, unread, flagged). Default port: 143 (unencrypted) or 993 (IMAPS with SSL/TLS). IMAP is ideal for multi-device access because changes on one device are reflected on others.
How it works: 1. Client connects to server and authenticates (LOGIN command). 2. Client selects a mailbox (SELECT INBOX). 3. Client fetches message headers or full messages (FETCH command). 4. Client can mark messages as read, delete, or move to other folders. 5. Client disconnects or issues LOGOUT.
IMAP does not natively sync contacts or calendars; it is email-only. For contacts/calendar sync, CalDAV and CardDAV are used.
POP3 (Post Office Protocol version 3)
POP3 (RFC 1939) downloads email from server to a single device and typically deletes the server copy. Default port: 110 (unencrypted) or 995 (POP3S). POP3 is not a sync method—it is a download-and-delete protocol. It does not sync across devices. The exam tests that POP3 is inappropriate for multi-device sync.
CalDAV and CardDAV
CalDAV (RFC 4791) and CardDAV (RFC 6352) are protocols for syncing calendar and contact data, respectively, using WebDAV. They allow two-way sync with a server (e.g., iCloud, Google Calendar). - CalDAV: Uses iCalendar format (RFC 5545). Syncs events, tasks, and alarms. - CardDAV: Uses vCard format (RFC 6350). Syncs contacts with fields like name, phone, email, address.
Both use HTTP/HTTPS and support conflict resolution via ETags (entity tags) and modification timestamps.
Cloud Sync (iCloud, Google, OneDrive)
Cloud sync uses proprietary protocols (often based on CalDAV/CardDAV/IMAP) to keep data consistent across devices and the cloud. For example: - iCloud: Uses Apple's push sync for contacts, calendars, and iCloud Drive. Settings are managed under Settings > [Your Name] > iCloud. - Google Sync: Uses Google's implementation of Exchange ActiveSync (for Gmail, Google Calendar, Contacts) or IMAP/CardDAV/CalDAV. - OneDrive: Uses Microsoft's sync engine (Files On-Demand) to sync files to Windows, macOS, iOS, and Android.
Wireless Sync vs. Wired Sync
Wireless Sync: Uses Wi-Fi or cellular data. Common examples: iCloud backup over Wi-Fi, Google Photos auto-upload, and Exchange push email. Wireless sync is convenient but uses data and battery.
Wired Sync: Uses USB cable to connect device to a computer. Examples: iTunes sync for iOS devices (music, photos, backups), Android File Transfer. Wired sync is faster and more secure but requires physical connection.
Synchronization Methods: Push vs. Pull vs. Two-Way
Push: Server sends updates to device immediately. Used by EAS, iCloud push. Low latency, high battery usage.
Pull: Device periodically requests updates from server. Used by IMAP (polling), POP3. Configurable interval (e.g., every 15 minutes). Higher latency, lower battery usage.
Two-Way Sync: Both device and server can initiate updates. Used by CalDAV/CardDAV, EAS. Requires conflict resolution.
Conflict Resolution Strategies
Last writer wins: The most recent modification timestamp determines the final state. Common in EAS and CalDAV.
Manual resolution: User is prompted to choose which version to keep. Used in some file sync services (e.g., Dropbox).
Merge: Attempt to combine changes (e.g., in calendar events, merge attendees). Rarely used in mobile sync.
Troubleshooting Sync Issues
Common problems and solutions: - Authentication failures: Verify username/password, check if account is locked or requires app-specific password. - Server connectivity: Ensure device has internet access, check firewall rules (port 443 for EAS, 993 for IMAPS, 995 for POP3S). - SSL certificate errors: If using a self-signed certificate, the device may reject the connection. Install the certificate or use a trusted CA. - Conflicts: If two devices edit the same contact simultaneously, the last sync wins. Educate users to avoid concurrent edits. - Data not appearing: Check sync settings (e.g., toggle Mail, Contacts, Calendars on/off). Force a sync by restarting the device or toggling Airplane Mode.
Exam-Tested Commands and Settings
On Android:
Settings > Accounts > [Account type] > Sync settings.
Use adb shell to force sync: adb shell am broadcast -a android.intent.action.SYNC.
On iOS:
Settings > [Your Name] > iCloud > Manage Storage.
Settings > Mail > Accounts > Fetch New Data > Push (or Fetch).
On Windows:
Settings > Accounts > Email & app accounts.
Control Panel > Mail (Microsoft Outlook) > Data Files.
Interaction with MDM (Mobile Device Management)
MDM solutions (e.g., Microsoft Intune, Jamf) can enforce sync policies: require encryption, disable iCloud backup, enforce passcode, and remotely wipe devices. The exam may test that MDM can configure EAS profiles on iOS/Android.
Configure Exchange ActiveSync on iOS
1. Open Settings > Mail > Accounts > Add Account > Microsoft Exchange. 2. Enter email address and description. 3. Tap Next; the device attempts Autodiscover to find server settings. If Autodiscover fails, enter server (e.g., outlook.office365.com), domain (optional), username, and password. 4. Choose what to sync: Mail, Contacts, Calendars, Reminders, Notes. 5. Tap Save. The device will begin syncing. Observe that the Mail app shows new emails immediately (push). If push fails, check that the server supports EAS and that port 443 is open.
Set up IMAP email on Android
1. Open Settings > Accounts > Add account > Email (or use Gmail app > Menu > Settings > Add account > Other). 2. Enter email address and password. 3. Select IMAP as account type. 4. Enter incoming server settings: server (e.g., imap.example.com), port 993 (IMAPS), security type SSL/TLS. 5. Enter outgoing server (SMTP) settings: server (e.g., smtp.example.com), port 465 (SMTPS) or 587 (STARTTLS). 6. Configure sync frequency (e.g., every 15 minutes). 7. Name the account and tap Next. The device will download email headers and sync folder list. Note that new emails may take up to 15 minutes to appear (pull).
Sync contacts via CardDAV
1. On iOS: Settings > Mail > Accounts > Add Account > Other > Add CardDAV Account. Enter server (e.g., google.com), username (full email), password, and description. Tap Next. The device will sync contacts. 2. On Android: Settings > Accounts > Add account > Personal (IMAP) or use a third-party app like DAVx5. Enter CardDAV URL (e.g., https://contacts.google.com/carddav), username, password. Sync interval can be set. CardDAV uses vCard format; each contact is a separate resource. Changes are tracked via ETags. If sync fails, verify the server URL and credentials.
Perform wired sync via USB
1. Connect device to computer using USB cable. 2. On iOS with iTunes (Windows) or Finder (macOS Catalina+): Select device, choose what to sync (music, photos, backups). Click Apply. 3. On Android: Enable USB debugging (Developer options) or use File Transfer mode (MTP). Transfer files manually. For contacts/calendar, use a third-party tool like Google Takeout or vendor software. Wired sync is faster and does not consume cellular data. Troubleshoot by checking cable, driver installation, and device lock screen (must be unlocked).
Troubleshoot sync conflicts
1. Identify the conflict: two devices edited the same contact/calendar event simultaneously. 2. Check the 'last modified' timestamps on the server (if accessible). 3. The sync protocol (e.g., EAS) will keep the version with the later timestamp. 4. If the wrong version is kept, manually restore from a backup or re-enter data. 5. To prevent future conflicts, educate users to sync before editing and avoid concurrent edits. In enterprise environments, use MDM policies to enforce sync intervals and conflict resolution rules.
In a mid-sized enterprise with 500 employees using iOS and Android devices, the IT department deploys Microsoft Exchange Online (Office 365) for email, calendar, and contacts. They configure Exchange ActiveSync (EAS) profiles via Microsoft Intune (MDM). The problem: employees frequently complain that emails appear on their desktop Outlook but not on their mobile devices. The solution: ensure that the EAS policy allows push sync and that the device is not in power-saving mode which disables background data. The IT team also configures Autodiscover to use DNS SRV records to simplify setup. Performance consideration: each device maintains a persistent HTTPS connection to the server; with 500 devices, the server must handle 500 concurrent connections. If the server is overloaded, push latency increases. Misconfiguration: if the EAS policy sets a sync interval to 'manual', users must manually refresh their inbox, leading to missed emails.
Another scenario: a small business uses Google Workspace. Employees sync contacts via CardDAV and calendar via CalDAV. The problem: a user edits a contact on their phone, but the change does not appear on their laptop. The cause: the laptop's sync interval is set to 'every 30 minutes' while the phone syncs immediately. The solution: adjust the laptop sync interval to 'every 5 minutes' or use the Google Calendar sync app for Outlook. Common scale issue: with many contacts, the initial sync can be slow; CardDAV uses ETags to only sync changed contacts after the first full sync.
A third scenario: a user syncs their iPhone with iTunes via USB to transfer photos and backups. The problem: the sync fails with error '0xE8000065'. The cause: the device is locked or the USB cable is faulty. The solution: unlock the device, try a different cable, or restart both computer and iPhone. For backups, ensure sufficient storage on the computer. Wired sync is still used in environments with strict security policies that prohibit wireless data transmission.
The CompTIA A+ 220-1101 exam tests Objective 1.2: 'Given a scenario, install and configure mobile devices.' This includes configuring email and corporate accounts, and synchronizing data. Key points:
Know the protocols: EAS (push, port 443), IMAP (port 143/993, pull), POP3 (port 110/995, download-only), CalDAV (port 80/443), CardDAV (port 80/443).
Understand push vs. pull: Push (EAS) uses server-initiated updates; pull (IMAP) uses client polling. The exam may ask: 'Which protocol provides real-time email delivery?' Answer: Exchange ActiveSync (push).
Common wrong answers:
- Choosing POP3 for multi-device access: POP3 downloads and deletes from server, so it is not suitable. Candidates pick POP3 because it is familiar. - Thinking IMAP uses push: IMAP is pull; the client must poll. Candidates confuse IMAP idle extension (which is push-like but not true push) with EAS. - Assuming CalDAV syncs email: CalDAV is for calendars only; CardDAV for contacts; IMAP for email. 4. Specific numbers: Default IMAP port (143), IMAPS (993), POP3 (110), POP3S (995), SMTP (25, 465, 587), EAS (443). Sync intervals: often 15, 30, 60 minutes for IMAP; push is immediate. 5. Edge cases:
- If a device is offline, push notifications are queued; when the device reconnects, it receives a 'ping' from the server. - Autodiscover failure: the device may prompt for manual server settings. The exam may test that Autodiscover uses DNS SRV record _autodiscover._tcp. - SSL certificate errors: the device will reject the connection if the certificate is untrusted. The solution is to install the certificate or use a public CA. 6. Eliminate wrong answers: If the question mentions 'synchronizing contacts across multiple devices', eliminate POP3 and IMAP (email only). If the question mentions 'real-time', eliminate IMAP and POP3 (pull). If the question mentions 'Microsoft Exchange', think EAS.
Exchange ActiveSync (EAS) uses push synchronization over HTTPS (port 443) and syncs email, contacts, calendars, tasks, and notes.
IMAP is a pull protocol for email only, using ports 143 (plain) or 993 (SSL). It syncs folder structure and message states.
POP3 downloads email to one device and typically deletes from server; not suitable for multi-device sync.
CalDAV syncs calendar data (iCalendar format); CardDAV syncs contacts (vCard format). Both use HTTP/HTTPS.
Wireless sync uses Wi-Fi/cellular; wired sync uses USB and is faster and more secure.
Conflict resolution in EAS uses last-writer-wins based on modification timestamp.
Autodiscover uses DNS SRV record _autodiscover._tcp to find Exchange server settings automatically.
MDM solutions can enforce sync policies, including encryption, passcode, and remote wipe.
These come up on the exam all the time. Here's how to tell them apart.
Exchange ActiveSync (EAS)
Push technology: server sends updates immediately.
Syncs email, contacts, calendars, tasks, and notes.
Uses HTTPS (port 443); encrypted by default.
Supports remote wipe and device security policies.
Requires Exchange server or compatible service (e.g., Office 365).
IMAP
Pull technology: client polls server at intervals.
Email only; no native contacts or calendar sync.
Uses port 143 (unencrypted) or 993 (SSL).
No remote wipe capability (unless combined with MDM).
Works with any IMAP-compatible email server (e.g., Gmail, Yahoo).
Mistake
IMAP pushes emails to the device instantly.
Correct
IMAP is a pull protocol; the client must periodically poll the server for new messages. The IMAP IDLE extension allows the server to notify the client of new messages, but this is not true push and is not as efficient as EAS. The exam tests that EAS is push; IMAP is pull.
Mistake
POP3 can sync email across multiple devices.
Correct
POP3 downloads messages to one device and typically deletes them from the server. This prevents other devices from accessing the same emails. For multi-device sync, IMAP or EAS is required.
Mistake
CalDAV is used for syncing email.
Correct
CalDAV is specifically for calendar data (iCalendar format). CardDAV is for contacts (vCard). Email sync uses IMAP, POP3, or EAS.
Mistake
Wired sync is slower than wireless sync.
Correct
Wired sync (USB) is generally faster than wireless sync (Wi-Fi or cellular) because USB 3.0 can transfer at 5 Gbps, while Wi-Fi 5 (802.11ac) maxes at about 1.3 Gbps. Wired sync is also more reliable and secure.
Mistake
Exchange ActiveSync only works with Microsoft Exchange Server.
Correct
EAS is licensed by many third-party providers, including Google (for Gmail/Google Calendar/Contacts) and Apple (for iCloud). The protocol is used by many email services that support EAS.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
Push synchronization means the server sends updates to the device immediately when changes occur, without the device requesting them. Exchange ActiveSync uses push. Pull synchronization means the device periodically asks the server for new data. IMAP uses pull. Push provides real-time updates but uses more battery; pull has delay but conserves battery. The exam tests that EAS is push and IMAP is pull.
Use CardDAV for contacts. It is a standard protocol that syncs vCard data over HTTP/HTTPS. Alternatively, Exchange ActiveSync can sync contacts if you have an Exchange account. IMAP and POP3 do not sync contacts. The exam may ask: 'A user wants to sync contacts between their iPhone and Android tablet. Which protocol should be configured?' Answer: CardDAV (or Exchange ActiveSync if using a compatible service).
Go to Settings > Mail > Accounts > Add Account > Microsoft Exchange. Enter your email address and description. The device will attempt Autodiscover. If it fails, enter server (e.g., outlook.office365.com), domain (optional), username, and password. Choose what to sync (Mail, Contacts, Calendars, Reminders, Notes) and tap Save. The device will begin push syncing. If push does not work, check that the server supports EAS and that port 443 is open.
The default sync interval varies by email client. In the Gmail app, you can set it to 'Auto' (which uses push if available) or a specific interval like 15 minutes, 30 minutes, or 1 hour. In the default Android Email app, the default is often 'Push' (if the server supports IMAP IDLE) or every 15 minutes. The exam does not test exact defaults but expects you to know that IMAP is pull and intervals are configurable.
The device still has the old password. Go to Settings > Mail > Accounts, tap the account, then tap Account again (or Password) and enter the new password. If the problem persists, delete the account and re-add it. Also check that the server is reachable and that the account is not locked. The exam may test that authentication failures are a common cause of sync issues.
No, POP3 is designed to download emails to one device and then delete them from the server. If you use POP3 on your phone, the emails will be removed from the server, so your laptop will not see them. For multi-device access, use IMAP or Exchange ActiveSync. The exam will test that POP3 is not suitable for multiple devices.
Autodiscover is a service that automatically configures Exchange client settings (server address, SSL requirements, etc.) by using the user's email address. It uses a DNS SRV record (_autodiscover._tcp) or an HTTP redirect. If Autodiscover fails, the user must manually enter server settings. The exam may ask about Autodiscover as a feature that simplifies EAS setup.
You've just covered Mobile Device Sync Methods — now see how well it sticks with free 220-1101 practice questions. Full explanations included, no account needed.
Done with this chapter?