# Microsoft Leap: eligibility, applications and the 16-week commitment

## Importing twice should not silently create duplicates

Original fictional software exercise. Your store already has appointments A and B. Under this specification, unchanged records are skipped, new IDs are added, and conflicting updates require approval.

### A second batch of three records

| ID | Stored value | Incoming value | Expected result |
| --- | --- | --- | --- |
| A | Jan 5, 10:00 UTC | Jan 5, 10:00 UTC | Unchanged; do not create another A |
| B | Jan 6, 10:00 UTC | Jan 7, 10:00 UTC | Conflict; preserve B until approved |
| C | Not present | Jan 8, 10:00 UTC | Create C |

## Your turn

How many stored appointments remain after the batch, and what should a repeat of that same batch do?

## Your answer

[Write your approach here.]

## For your own application

Demonstrate the repeat test in your own project. Explain what counts as the same record and when an update is permitted.

Return to the guide for the worked answer and source notes:
https://internshipdeadlines.com/guides/microsoft-leap-application-guide