Force Immediate Azure AD Connect Sync of New User

Manage Microsoft Entra users and groups
Answer Correct answer: B — Start-ADSyncSyncCycle -PolicyType Initial runs a full sync cycle; use -PolicyType Delta to replicate the new on-premises user to Azure AD immediately.

Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if the solution satisfies the requirements. Your company has an Azure Active Directory (Azure AD) tenant named weyland.com that is configured for hybrid coexistence with the on-premises Active Directory domain. You have a server named DirSync1 that is configured as a DirSync server. You create a new user account in the on-premise Active Directory. You now need to replicate the user information to Azure AD immediately. Solution: You run the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet. Does the solution meet the goal?

  1. Yes
  2. No Correct Answer

Community Insight

The test measures whether you know that -PolicyType Initial launches a full import/full sync/export cycle across all connectors, so it cannot satisfy an 'immediately' requirement where -PolicyType Delta is the documented urgent-change switch.

This AZ-104 scenario asks whether running Start-ADSyncSyncCycle -PolicyType Initial will immediately replicate a newly created on-premises Active Directory user to the weyland.com Azure AD tenant. The page establishes that the answer is No, because only -PolicyType Delta delivers the urgent, targeted sync cycle the requirement calls for.

Choosing A (Yes), because an Initial cycle would eventually create the user in Azure AD; learners overlook that a full sync cycle is lengthy and that Microsoft prescribes -PolicyType Delta for urgent manual synchronization.

Community Discussion (232 comments)

