Answer is B ( No ) Initial will perform a full sync and add the user account created but it will take time, Delta, will kick off a delta sync and bring only the last change, so it will be "immediately" and will fulfill the requirements.

Answer is A YES delta:synchronize changes since last full synchronization Start-ADSyncSyncCycle -policy initial PS C:\Users\Administrator> Start-ADSyncSyncCycle Result ------ Success https://geekdudes.wordpress.com/2018/06/05/office-365-configuring-ad-synchronization/

Final Answer : A

It could be that you have an urgent change that must be synchronized immediately, which is why you need to manually run a cycle. If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta. To initiate a full sync cycle, run Start-ADSyncSyncCycle -PolicyType Initial from a PowerShell prompt. Running a full sync cycle can be very time consuming, read the next section to read how to optimize this process. https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-feature-scheduler

The answer is B. The question said "you create a new user", it suggests that the initial sync have been done.

Yes, the solution meets the goal. The Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet is used to initiate an initial synchronization cycle for Azure AD Connect, which is the successor to DirSync. This command triggers the synchronization process and replicates changes from the on-premises Active Directory to Azure AD immediately.

I have attended the Sample test from Microsoft portal, They have mentioned option A as answer

Yes is right

Answer is: B - No. I'll explain: Please please read the reference URL posted in the solution for the question. That link TELLS YOU "This is where a nice streamlined single powershell cmdlet comes into play. Gone is the old Start-OnlineCoexistenceSync and in comes the nice new cmdlet: Start-ADSyncSyncCycle -PolicyType Delta. If we go back to my extreme example of a multi-forest AADConnect deployment there could be a VERY LONG WAIT TIME to have all objects run through a full sync because you forgot to specify policy type (DELTA)

I think people are reading too far into this question. They are asking IF THE SOLUTION WILL WORK. YES. YES IT WORKS. Is it the fastest? NOPE. Delta sync is the fastest by large. Initial takes forever and syncs the entire directory. Obviously we don't want that as engineers, but the solution for using initial sync DOES work.

"Start-ADSyncSyncCycle -policy initial" will work, even though it may not be the best solution to accomplish the task. That is all the question is asking.

A is correct, Delta will work as it's just a single user.

No Start-ADSyncSyncCycle -PolicyType Initial cmdlet: This PowerShell command is specifically designed to trigger an immediate synchronization of all objects (including users) from your on-premises Active Directory to Azure AD. Hybrid coexistence: Since your environment is configured for hybrid coexistence with DirSync, any changes made in on-premises AD are automatically detected and queued for synchronization with Azure AD. Immediate replication: The -PolicyType Initial flag ensures a complete synchronization, including newly created objects, unlike the default Delta sync which only synchronizes changes since the last run. Therefore, running the Start-ADSyncSyncCycle -PolicyType Initial cmdlet will immediately replicate the newly created user account from your on-premises Active Directory to Azure AD.

this question is reffering to single account user then until Start-ADsyncsynccycle -policy this command is correct when use the initial word then it is not correct so the answer is B

No is the clear choice Touch me at [email protected] for full set

A Start-ADsyncsynccycle -policy

So which is the answer on the test? The one they give or the one you guys vote for and provide explanations as to why it's wrong ?