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

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.

according to https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-feature-scheduler "Running a full sync cycle can be very time consuming" you need to use delta instead of initial

Answer should be A here. Initial initiates a full sync cycle while Delta sync's the changes made since the last sync

Running the PowerShell cmdlet Start-ADSyncSyncCycle -PolicyType Initial will trigger a full synchronization cycle between your on-premises Active Directory and Azure Active Directory. This ensures that any new user accounts or changes made on-premises, like the one you created, are replicated to Azure AD immediately. The "Initial" policy type triggers a full sync, which is appropriate in this case to ensure that the newly created user account is synchronized. The correct answer is: A. Yes

The cmdlet would sync it

Segundo o Copilot: A. Sim. Executar o cmdlet Start-ADSyncSyncCycle -PolicyType Initial no PowerShell iniciará uma sincronização imediata entre o Active Directory local e o Azure AD, replicando as informações do usuário.

Running the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet initiates a full synchronization cycle, replicating the new user information from the on-premises Active Directory to Azure AD immediately.

The Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet forces an initial synchronization between the on-premises Active Directory and Azure Active Directory (Azure AD). This includes all objects, such as users, groups, and contacts. An Initial Sync is a full synchronization cycle, which pulls all changes from the on-premises Active Directory to Azure AD. Since your goal is to replicate the new user information to Azure AD immediately, running this cmdlet achieves that by initiating a sync.

it´s B Keyword is IMMEDIATELY. So we muat use: Start-ADSyncSyncCycle -PolicyType Delta cmdlet. The Delta policy is much FASTER and intended for syncing recent changes, such as a newly created USER ACCOUNT.