Srikantha 👍 1 Selected: A
According to the official Microsoft documentation for Microsoft Entra Connect Sync (formerly Azure AD Connect), running the command: PowerShell Start-ADSyncSyncCycle -PolicyType Initial explicitly initiates a full synchronization cycle. While a delta synchronization (-PolicyType Delta) is typically used for routine changes like adding a single user, running an initial (full) sync cycle processes all objects and attributes, which successfully replicates the newly created user account to Microsoft Entra ID (Azure AD). Therefore, the solution meets the goal (A. Yes).
Auniii 👍 2 Selected: A
A new user is picked up by a Delta synchronization. An Initial synchronization also synchronizes the new user because it performs a full synchronization. So the solution works.
chest_jd 👍 2 Selected: A
The solution SOLVES the issue. It is not efficient but it works.
Chris2pher 👍 2
no. the question says, immediate. The command will take some times and not immediate: Start-ADSyncSyncCycle -PolicyType Initial
Gramgm 👍 1 Selected: B
The cmdlet Start-ADSyncSyncCycle -PolicyType Initial is specific to Azure AD Connect. Your environment uses DirSync (you stated DirSync1 as a DirSync server). DirSync does not support this cmdlet. If the environment were using Azure AD Connect (not DirSync), you could use: Start-ADSyncSyncCycle -PolicyType Delta (usually enough for new users), Or -PolicyType Initial for a full import/sync cycle (takes longer).
cafenipon 👍 2 Selected: B
Must be from PowerShell and run Start-ADSyncSyncCycle -PolicyType Delta
CloudEnabler 👍 1 Selected: A
Copilot answer: A. Yes Running the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet on your DirSync (Azure AD Connect) server does meet the goal. This command immediately triggers a full synchronization cycle, which will replicate the newly created on-premises Active Directory user to Azure AD right away. Summary: Start-ADSyncSyncCycle -PolicyType Initial = Full sync (including all objects and attributes) This is the correct way to force an immediate sync after creating a new user.
RushaShah 👍 1 Selected: B
Answer: B. No What the Solution Does Start-ADSyncSyncCycle -PolicyType Initial runs a full (initial) synchronization. A full sync reprocesses all objects and takes much longer than a delta sync. It will eventually replicate the new user, but it is not immediate, it’s heavier and slower than what the requirement calls for. The proper/fastest command would be: That replicates only new/changed objects → much faster and effectively immediate.
Sahar_A 👍 1 Selected: B
No need for a full sync, just sync the recent changes using delta instead of Initial
ahmadniknam 👍 2 Selected: B
I considered "DirSync1" to be just the server name. However, the question clearly states that the server is configured as a DirSync server, which implies that it's running the legacy DirSync tool — not Azure AD Connect. Since the Start-ADSyncSyncCycle cmdlet is only available in Azure AD Connect, this solution would not apply here. So you're absolutely right — the correct answer should be No in this case. Thanks for pointing it out!
ahmadniknam 👍 1 Selected: A
In differentiating between Azure AD Connect and DirSync. But in the context of this inquiry, "DirSync1" is probably just the name of the server, and Azure AD Connect—which is frequently used in real-world setups following upgrades—is the synchronization tool in use. We can presume that the question is about the Start-ADSyncSyncCycle -PolicyType Initial cmdlet, which is only accessible with Azure AD Connect. Thus, in a technical sense, the solution does achieve the objective. I appreciate you bringing up a valid point.
SherryJamkam 👍 1 Selected: A
The solution correctly forces an immediate sync of the new user to Azure AD, meeting the requirement.
Kabilanis 👍 2 Selected: B
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
shankey05 👍 1 Selected: A
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
ZUMY 👍 2 Selected: B
B is the Answer Start-ADSyncCycle -PolicyType Delta
NicoVick 👍 1 Selected: B
b is good answer
Rab4622 👍 1 Selected: B
La commande Start-ADSyncSyncCycle -PolicyType Initial est spécifique à Azure AD Connect, et non à DirSync.
Rab4622 👍 1 Selected: B
Is no because the command is for Azure ad connect not for the obsolete service servsync
andted98 👍 1 Selected: B
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'.
jharishi 👍 1 Selected: A
A is correct, as it meets the solution. It doesn't ask the faster solution, just if its meet or not, so it meet.
victorio_27 👍 1 Selected: A
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.
willie439 👍 1 Selected: A
Answer A is correct. The question is "Does the solution meet the goal?" it is not the best solution, however it meet the goal.
Nathan12345 👍 1 Selected: A
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
guha_saheb 👍 1 Selected: B
immediately key word changes the answer to NO so the corret answer in this question in B
guha_saheb 👍 1 Selected: A
it will take time but the solution is met
SolimanAlali 👍 1 Selected: A
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.
mm102938 👍 1
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
Capzn 👍 1
Answer should be A here. Initial initiates a full sync cycle while Delta sync's the changes made since the last sync
Ariel235788 👍 2
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
0378d43 👍 1 Selected: A
The cmdlet would sync it
LaReis 👍 2
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.
asuarez 👍 1 Selected: A
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.
Pcservices 👍 1 Selected: A
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.
👍 2 Selected: B
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.
Nathan12345 👍 1
for this , pre-requisite is initial sync, which is required to run delta cmd
Devs84 👍 2 Selected: B
Only need to do a Delta sync
vrm1358 👍 2 Selected: B
B is correct. initial can sync last config and is rapid
Garthage 👍 2
'Immediately' in this context just means you want to kick off the sync manually right that moment, rather than wait for the next automated scheduled sync. Therefore -initial or -delta are both correct but as the questions asks specifically about -initial, then the answer is A. Yes
vrm1358 👍 2
This cmdlet can be run with two different options for the -PolicyType parameter: 1- -PolicyType Delta: This triggers a delta synchronization. A delta sync processes only the changes (additions, deletions, and updates) that have occurred since the last synchronization. This is usually the preferred option for most scenarios because it's faster and less resource-intensive. 2--PolicyType Initial: This triggers a full synchronization. A full sync processes all directory objects and attributes from scratch, regardless of whether they have changed since the last sync. This option is more comprehensive but takes longer and uses more resources. Answer B is correct
TheFivePips 👍 3 Selected: B
The Start-ADSyncSyncCycle cmdlet has two policy types: Delta: This policy type performs a delta (or incremental) synchronization, syncing only the changes since the last sync. Initial: This policy type performs a full synchronization, syncing all objects and attributes. To immediately replicate the new user information to Azure AD, the Delta synchronization is typically sufficient because it syncs recent changes. The correct command for this scenario should be: Start-ADSyncSyncCycle -PolicyType Delta Thus, the correct answer is: B. No The -PolicyType Initial performs a full synchronization, which is more extensive than necessary just to sync a new user account.
Rahulchowchow 👍 1
A. Yes Explanation: The provided solution, running the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet, effectively meets the goal of immediately replicating the newly created user account in your on-premises Active Directory to Azure AD. Initial Synchronization: However, for newly created or modified objects, you can trigger an immediate synchronization cycle using the Start-ADSyncSyncCycle cmdlet. The -PolicyType parameter specifies the type of synchronization cycle to initiate. In this case, -PolicyType Initial forces a full initial synchronization, meaning it prioritizes syncing any objects that haven't been synchronized yet, including the newly created user account.
Markoduk 👍 1 Selected: A
A is the right answer
BanthonyB 👍 1 Selected: A
Yes, the solution meets the goal. Running the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet will initiate a full synchronization cycle, which includes replicating new user information from the on-premises Active Directory to Azure AD immediately1.
Nico1973 👍 1
Solution Analysis: The command Start-ADSyncSyncCycle -PolicyType Initial triggers a full synchronization cycle in Azure AD Connect. This cycle is used to immediately synchronize all changes, including the newly created user account, from the on-premises Active Directory to Azure AD. Conclusion: Answer: A. Yes The given solution meets the goal of replicating the user information to Azure AD immediately.
shobhitmathur18 👍 1
The Start-ADSyncSyncCycle cmdlet is used in PowerShell to manually start a synchronization cycle for Azure Active Directory (Azure AD) Connect. This cmdlet is often utilized to initiate an immediate synchronization of directory changes from on-premises Active Directory to Azure AD, instead of waiting for the next scheduled synchronization cycle.
tsummey 👍 2 Selected: B
This is a bad question. The PowerShell cmdlet 'Start-ADSyncSyncCycle -PolicyType Initial' would work, but the word 'immediately' in the requirements makes B a better choice. The powershell cmdlet 'Start-ADSyncSyncCycle -PolicyType Delta' will only synchronize the changes since the last sync. It would be faster than 'Start-ADSyncSyncCycle -PolicyType Initial' and come close to meeting the 'immediately' requirement
azmlan 👍 2
As per to chatgpt answer is A Running the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet initiates an initial synchronization cycle between your on-premises Active Directory and Azure AD. This command ensures that changes made in the on-premises Active Directory, such as creating a new user account, are replicated to Azure AD immediately. Therefore, yes, the solution meets the goal of replicating the newly created user information to Azure AD immediately.
ClayG5 👍 1
B (NO) is the only correct answer. No, running the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet does not meet the goal. This cmdlet initiates a full synchronization cycle, which is not necessary for replicating a single new user account to Azure AD. Instead, you should use the Start-ADSyncSyncCycle -PolicyType Delta cmdlet, which performs a delta sync, replicating only the changes made since the last sync cycle, including the new user account. For immediate replication of a single object, you might also consider using the Start-ADSyncSyncCycle -PolicyType Delta cmdlet, which is specifically designed for such tasks
Forkbeard 👍 1
This totally depends on what you subjectively experience as 'immediately'. How many users, sites, how much bandwidth? Six users, one site, symmetrical Gb connections: yes, I'd say initial is pretty immediate. Eight thousand users, sixty sites, dial-up connections: I'd say not immediate. The answer lies somewhere in between and is subjective, hence the answer cannot be binary. I hereby reject the question!
Morgan91 👍 1
Answer is B - NO Run Start-ADSyncSyncCycle -PolicyType Delta for delta Start-ADSyncSyncCycle -PolicyType Initial is for full sync cycle
roses2021 👍 2
The answer is NO. Please refer to the Microsoft link below: https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-feature-scheduler#full-sync-cycle
3c5adce 👍 2
A- YES. Start-ADSyncSyncCycle -PolicyType Delta is the ideal route - but - if you had to go the "Start-ADSyncSyncCycle -PolicyType Initial" it would work (but slowly). Given that some questions and answers are outdated, I would still say A, YES.
varinder82 👍 2
Final Answer: B (No)
DataTraveler 👍 4 Selected: B
The answer is explicitly stated in the Microsoft documentation at https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-feature-scheduler "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."
learnazureportal 👍 1
Yes. The solution provided, running the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet, would initiate an immediate synchronization of the newly created user account from the on-premises Active Directory to Azure AD.
3c5adce 👍 1
I put the question in ChatGPT and here is the answer: No, the solution does not meet the goal. The Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet initiates a full synchronization cycle for all synchronization policies. While this would replicate the user information to Azure AD, it might not be immediate, and it would also synchronize all objects, not just the newly created user account. A more suitable solution would be to run the Start-ADSyncSyncCycle -PolicyType Delta PowerShell cmdlet, which initiates an incremental synchronization cycle and replicates only the changes, including the newly created user account, to Azure AD immediately.
varinder82 👍 1
Final Answer : A
SarahMed 👍 1
Hello, please when do you pass the exam?
MCLC2021 👍 1
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
Jobalos009 👍 2 Selected: B
The answer is B. The question said "you create a new user", it suggests that the initial sync have been done.
Azlank24 👍 1
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.
Damina 👍 2
I have attended the Sample test from Microsoft portal, They have mentioned option A as answer
tashakori 👍 1
Yes is right
18c2076 👍 2
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)
18c2076 👍 3
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.
3c5adce 👍 1
That's right! Start-ADSyncSyncCycle -PolicyType Delta is the ideal route - but - if you had to go the "Start-ADSyncSyncCycle -PolicyType Initial" it would work but slowly. Given that some questions and answers are outdated, I would still say A, YES.
MelKr 👍 3 Selected: A
"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.
gil906 👍 2 Selected: A
A is correct, Delta will work as it's just a single user.
ITLearner 👍 3 Selected: B
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.
ITpower 👍 1
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
Saurabh_Bhargav 👍 1
A Start-ADsyncsynccycle -policy
JW36 👍 3
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 ?
_gio_ 👍 1 Selected: A
i think a
pradeept4 👍 1
The correct answer is A(YES). Here the question is not about the DELTA or INITIAL but the manual triggering of Sync Cycle instead waiting for the next automatic trigger.
jensdevopstraining 👍 8 Selected: A
This question has 3 variants: 1. Solution: You run the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet. 2. Solution: You use Active Directory Sites and Services to force replication of the Global Catalog on a domain controller. 3. Solution: You restart the NetLogon service on a domain controller. We all agree solution 2 and 3 are wrong. I think everyone that thinks the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet solution is wrong is focusing too much on the word "immediately". It will start the sync immediately. It will just take some time. The question does not ask for the quickest solution, it is asking for to start the sync immediately. I think Microsoft has at least 1 correct answer to this question set and therefore I will answer A on this.
Matheusinho 👍 2 Selected: A
Although the Full sync is more time-consuming than the Delta sync, it will kick off the sync anyway, therefore my answer is A. https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-feature-scheduler#full-sync-cycle
ef094b65596c14 👍 1
B. No, the solution does not meet the goal. The correct approach would be to use Start-ADSyncSyncCycle -PolicyType Delta to immediately replicate the new user information to Azure AD.
XavierG 👍 2
Answer is B. Key Word "Immediately" 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.
hoo 👍 1
B is correct
go4adil 👍 1
Answer is B (No) 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. Above text is quoted from MS Learn https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-feature-scheduler
AD_Dude 👍 3 Selected: B
B is the Correct answer. Start-ADSyncSyncCycle -PolicyType Delta is the right command. Initial - force a complete sync but note that the length of sync time would be greatly increased. Delta - initialize the AzureAD Sync immediately
Grodaz0 👍 2
The answer is No: For a delta sync cycle (start-adsyncsynccycle delta), you can use the below syntax Start-ADSyncSyncCycle -PolicyType Delta For a full sync cycle (start-adsyncsynccycle full), you can use the below syntax Start-ADSyncSyncCycle -PolicyType Initial
Kopf 👍 2
if anyone is going to buy a contributor access kindly get to know that i am also planning and we can share the bill (Ex. if 5 people one account 5-7 dollars each).
Yuraq 👍 2
B 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/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler
pal40sg 👍 1 Selected: A
Start-ADSyncSyncCycle -policy initial
F_Ahmad 👍 1
Answer is A https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler
ExamTopics1_EIS 👍 3
Start-ADSyncSyncCycle -PolicyType Delta is the correct answer for a single addition. Initial would work too, but take a long time in a large company, Especially if Users, groups and devices are syncing. I am sure the question has been updated by now.
Push_Harder 👍 1
Answer: B (No) Both A and B are correct, technically. However, a full Azure AD sync takes longer as it goes through all the Active Directory objects and synchronizes them again. The only use case in which you need to do a full synchronization is when you change the Azure AD Connect configuration. Note the term "immediately" used in the question, so B is the best answer.
yashsj 👍 1
I think the correct answer yes Option A, although its not optimal but it meats the goal as the question did not specify it should take less time or it should be optimal. So it meets the goal
Ashwini_Gjh 👍 1
answer is no because The PowerShell cmdlet Start-ADSyncSyncCycle -PolicyType Initial is used to start an initial synchronization cycle for Azure AD Connect, which replicates all objects from the on-premises Active Directory to Azure AD. If you want to replicate a specific user's information to Azure AD immediately, you should use the Start-ADSyncSyncCycle -PolicyType Delta PowerShell cmdlet. The delta synchronization cycle is designed to replicate changes (including new user accounts) made in the on-premises Active Directory to Azure AD without waiting for the next scheduled synchronization.
Harau 👍 2
Answer is A (Yes) Initial will meet the goal since it syncs everything, including new changes. However, Delta is more than enough, since this syncs the more recent changes.
mzala 👍 1
B is the correct answer
Arun_U 👍 1 Selected: A
The PolicyType parameter can also be set to Delta, which will only synchronize the objects that have changed since the last synchronization cycle. However, in this case, you want to make sure that the new user account is synchronized immediately, so you should use the Initial policy type.
TobeReto 👍 1
B The catch there is that we get an Immediate sync
dddddddddddww12 👍 1
Answer is A, because the question is 'does it meet the goal' which it does, even though it takes long
Acrious 👍 3 Selected: B
B) B) As usual there are some deterministic things. 1. It says immediately. Initial will not be immediate so therefor it cannot be Initial. yes it will start essentially (immediately), but for all we know there are 100,000 accounts and you are about to replicate it all again 2. It says the User information needs to be done immediately. now I recognize that doing an initial will at some point get to the User information and I get that Initial or Delta will do that, but again, I believe the point they are looking at is, how do we do it "immediately" Not, how do we do it at all. So you have Time: Immediately Accounts: User (the new one) B only meets that to the intent of the question (IMHO)
GoldenDisciple2 👍 25 Selected: B
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
tercy 👍 2
Answer is B The directory server is already in existence. This is not initial migration
Ahja666 👍 5 Selected: B
B is correct. "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/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler
GoldenDisciple2 👍 1
Thank you for sharing. Needs more thumbs up. Word for word in the learn.microsoft article you shared, it literally uses the key word IMMEDIATELY and tells you to run the delta variation instead of the initial. Couldn't be any clearer than that.
Maclouis116 👍 1
Answer is No, The command to sync AD to AAD immediately is:Start-ADSyncSyncCycle -PolicyType Delta
urbanmonk 👍 1
The keywords "relicate .... immediately" in the question suggests the need for a delta sync to capture the changes. Another clear case of bad wording in this question as it has left some room for assumptions. But I will go with B(No)
Josete1106 👍 1
The answer is A (YES).
rgnanav 👍 1 Selected: A
Answer looks A, as they mentioned its already deployed as an hybrid, they want to replicate the newly created account, so delta sync would suffice for that.
SeregonAzDev 👍 1
I think that the question is incomplete. Does not specify if the initial sync was already done or not. That information could change the answer. If initial sync was already done, delta il faster (so the answer is no). Otherwise there is no difference (so the answer is yes)
XtraWest 👍 2 Selected: B
(B. No) The Start-ADSyncSyncCycle -PolicyType Initial cmdlet triggers a full synchronization cycle of Azure AD Connect, but it is not designed specifically for replicating a single user account immediately.
XtraWest 👍 2 Selected: B
B (No): the PowerShell cmdlet, Start-ADSyncSyncCycle -PolicyType Initial, is used for triggering an initial synchronization cycle in the Azure AD Connect tool, not for replicating user information from on-premises Active Directory to Azure AD.
Badhusha 👍 2
Correct Answer is (A) Yes. Explanation: The Delta sync will not start immediately. The Start-ADSyncSyncCycle cmdlet will schedule a delta sync to start at the next available opportunity. The next available opportunity may be within a few minutes, or it may be longer depending on the load on the Azure AD Connect server. If you need to sync changes to Azure AD immediately, you should use the Start-ADSyncSyncCycle -PolicyType Initial cmdlet. This will initiate a full synchronization, which will start immediately.
XtraWest 👍 1
B (No): To initiate an immediate synchronization of user information from the on-premises Active Directory to Azure AD in a hybrid coexistence configuration, you should use the following PowerShell cmdlet: Start-ADSyncSyncCycle -PolicyType Delta.
LPaul 👍 1
Start-ADSyncSyncCycle -PolicyType Initial this should be the script to replicate user information to Azure AD immediately.
LPaul 👍 1
Try to edit but i cant , the answer should be No , 1. Start-ADSyncSyncCycle -PolicyType Initial = This cmdlet can take some time depending on the size of the directory because of full synchronization cycle. 2. Start-ADSyncSyncCycle -PolicyType delta = This cmdlet synchronizes only the changes
picho707 👍 1
The answer is B because it will not replicate immediately.
RandomNickname 👍 3 Selected: B
As per MS article, take note of manually running; Full sync cycle A full sync cycle includes the following steps: Full Import on all Connectors Full Sync on all Connectors Export on all Connectors 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/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler
rogerius 👍 1
The answer is B: Microsoft Documentation: https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler 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. -> Param: -policyType initial runs a full sync
BeauChateau 👍 2 Selected: A
A. Yes. The solution meets the goal of replicating the newly created user account from the on-premises Active Directory to Azure AD immediately. The Start-ADSyncSyncCycle PowerShell cmdlet is used to manually start a synchronization cycle of Azure AD Connect, which replicates changes from the on-premises Active Directory to Azure AD. By specifying the -PolicyType parameter with a value of "Initial," a full synchronization cycle is initiated, which replicates all changes that have not been synchronized to Azure AD.
Madbo 👍 1
A. Yes, the solution meets the goal. The Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet forces a full synchronization of on-premises Active Directory to Azure AD, replicating any new user accounts created in the on-premises Active Directory immediately.
DF22 👍 4
Don't rely on 3rd party blogs. Use the MS documentation. The answer is B. 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. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
GohanF2 👍 1
It's incorrect. Answer: B (no) -Delta is missing, since it needs to be immediate. Command would be : Start-ADSyncSyncCycle -PolicyType Delta
VGRY 👍 4
For the scenario where a new user account has been created in the on-premises Active Directory and needs to be replicated to Azure AD immediately, using the -PolicyType Initial parameter with the Start-ADSyncSyncCycle cmdlet would be the better option. This is because the Initial policy type triggers a full synchronization of all objects in the on-premises Active Directory to Azure AD, while the Delta policy type only synchronizes changes that have occurred since the last synchronization. Since the new user account is not yet synchronized to Azure AD, a full synchronization is required to ensure that it is replicated immediately.
garmatey 👍 1
But wouldnt the creation of that new user be a change that was made and therefore sync from delta?
TunaSD 👍 1
No, the solution does not meet the goal. Running the Start-ADSyncSyncCycle -PolicyType Initial cmdlet initiates a full initial synchronization, which is not necessary in this case. To replicate the new user information to Azure AD immediately, you should run the following PowerShell cmdlet: Start-ADSyncSyncCycle -PolicyType Delta This cmdlet initiates a delta synchronization, which only synchronizes the changes made in the on-premises Active Directory, such as the new user account, to Azure AD.
eddy39 👍 1
I would choose B (No). There is no reason to perform an initial sync to synchronize recent changes. Although, the wording is ambiguous. Technically, an initial sync would synchronize those changes eventually.
GoldBear 👍 3 Selected: B
https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler 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.
mateq34 👍 3 Selected: B
Immediate - you need to use delta sync and not the initial sync
je_it 👍 2
B- No. To summarize, the main difference between “initial” and “delta” sync in AAD synchronization is that the initial sync transfers all the objects and attributes from the on-premises AD, while the delta sync only transfers the changes made since the last sync.
kklohit 👍 4 Selected: B
The solution partially meets the goal. The Start-ADSyncSyncCycle -PolicyType Initial cmdlet initiates an initial sync cycle, which replicates all the changes from on-premises Active Directory to Azure AD. However, it is not recommended to use this cmdlet unless it is the first synchronization cycle because it will affect the performance of the server. Instead, you should use the Start-ADSyncSyncCycle -PolicyType Delta PowerShell cmdlet, which will replicate only the changes made to the on-premises Active Directory since the last synchronization cycle. This cmdlet will allow you to replicate the new user account to Azure AD immediately
skydivex 👍 1
Answer A is correct. Question mentions the sync has been setup, but never talked about it is in progress or has been synced before.... A could be correct..
Emesias 👍 1
The question says Create an account, that means that it does not have an initial synchronization, therefore the answer is A
CommanderBigMac 👍 4 Selected: B
While -PolicyType Initial will work, it will take some time. The question specifically says that the new user data needs to be synced immediately, so -PolicyType Delta needs to be used.
TK2023 👍 1
https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler 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.
kkrGmail 👍 2 Selected: B
Initial sync - when you change synchronization rules and need it to take effect. delta sync - using last synchronization rules and sync updated on-premises AD user over to Azure AD.
Alphachoups 👍 1 Selected: A
Requirement is to replicate immediately without waiting the automatic synchronize task. So option A will comply the requirement because it will synchronize the user info immediately despite de fact that it will make a full sync.
CommanderBigMac 👍 1
The question specifically mentions the new user data needs to be synced, not to resync everything. "You create a new user account in the on-premise Active Directory. You now need to replicate the user information to Azure AD immediately." The new user's data needs to be replicated immediately, so Delta needs to be used.
fesioche 👍 2 Selected: B
https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler 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.
Rufusinski 👍 2 Selected: B
B is correct.
Crawfork 👍 2 Selected: B
Delta is what used
km_2022 👍 1
I would say B is answer as should be a delta Sync Run the following Command(s): For a Delta Sync (most common, and used for most situations): Start-ADSyncSyncCycle -PolicyType Delta For a Full Sync (only necessary in some situations): Start-ADSyncSyncCycle -PolicyType Initial
khaled_razouk 👍 2 Selected: A
Yes, the solution meets the goal. The Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet initiates an initial synchronization process between the on-premises Active Directory and Azure AD. This will cause the new user account information to be replicated to Azure AD immediately. After running this cmdlet, the initial synchronization process will begin, and the new user account information will be replicated to Azure AD. This will ensure that the user account information is available in Azure AD, and that the user can use their account to sign in to Azure AD-connected services.
BShelat 👍 1
Policy Type initial will take longer for implementing the full sync of all objects but it will still sync new user created in on premise AD with Azure AD. So it fulfills the requirement and hence answer is A.
darthfodio 👍 3 Selected: B
For the fastest update time, you should use -PolicyType Delta so that only the changes will sync to Azure AD.
Alphachoups 👍 1
It's not asked a "fastest" way but only an immediat synchronization so A is correct because the sync start directly even if it's a full sync.
DesolateMarauder 👍 2
No. 100%. Delta would be quicker as it would only process any changes from the last sync. Initial is the slowest method which would typically only be done, initially. For delta synchronization use the parameter -PolicyType Delta (used in most situations) For full synchronization, use the parameter -PolicyType Initial (rarely used) https://www.easy365manager.com/how-to-run-start-adsyncsynccycle/ https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
Alphachoups 👍 1
Same answer as above --> It's not asked a "fastest" way but only an immediate synchronization so A is correct because the sync start directly even if it's a full sync.
awsazgc 👍 4
Other options for this question: 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 Okay, then what is the answer?
fesioche 👍 2 Selected: B
Important! Don’t forget to include the “-PolicyType Delta” to only kick off a delta sync.
belaBen 👍 2 Selected: B
Answer is B, since "Delta" is already enough and fast for sync, "Initial" may cost over 30 min ~ 1 hour to do a full sync Start-ADSyncSyncCycle -PolicyType Delta
SnezaNS 👍 1
If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
Hyper 👍 3
The ideal command is with Delta, but in this serie of questions the unique correct offered answer is with Initial. So as Initial works, Initial is correct. If Delta appears in other question of the serie Delta will be Ok too.
UWSFish 👍 1
100%. Do people not understand how Microsoft exams work? This is not an academic discussion. A is the correct answer.
rupayan87 👍 1
you only have four options in the exam as i see from various dumps. start-adsyncsynccyle restart dirsync1 restart netlogon force replication of global catalog on a domain controller. looks like the fourth one is ideal here as that only syncs the particular domain controller. Disclaimer - i am not an AD guy
car10589 👍 2 Selected: B
Answer is B. The policy type is Delta
ushahid 👍 2 Selected: B
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. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
FurnishedFlapjack 👍 2 Selected: B
Was A, now after 2018 is B
Pancit 👍 4 Selected: A
The question is tricky and it doesn't indicate how large the On-prem AD is... You all assume it is a large infrastructure what if it is just a 10 to a 100 users.. It doesn't also indicate if the full sync cycle has occurred already for all we know the admin just created the sync server 15 min ago and untick the start sync process after installation of Azure AD connect which means full sync cycle haven't occurred yet.. Start-ADSyncSyncCycle -PolicyType Initial = This will get the job done regardless how big or small the infrastructure is. Even if the sync server was just created 15min ago, this will work regardless if the full sync cycle occurred already. The question will this achieve its goal to replicate AD? = YES
SpicyMonkey 👍 3
The answer is No, If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler#full-sync-cycle
cnduknthm 👍 1
This link clearly says not to use initial for immediate sync. Thankyou!
majerly 👍 2
Answer is B 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 from a PowerShell prompt.Start-ADSyncSyncCycle -PolicyType Initial Running a full sync cycle can be very time consuming, read the next section to read how to optimize this process.
AltHexMax 👍 1
Should be using -PolicyType Delta not Initial
Ntinsky 👍 2 Selected: B
I agree with imartinez
gabyrever 👍 2 Selected: B
New user changes will sync immediately if it is a "delta" and not an "initial" policy type.
NaoVaz 👍 3 Selected: B
In my opinion the correct answer is B) "No". The "Start-ADSyncSyncCycle -PolicyType Initial" command will do a full synchronization and therefore take quite some time depending on the amount of information being currently existing in the AD. The fastest way to perform a sync and the thing that is nearest with the requested immediate sync is the command "Start-ADSyncSyncCycle -PolicyType Delta", as described here: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler#delta-sync-cycle
BigBigChannel 👍 2
B is correct
Mev4953 👍 2
Immedialtely => Start-ADSyncSyncCycle -PolicyType Delta More time consuming => Start-ADSyncSyncCycle -PolicyType Initial https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler#:~:text=It%20could%20be,optimize%20this%20process.
EmnCours 👍 2 Selected: B
the question want the change to be immediate. If the Initial was run against a large directory, that could take some time. Instead, run a Delta to just capture the change made and sync it immediately: Start-ADSyncSyncCycle -PolicyType Delta. Thus answer is B, NO.
Tyy27 👍 2 Selected: B
Needs to be a delta sync for immediate synchronisation
sjb666 👍 1
I think answer is B, why would you want to sync full policy? Question asks for immediacy.
bhanukiran 👍 1
Answer is B (No) as initial policy does a full sync while Delta syncs last changes and is faster. https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
RalphLiang 👍 3 Selected: B
Delta is ok
GaaTYZA 👍 3 Selected: B
Answer is B. Delta is sync is the way to. Changes usually reflect within a few minutes.
Henk36 👍 2 Selected: A
However not the fastest option, initial sync definetely syncs the user to azuread.
Chosen_1010 👍 2
The question is focused on how do you replicate the user account not which is the fast or slowest to do it. But how you do push this information from the on-premises to the cloud...So A is the answer.
Bobdobbs242 👍 1
Exactly. The question doesn’t say fastest, it says immediately. The initial sync does just that. It may take longer to finish but it starts immediately.
Ahmed_Root 👍 1
the keywork here is "immediately" so it is not this one but Start-ADSyncSyncCycle -PolicyType Delta command that meet the requirement.
CTino 👍 3 Selected: A
Kicking off an initial sync meets the goal. Faster is to do a delta sync though ;-)
Azure_daemon 👍 2
looks the correct answer is B: The delta sync in Azure AD Connect is the most common form of synchronization. It only performs a partial synchronization of any changes since last synchronization, so it’s very quick. You trigger the delta sync from PowerShell using the following command: Start-ADSyncSyncCycle -PolicyType Delta.
sumit_das 👍 1
Question is : replicate the user information to Azure AD immediately. Start-ADSyncSyncCycle -PolicyType Delta -- This PowerShell script will immediately sync the urgent change. where as, Start-ADSyncSyncCycle -PolicyType Initial. - this PowerShell script will take longer time to initiate full sync. Answer is B (No) : PowerShell script - Start-ADSyncSyncCycle -PolicyType Initial is not fit for immediate sync.
Anzus 👍 2 Selected: B
t 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. https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
GiJoe1987 👍 4 Selected: A
Guys, Initial and Delta will both sync the the required data. Delta is all that is required but Initial will do plus more.
chrzanekz 👍 3
I think that it's true answer. It will sync data after all
gloawyn 👍 2 Selected: A
The -policy initial will start the sync "immediately". Don't over think the answer. It is not asked for the most efficient, fastest solution. Arguing that B is in favor of "immediate" solution is making the assumption that the result will be "immediate" which is not true because even a delta will take an amount of time to complete and will not be immediate. Meanwhile, starting the sync will be "immediate" with both delta and initial.
mmtechsolutionsinc 👍 3 Selected: B
inial is slow, delta immediately
Brother_99 👍 1 Selected: A
Answer A is correct as it start a sync immediately instead of waiting up to 30 minutes.
MrTea 👍 2 Selected: B
It is slow and inefficient to re-run an initial sync. As the name suggests, it is used for when you initially set up Azure AD Sync. You should use a delta sync for immediate syncing of new/updated objects.
AzureLearner76 👍 2 Selected: B
you need to use delta for immediate results
Pasmo 👍 1
The answer is B (No) The question states that the changes must be done immediately which means that on Powershell you must run Start-ADSyncSyncCycle-PolicyType Delta. If the requirement was to do the full sync cycle then you would run Start-ADSyncSyncCycle-PolicyType initial. This is time consuming.
Phlex 👍 1
the correct choice would be Start-ADSyncSyncCycle -PolicyType Delta. Start-ADSyncSyncCycle -PolicyType Initial takes way to long and would defeat the purpose of trying to speed this up.
CaptainChunk 👍 3 Selected: B
initial sync is a full sync, takes longer
Hari2017 👍 2
Common Guys: Answer is B - NO. Why? The question is clear with PolicyType Initial. Please note: The DirSyncServer connection is already established with Azure AD. That means Full sync was already run automatically for the first time when the connection is up. Here, the user was added later and needs to be synced ASAP. Therefore, Type Initial - Will run Full scan & Full Sync (From On-Prem) Type Delta - Will run the sync on Newly created objects (Delta) which is True.
9InchPianist 👍 2 Selected: B
As stated by other users, delta would meet the requirements of the question better because it will be quicker. Initial would sync everything.
Etan1 👍 1
You article is correct but the answer is A Run the following command to force a complete sync but note that the length of sync time would be greatly increased. Start-ADSyncSyncCycle -PolicyType Initial
GenjamBhai 👍 6
B is ok, delta for immediate sync, initial will take longer
nqthien041292 👍 1 Selected: A
Vote A
007Ali 👍 1 Selected: A
In addition to the comments below in favour of A, looking at the other proposed solutions in the series of questions, this is the one that would achive the desired result.
BeamerV 👍 3 Selected: A
the question is very tricky. It wants us to start the sync ASAP. so both cmdlets will start the sync right away once entered.. It does not mention that you need the synced account ASAP
Marski 👍 1
AD Connect is the synchronizer. Nice that there are solutions suggested in comments.
rohit_khandelwal 👍 2
Answer : A To initiate a Delta Sync, open Windows PowerShell and run: Start-ADSyncSyncCycle -PolicyType Delta To initiate a Full Sync, open Windows PowerShell and run: Start-ADSyncSyncCycle -PolicyType Initial As user is created new and no changes are made in existing to updated to replicate with Azure AD it should be Answer : A
Mozbius_ 👍 3
Not sure what to think here... I am preparing for az-104 and followed Microsoft Delivered course in December and beginning of the month to solidify and NEVER did the instructors mentioned anything about Star-ADSyncSyncCycle. It was basically not part of the syllabus nor in the standards labs. They talked about CSV imports though when talking about bulk imports and also AD Connect that's it. So I am not sure what to think. Perhaps the students are expected to expand on what was taught on their own for the exam? Who got this question the latest?
peymani 👍 1
As described here: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler 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, so if you need to replicate the user information to Azure AD immediately then run Start-ADSyncSyncCycle -PolicyType Delta.
Bere 👍 33
In the solution of this question they say “-PolicyType Initial”. However you must use “-PolicyType Delta” to get only the change made and sync it immediately. So the answer is “No”.
elishlomo 👍 2 Selected: B
The answer is NO. You need to make sure you're on the preferred domain controller in the real world. It would be best if you worked with what Start-ADSyncSyncCycle -PolicyType Delta.
kevinirl 👍 1
NO- As that will trigger full Sync
AltHexMax 👍 2 Selected: B
This explains it: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler#delta-sync-cycle "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."
Sara_Mo 👍 1
the correct answer is yes, because it means we do it manually and for the first time you should use initial
marco_aimi 👍 1
YES: is correct: MIND don't ask "with less time" or "solution to avoid network traffic", simple if works, so YES even should be better use delta
EleChie 👍 1
Answer A is correct - YES Since they need a "to replicate the user information to Azure AD immediately." A replicate means a full copy or an exact copy of AD. "full sync"
Barrie 👍 3 Selected: B
B is immediate
Agrim_09 👍 3 Selected: B
should be -Delta
Marutain 👍 1
I mean it DOES meet the goal..so I'd say A if it was best practice then it would be the Delta
Marutain 👍 1
Answer is idd B, my brain didnt comprehend the Immediately.
Prano 👍 1
Ans : B Start-ADSyncSyncCycle -PolicyType Delta - Will publish change immediately otherthan initial
DMouser 👍 3 Selected: B
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.
roukettas 👍 2 Selected: B
I will go with B based on this statement "You now need to replicate the user information to Azure AD immediately." Otherwise, A can be considered correct as well.
safwansalama 👍 2
as I see , the answer is NO : 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.
verifedtomic 👍 3 Selected: B
Check imartinez's comment for explanation.
zankuko_tenshi 👍 3
Start-ADSyncSyncCycle -PolicyType Initial - Will work but will take longer time to complete Start-ADSyncSyncCycle -PolicyType Delta - Will publish change immediately ANSWER: NO
MitchelLauwers1993 👍 1
we are Ms partners and have free test from uplearn the answer there is: Yes
Marski 👍 1
Fortunately there is official Microsoft doc described in this message chain. Thank you.
Bere 👍 4
As described here: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler 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, so if you need to replicate the user information to Azure AD immediately then run Start-ADSyncSyncCycle -PolicyType Delta. Answer is B. No
Eltooth 👍 4
Correct answer - No. - delta is needed for immediate.
Mikeyo 👍 6
For Immediate sync use -> Start-ADSyncSyncCycle -PolicyType Delta. https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler Full sync cycle A full sync cycle includes the following steps: Full Import on all Connectors Full Sync on all Connectors Export on all Connectors 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.
theOldOne 👍 4
When I read the question as "immediately" I think of it as not waiting for the automatic sync that would occur at a set interval and possibly delay someone logging in. By running the command I am forcing an "immediate" sync of the info. Sometimes it is difficult to tell what they are looking for as sometimes they want you to be as literal as possible and other times they expect you to understand what they are asking. In this case it does meet the objective that we do not have to wait for the auto sync but running the delta option may have been faster. So strange a question.
Pradh 👍 1
Agreed .. Running a Delta Sync through a scheduler at mid nigh 12:00AM is not immediate ...compared to running a manual initial sync command. But we could also run a manual delta sync instead of initial right ?
imartinez 👍 137
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.
skydivex 👍 13
The answer is A (YES), since the question did not mention the initial sync has been already done. A is correct
arunet 👍 9
B is the answer. https://techcommunity.microsoft.com/t5/itops-talk-blog/powershell-basics-how-to-force-azuread-connect-to-sync/ba-p/887043
juniorccs 👍 6
if the delta will be bring the last changes, so it's okay here, isn't it ? the answer should be then "YES" , correct ? where am I lost here ?
dupakonia 👍 3
"You now need to replicate the user information to Azure AD immediately." Based on the work "immediately" I would say the answer is NO. If we want to make this happen asap then we should go for Delsa sync
Vlako 👍 2
Answer is still yes. Though only Delta is required - the initial sync still meets the Goal.
Pradh 👍 1
Question says "You now need to replicate the user information to Azure AD IMMEDIATELY. " Still Yes ???
BenStokes 👍 7
Wrong answer. It is B. Delta sync should be used since initial will do full sync. To initiate a full sync cycle, run Start-ADSyncSyncCycle -PolicyType Initial from a PowerShell prompt. Ref # https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
GabeCanada 👍 4
"Initial" will force a full Sync while "Delta" just the changes since last sync. With the wording "Immediately" delta would be the correct option as the full sync depending on directory size could take hours... and the delta sync default is every hour. I still count as correct but this is a badly formulated question.
spektrum1988 👍 3
Why would you do an initial sync if it's already set up? A Delta sync is enough.

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Submitted for moderation before publishing. Keep it helpful and respectful.

