A customer wants to create a mobile app that requires users to log in or...

Because newly registered users have no pre-existing Salesforce Contact record and their device is explicitly stated to remain unassociated with a proper ContactKey for up to 24 hours after registration, MobilePush will, during that unassociated window, necessarily create a new, temporary contact record in Marketing Cloud to track that device ' s push registration and interactions — since the platform requires some contact-level record to associate a registered device with, even before the eventual Salesforce ContactKey linkage completes. This means the consultant must flag that newly registered users will generate additional (initially unmatched) Contact records in Marketing Cloud during that gap period, a consideration with implications for contact-count licensing, deduplication planning, and eventual merge/reconciliation logic once the 24-hour Salesforce association process completes. Existing users who log in with credentials already tied to a Salesforce record (option D) are immediately and correctly matched to their existing ContactKey upon login, so they do not generate additional contacts. Option B ' s ' 48 hours ' figure does not match the 24-hour window explicitly stated in the scenario. Option C incorrectly generalizes the issue to all mobile app users, when it specifically and only affects newly registered users during the unassociated window, not those logging in with pre-existing credentials. Reference: MobilePush ContactKey Association, Mobile App Registration Flows.