Exam AZ-104 topic 1 question 9 discussion

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.

https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler In this article. It says word for word, "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." Keywords in this learn.microsoft article are immediately and manually.... If you want it to synchronize immediately, then you'll want to manually run a cycle.... To run a cycle manually, run the -delta command. Immediate = Manual. Manual = Delta. Therefor Immediate = Delta Full sync = Time Consuming. Time Consuming = Initial

Below are the possible options for this scenario. Consolidating here for easy read of subscribers. Solution: You run the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet. - No Solution: You use Active Directory Sites and Services to force replication of the Global Catalog on a domain controller. - No Solution: You restart the NetLogon service on a domain controller. - No Solution: You run the Start-ADSyncSyncCycle -PolicyType Delta PowerShell cmdlet. - No

Yes, running this command will force Azure AD Connect to sync all objects, including the new user, immediately to Azure AD. - Although a delta sync (`-PolicyType Delta`) is usually enough and faster for syncing new users, a full sync (`-PolicyType Initial`) will also replicate the user information immediately. - So, the solution does meet the goal of replicating the user to Azure AD immediately. Since the question uses the full sync command (`-PolicyType Initial`), it does meet the goal of immediate replication. Answer: A. Yes

The cmdlet Start-ADSyncSyncCycle -PolicyType Initial is used to manually trigger a full synchronization between the on-premises Active Directory and Azure Active Directory (Azure AD). -PolicyType Initial performs a full sync, including both delta and initial sync processes. This is typically used when there have been changes in configuration or schema that require a complete sync. Since the goal is to replicate the new user account information to Azure AD immediately, this command does meet the goal.

B is the Answer Start-ADSyncCycle -PolicyType Delta

b is good answer

La commande Start-ADSyncSyncCycle -PolicyType Initial est spécifique à Azure AD Connect, et non à DirSync.

Is no because the command is for Azure ad connect not for the obsolete service servsync

To initiate an immediate sync between the on-premises AD and Azure Active Directory, the policy type needs to be changed from 'Initial' to 'Delta'.

A is correct, as it meets the solution. It doesn't ask the faster solution, just if its meet or not, so it meet.

l cmdlet Start-ADSyncSyncCycle -PolicyType Initial se usa en entornos con Azure AD Connect (anteriormente DirSync) para iniciar manualmente una sincronización completa de directorios. Dado que el entorno descrito utiliza Azure AD en modo híbrido con un servidor DirSync (DirSync1), la creación de una nueva cuenta de usuario en Active Directory local no se replicará inmediatamente en Azure AD a menos que se inicie manualmente la sincronización o se espere la sincronización programada (que ocurre cada 30 minutos, por defecto). Diferencia entre tipos de sincronización en Azure AD Connect: Delta: Solo sincroniza los cambios recientes. Se ejecuta automáticamente cada 30 minutos. Initial: Realiza una sincronización completa, útil para nuevos usuarios, cambios de esquema o cuando se configuran nuevas reglas de sincronización.

Answer A is correct. The question is "Does the solution meet the goal?" it is not the best solution, however it meet the goal.

To run Delta cmd, data needs to be synced already. Anyway Initial cmd will not impact immediately however for new sync below cmd is req Start-ADSyncSyncCycle -PolicyType Initial

immediately key word changes the answer to NO so the corret answer in this question in B

it will take time but the solution is met

The Start-ADSyncSyncCycle PowerShell cmdlet is used to trigger a synchronization cycle between the on-premises Active Directory and Azure Active Directory. -PolicyType Initial: This parameter forces a full synchronization of all objects from the on-premises Active Directory to Azure AD. It includes all changes and ensures that the newly created user is replicated to Azure AD. Since the goal is to replicate the new user information to Azure AD immediately, running this cmdlet with the -PolicyType Initial parameter meets the requirement. We can use Start-ADSyncSyncCycle: -PolicyType Delta: Use this for incremental syncs, which only synchronize the changes since the last sync. It is faster and sufficient in most cases. -PolicyType Initial: Use this for a full sync. It processes all objects and is typically used when there are significant changes, such as schema updates or large-scale object additions.