Expert Analysis

Why the Answer Is Correct

Option B (No) is correct because the requirement is explicit: the new on-premises user must reach Azure AD immediately. Microsoft's Azure AD Connect feature scheduler documentation states that a full sync cycle consists of Full Import on all Connectors, Full Sync on all Connectors, and Export on all Connectors, which is a heavy, time-consuming operation. The same documentation prescribes the Delta policy for urgent changes, so running Start-ADSyncSyncCycle -PolicyType Initial on DirSync1 does not satisfy the timing requirement. As GoldenDisciple2 quoted from the official article, "then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta" is the sanctioned way to push a change right away. Therefore the proposed solution fails the stated goal and the answer is No.

Why the Other Options Are Wrong

Option A (Yes) would only be defensible if the question asked merely whether the user is eventually created, but the operative word is 'immediately' — an Initial cycle performs full discovery and processing of every connected source, which can take many minutes or longer on a real hybrid tenant. skydivex argued that A is right because the scenario never says an initial sync has already run, but that objection misses the point: even in a never-synced environment, the Delta policy is what the product documents for a manually triggered urgent cycle, and the Initial policy is reserved for provisioning or disaster-recovery style full rebuilds. Treating the Initial cmdlet as an 'immediate' mechanism conflates completeness with speed, which is exactly the distinction this question is built to test.

Community Comment Notes

imartinez captured the core reasoning, noting that "Delta, will kick off a delta sync and bring only the last change" and therefore fulfills the immediate requirement, and Bere added that using -PolicyType Initial "will perform a full sync and add the user account created but it will take time." GoldenDisciple2 backed this with the official scheduler article, and Mikeyo likewise cited the same doc while listing the Full Import/Full Sync/Export steps. On the opposing side, skydivex voted A arguing the initial sync may never have completed, while jensdevopstraining treated this as one variant of a three-part question and favored A; juniorccs openly asked "where am I lost here?" about the Delta-versus-Initial distinction, which is precisely the trap the correct answer resolves.

Official Reference

Exam Strategy

On hybrid sync questions, flag any timing adverbs — 'immediately', 'right away', 'urgently' — because they map directly to -PolicyType Delta, while Initial signals a full rebuild. Never assume an unstated prerequisite (like a missing initial sync) to justify an option; judge the cmdlet against the literal requirement.

Frequently Asked Questions

Why doesn't Start-ADSyncSyncCycle -PolicyType Initial sync a new user immediately?

Initial triggers a full sync cycle — Full Import, Full Sync, and Export on all connectors — which is far slower than the targeted Delta cycle needed for one urgent change.

Which cmdlet replicates one new on-premises user to Azure AD right away?

Run Start-ADSyncSyncCycle -PolicyType Delta from an elevated PowerShell prompt on the DirSync1 Azure AD Connect server to push only the latest directory changes.

More AZ-104 FAQ →

Related Analysis

Case study - This is a case study. Case studies are not time

A-Grade

Note: This question is part of a series of questions that pr

S-Grade

Note: This question is part of a series of questions that pr

A-Grade

Practice All AZ-104 Questions

Access 100 questions with complete answers and detailed explanations.

View Full AZ-104 Practice Test →

← Back to AZ-104 Study Guide