Azure File Sync Endpoint Availability Within 24 Hours

Configure Azure Files and Azure Blob Storage

Answer File1: Endpoint1 only. File2: Endpoint1, Endpoint2, and Endpoint3.

HOTSPOT You have an Azure File sync group that has the endpoints shown in the following table. [sampleXML/xmlfile-161_2.png] Cloud tiering is enabled for Endpoint3. You add a file named File1 to Endpoint1 and a file named File2 to Endpoint2. On which endpoints will File1 and File2 be available within 24 hours of adding the files? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area: [sampleXML/xmlfile-162_1.jpg]

Community Insight

The question tests the difference between real-time USN journaling for on-premises agents and the periodic detection job for cloud-tiered endpoints. The common trap is assuming cloud storage syncs in real-time like on-prem storage.

This page explains the synchronization behavior of Azure File Sync endpoints, specifically how on-premises changes sync instantly while cloud endpoint tiering scans occur every 24 hours. It clarifies that files added to on-prem servers are immediately available across all sync group endpoints.

Candidates often select all endpoints for both files, failing to recognize that cloud-tiered endpoints only reflect new cloud content after the 24-hour scan cycle completes.

Community Discussion (117 comments)

SPDumps 👍 1

File1: Endpoint1, Endpoint2, and Endpoint3 File2: Endpoint1, Endpoint2, and Endpoint3 A sync group synchronizes all endpoints with one another. It doesn't matter where you add the file; it eventually reaches every location. File2 (added to a server endpoint): the Azure File Sync agent detects the change almost immediately, uploads it to the cloud endpoint (Endpoint1), and from there it propagates to Endpoint3. The entire process takes just a few minutes. File1 (added directly to the Azure file share—i.e., the cloud endpoint): this is the tricky part. Changes made directly to the file share are not detected instantly; they are picked up by a change detection job that runs once every 24 hours. Since the question asks about the timeframe "within 24 hours," the file does indeed reach all endpoints within that period. Cloud tiering on Endpoint3 does not change the answer. With tiering, the file might exist locally only as a pointer (reparse point), but it still appears in the namespace and remains accessible (downloading on demand). For the exam, "available" means visible and accessible, so tiering is a distractor.

Lord_ashy 👍 1

Answer from copilot: Within 24 hours, Azure File Sync will have synchronized both files across the entire sync group: File1 (added to Endpoint1 – cloud endpoint): Available on Endpoint1, Endpoint2, and Endpoint3. File2 (added to Endpoint2 – server endpoint): Available on Endpoint1, Endpoint2, and Endpoint3.

AzureGeek79 👍 3

Correct answer: File1: Endpoint1, Endpoint2 and Endpoint3 File2: Endpoint1, Endpoint2 and Endpoint3

ahmadniknam 👍 2

File1: Endpoint1, Endpoint2 and Endpoint3 File2: Endpoint1, Endpoint2 and Endpoint3 https://learn.microsoft.com/en-us/azure/storage/file-sync/file-sync-planning

varinder82 👍 1

Final Answer: (key- within 24 hrs) File1: Endpoint1 only File2: Endpoint1, Endpoint2 and Endpoint3

tashakori 👍 2

File1: Endpoint1, Endpoint2 and Endpoint3 File2: Endpoint1, Endpoint2 and Endpoint3

Amir1909 👍 1

Endpoint1, Endpoint2 and Endpoint3 - Endpoint1, Endpoint2 and Endpoint3

nandakku 👍 4

This Question appeared in Exam attended in September 15th. Corredt answer is File 1 -------> Endpoint 1 only - Becuase question mentioned "within 24 hours". File 2 -----> Endpoint 1,2 and 3

Mitazure7 👍 1

What's going on within 24 hours?

rodrigo2186 👍 7

https://www.youtube.com/watch?v=_Dv5HrAqsn4

Josete1106 👍 1

File1: Endpoint1 only File2: Endpoint1, Endpoint2 and Endpoint3

Madbo 👍 4

File1: Answer: a. Endpoint1 only Explanation: File1 is added to Endpoint1 which is a cloud endpoint. Cloud tiering is enabled for Endpoint3 but it is not guaranteed that the file will be tiered within 24 hours. Therefore, File1 will only be available on Endpoint1 within 24 hours. File2: Answer: d. Endpoint1, Endpoint2, and Endpoint3 Explanation: File2 is added to Endpoint2 which is a server endpoint. Azure File Sync syncs files between all endpoints in the sync group. Therefore, File2 will be available on Endpoint1, Endpoint2, and Endpoint3 within 24 hours.

Exilic 👍 2

If the question was changed to after 24 hours, Why has Examtopics not changed the question also?

nmnm22 👍 1

thank you toeee

orionduo 👍 2

File1: Endpoint1 only It is a cloud endpoint, and it is scanned by the detection job every 24 hours. Note: They changed the question in Exam from "within 24 hours" to "after 24 hours". So, the answer is: File1: Endpoint1, Endpoint2 and Endpoint3

KeerthiVasanG 👍 6

Azure Files doesn't have change notification or journaling yet, so Azure File Sync has a scheduled job called a change detection job. This job is initiated every 24 hours. That means that if you change a file in the Azure file share, you might not see the change on the on-premises file share for up to 24 hours.

NaoVaz 👍 5

1) "Endpoint1 only" 2) "Endpoint1, Endpoint2, and Endpoint3" Files added to the Cloud Endpoint are scanned every 24 hours. With the rest of the server endpoints files are synced automatically. Reference: https://docs.microsoft.com/en-us/training/modules/extend-share-capacity-with-azure-file-sync/2-what-azure-file-sync

EmnCours 👍 9

File1: Endpoint1 only It is a cloud endpoint, and it is scanned by the detection job every 24 hours. File2: Endpoint1, Endpoint2 and Endpoint3 With the on-premises servers the file is scanned and synced automatically after it's being added. Note: They changed the question in Exam from "within 24 hours" to "after 24 hours". So, the answer is: File1: Endpoint1, Endpoint2 and Endpoint3 File2: Endpoint1, Endpoint2 and Endpoint3

pari205 👍 9

Why correct answers are not updated in the main pages? isn't misleading

Lazylinux 👍 1

File1: Endpoint1 only File2: Endpoint1, Endpoint2 and Endpoint3 comments as per others

manalshowaei 👍 1

1: Endpoint1 only 2: Endpoint1, Endpoint2 and Endpoint3

atilla 👍 1

the file is available on endpoint 3 as pointer to azure share right?

InvisibleShadow 👍 4

This question came in the exam today 8/Mar/2022. I passed the exam, 95% questions came from here.

Akshay_S_A 👍 1

what's the option you had selected in your exam ? Did you get it right ?

klexams 👍 2

on your statement "The cloud endpoint is not the Azure file share, the server endpoint is." - It is wrong. The cloud endpoint is the Azure file share that's part of a sync group https://docs.microsoft.com/en-us/learn/modules/extend-share-capacity-with-azure-file-sync/2-what-azure-file-sync

magichappens 👍 1

for maximum 24 hours. The job runs every 24 hours so in the worst case it runs after 24 hours which means all changes are done "within 24 hours".

amiri7171 👍 4

All is needed to understand this topic deeply is in this article. https://docs.microsoft.com/en-us/learn/modules/extend-share-capacity-with-azure-file-sync/2-what-azure-file-sync

njain453 👍 2

File1: Endpoint1 only -> cloud endpoint will be scanned after 24 hrs. File2: Endpoint1, Endpoint2 and Endpoint3-> server endpoint automatically scanned

jaydee7 👍 10

Why nobody is mentioning Cloud Tiering? it is just meant to ignore?

drae2210 👍 2

"If you make a change to the cloud endpoint (Azure file share) directly..." The cloud endpoint is not the Azure file share, the server endpoint is. The cloud endpoint would be the on-premise file share because it is in the cloud already. Azure file shares are put on on-premise servers. If you make changes to the cloud endpoint (on-premise file share), the changes are immediately detected and replicated to the Azure file share (the on-premise server or server endpoint in this case). "Azure File Sync (server endpoint) has a scheduled job called a change detection job. This job is initiated every 24 hours. So, if you change a file in the Azure file share(server endpoint), you might not see the change on the on-premises file share (cloud endpoint) for at least 24 hours." Mlantonis's answers are correct, but the explanation above by Mcc is not.

JouPa 👍 1

that cleared it up for me , thanks

stdevops 👍 18

Passed Oct 29 score 940. This question was asked. Was "after 24 hours" File1: Endpoint1, Endpoint2 and Endpoint3 File2: Endpoint1, Endpoint2 and Endpoint3

ScoutP 👍 2

This question was asked on exam taken on Sept 30, 2021

Mercator 👍 6

What I got wrong here as non native english speaker: What does it mean within 1 hour? Google: Within an hour" means "within 60 minutes." " Within the hour" means "before the next hour is reached." So within 24 hours means the time period before (!) the 24 hours have passed.

josevirtual 👍 1

Thanks pal for clarifying, I was about to go crazy!

Mukesh_Aggarwal_07 👍 10

Within 24hours: File1: Endpoint 1 only File2: Endpoints 1, 2 & 3 After 24hour File1: Endpoint 1, 2 & 3 File2: Endpoints 1, 2 & 3

Mukesh_Aggarwal_07 👍 1

File1: Endpoint 1, 2 & 3 File2: Endpoints 1, 2 & 3

AubinBakana 👍 17

The answer is wrong. How can file 1 be in Endpoint3 only when it is already in Endpoint1? What they are trying to establish is if you know that the online file will not be synchronized until after 24h. The only files that are sync within that period are the On-Prem files in the sync group. Since File1 is already in Endpoint 1, within 24 it will only be in Endpoint 1 File 2 is an on-prem file - replicate to the cloud and across all endpoints connected to the sync group Within 24hours: File1: Endpoint 1 only File2: Endpoints 1, 2 & 3 After 24hour File1: Endpoint 1, 2 & 3 File2: Endpoints 1, 2 & 3 Unfortunately cloud tiering has nothing to do with the answer here. It's just there to confuse you. Thank You

nachito 👍 1

Thanks a lot for your answer, it is the most clear and easy to understand

Parry11 👍 3

In this case the answer is- 1. Endpoints 1,2,3 2. Endpoints 1,2,3

RoastChicken 👍 1

Correct answer: File 1: Endpoint 2 and Endpoint 3 - When you add a file to the Cloud endpoint it takes 24 hours to be sync with the server endpoints https://docs.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal%2Cproactive-portal#deploy-the-storage-sync-service and https://docs.microsoft.com/en-us/azure/storage/files/storage-files-faq?toc=/azure/storage/filesync/toc.json#afs-change-detection File 2: Endpoint 1, 2 and 3

tzaroon 👍 1

Answers are for file1 will be endpoint 1 and 3 because file 1 is already at endpoint 1 and within 24 hours which is the file sync limit. The file will be available within 24 at endpoint 3 only because of the enabled cloud tier.

juniorccs 👍 2

Thanks a lot!

Anshul174 👍 3

Answer is File1: Enpoint3 and File2: all Endpoints. When you enable cloud teiring you get a cached copy of file1 on Ep3

ScreamingHand 👍 1

Am I right in thinking that; File2, once copied to Endpoint2 will be immediately sync'd to the Cloud endpoint, - from there it may take 24 hours for it to be replicated to Endpoint3. Therefore File2: Endpoint2 and Endpoint3 only.

CloudyTech 👍 4

Tested File 1- Endpoints 1 File 2 - Endpoints 1, 2, 3

mkoprivnj 👍 3

1) E1, E2, E3 2) E1, E2, E3

lockc1811 👍 6

omg. people. its endpoint 1 only & second question is endpoints 1, 2 & 3. microsoft arent trying to trick you with their exam q's

PersonT 👍 3

hahahaha

mlantonis 👍 776

Correct Answer: File1: Endpoint1 only It is a cloud endpoint, and it is scanned by the detection job every 24 hours. File2: Endpoint1, Endpoint2 and Endpoint3 With the on-premises servers the file is scanned and synced automatically after it's being added. Note: They changed the question in Exam from "within 24 hours" to "after 24 hours". So, the answer is: File1: Endpoint1, Endpoint2 and Endpoint3 File2: Endpoint1, Endpoint2 and Endpoint3 Reference: https://docs.microsoft.com/en-us/learn/modules/extend-share-capacity-with-azure-file-sync/2-what-azure-file-sync

Barachan 👍 1

very clear explanation even with additinal note, many thanks!

Alscoran 👍 2

I disagree. My understanding of "within 24 hours" means that something could be done before 24 hours, but definitely will be. So if you add file 1 at 7am and the detection job runs at 8am, then you'll see the file everywhere within an hour. If the job runs at 6:59, then again, the file will be everywhere within 24 hours (7am). So shouldn't it be all three endpoints for File 1 ?

Juwizee 👍 3

Mlany!!! Thanks...

ServerBrain 👍 4

mlantonis, thank you. I would like to send you a trophy, all the way from South Africa. God Bless you.

xRiot007 👍 4

The question text seems to have changed several times. At this time, its phrased as "within 24 hours", so your first answer is correct. MS probably has both variants and some people encounter just one of them during the exam.

GohanF2 👍 8

MAN , YOU ROCK !

TinyRunner 👍 4

thank you mlantonis

RougePotatoe 👍 24

Their ref link section: "how does it work?" 1. "That means that if you change a file in the Azure file share, you might not see the change on the on-premises file share for up to 24 hours." 2. "Azure File Sync uses Windows USN journaling on the Windows Server computer to automatically start a sync session when files change on the server endpoint. Changes made to the on-premises file share are immediately detected and replicated to the Azure file share." Just in case yall wanted the quote without having to look for it in their ref link.

codeScalable 👍 21

God bless you @mlantonis. You are a real gem

klexams 👍 4

Spot on! If within 24hrs, then F1: E1 only. If after 24hrs then F1: E1 E2 E3. Azure Files (cloud EP) doesn't have change notification or journaling yet so it needs scheduling to detect changes which is every 24hrs.

mcc 👍 6

Correct, to add: "You can make changes to any cloud endpoint or server endpoint in the sync group and have your files synced to the other endpoints in the sync group. If you make a change to the cloud endpoint (Azure file share) directly, changes first need to be discovered by an Azure File Sync change detection job. A change detection job is initiated for a cloud endpoint only once every 24 hours. For more information"

AubinBakana 👍 3

Thank you so much. That's something I thought was a little confusing as it would make their revealed answer wrong.

suriyaswamy 👍 4

Good Info

Harshul 👍 4

Excellent Explaination!

bacana 👍 1

sorry. File1 will be at endpoints 1 and 3 (cloud tearing maintains a local copy), but there is no option 1 and 3 in the response, so endpoint1 or endpont3 only. At endpoints 1, 2 and 3 because it was added to endpoint 2.

bacana 👍 1

"On which endpoints will File1 and File2 be available within 24 hours of adding the files?" File1 will be at endpoints 1 and 3 (cloud tearing keeps a local copy), but there is no option 3 in the response, so server1 only. At endpoints 1, 2 and 3 because it was added to the local server 2

kawsar 👍 1

Cloud tiering is enabled for Endpoint3. Which means you need to manually download the files. That is why first answer is Endpint 1 Only, Second question is right.

Lkk51 👍 3

Disagree. "Regardless of whether cloud tiering is enabled, your Azure file share always has a complete copy of the data in the sync group." https://docs.microsoft.com/en-us/azure/storage/file-sync/file-sync-deployment-guide?tabs=azure-portal%2Cproactive-portal#create-a-server-endpoint https://docs.microsoft.com/en-us/azure/storage/file-sync/file-sync-cloud-tiering-overview

nfett 👍 1

Agree with nilf here if the question logic has changed to after 24 hours.

coders1234 👍 2

within is actually quite clear, it means before or up to 24 h

ZetaZeti 👍 17

If within means less than 24 hours: 1) Endpoint 1 only 2) E1, E2, E3 If within means less than or EQUAL TO 24 hours: 1) E1, E2, E3 2) E1, E2, E3

Kiano 👍 2

I think everyone is being confused by the term within 24 hours. If withon 24 hours does not actually mean 24 hours, then there should have been another opiton for: File 1: only on Endpoint1 (gets replicated within 24 hours, as we do not know how many minutes have passed since the last schedule was run and the file was copied.) File 2: On endpoint2 and endpoint1. As it is instantly gets replicated to the cloud. Because we do not have the option: Endpoint1 and 2 for file 2, it means that the answer should be: File1: On all three endpoints File2: On all three endpoints. Please see my reasoning regarding "within 24 hours" to understand what I mean.

Nilf 👍 27

They changed in Exam "within 24 hours" with "after 24 hours" So the answer is: - File 1 - Endpoint 1,2,3 - File 2 - Endpoint 1,2,3

Benny4321 👍 1

Good, because "within" is very confusing, as it leaves several scenarios open. "After" will make sure that all is synced after a period of 24 hours.. no question about that.

mc3 👍 4

Why would File1 not be available on the drive that it was loaded on to?

ms70743 👍 5

File 1- endpoints 1 File 2 - endpoints 1, 2, 3

ZUMY 👍 7

Important here within or after 24 hours. If we say within 24 as job already run Then file 1 and file 2 will be avail in all end points. If we take within 24 hours as shedular not run yet Answers are 1. Endpoint 1 only 2. Endpoint 2 and Endpoint 1 only So based on the answer given we have to assume schedular had alredy been run within 24 hours. Bcz we have not given answer matching shedular had not run. So I go for >>> all endpoints have all the files within 24 hours

Wizard69 👍 1

Ok, the question asks what files will be available within 24 hours... Sometime within the 24 hours the detection job will run and sync file1 to all endpoints, so the answer is that both files will be available on all endpoints

ZUMY 👍 3

File1 : EndPoint1 - Changes made in Server Endpoint immediately reach Cloud Endpoint File2 : EndPoint1 ,EndPoint2 ,EndPoint3 - ( File1 & 2 File 2 are now in Cloud Endpoint and will replicate to Server endpoints via a 24 hour inbuid scheduler) Further referece https://docs.microsoft.com/en-us/learn/modules/extend-share-capacity-with-azure-file-sync/2-what-azure-file-sync "How does it work? Azure File Sync uses a software-based agent that's installed on the on-premises server that you want to replicate. This agent communicates with the Storage Sync Service. Azure File Sync uses Windows USN journaling on the Windows Server computer to automatically start a sync session when files change on the server endpoint. So changes made to the on-premises file share are immediately detected and replicated to the Azure file share. Azure Files doesn't yet have change notification or journaling. So Azure File Sync has a scheduled job called a change detection job. This job is initiated every 24 hours. So if you change a file on the Azure file share, you might not see the change on the on-premises file share for at least 24 hours."

toniiv 👍 1

Answer is not correct: -File1 will be in all endpoints within 24 hours (worse scenario will be sync occurs in 24 hours, but normal scenario will occur before the 24 hours). Within 24 hours is defined from the first second until the last second of the 24 hours, and covers the 24 hours in the worse scenario which will happen if you copy the file just after the moment sync event occurs, so before the next 24 hours the file will be synced to all rest of endpoints in the sync group.) File2 will be also in all endpoints

CISCOGUY01 👍 1

The answer given is correct. When the change detection job determines that files have changed, Azure File Sync initiates a sync session. The change detection job is initiated EVERY 24 hours, NOT WITHIN 24 hours. link:https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-troubleshoot?tabs=portal1%2Cazure-portal

shetoshandasa 👍 2

1.Since file2 is added to the server-side, then the file would be replicated to cloud share immediately. [as of now, it exists on ednpoint2 and endpoint1] 2.Since file1 is added to the cloud-share, then it would take up to 24 hours for the file to be replicated to the server-side. [as of now, it exists only in endpoint1] based on (1) and (2), file1 and file2 should be replicated to all endpoints after 24 hours

Naqsh27 👍 1

I believe it will be available on all endpoints. Azure file sync will sync all on premise (or cloud) file servers to a cloud endpoint. I have set up several of these sync groups. Cloud endpoint 1 / \ / \ / \ Prem endpoint 2 Prem Endpoint 3 Whatever is in endpoint will come 'down' to the prem endpoints almost immediately whatever is on prem will sync up to cloud eventually (within 24 hours). the sync group keeps copies of files on all the endpoints. The cloud tiering is neither here no there. The file pointers are still available on the endpoints even if the actual data on disk isn't . Semantically it is "available" to access even if the actual data is in the cloud. this works from on prem up to cloud, making the cloud as the primary data store (relatively)

iamkl00t 👍 2

NO... on prem will sync to cloud immediately... cloud will sync to on own within 24 hours "Azure File Sync uses Windows USN journaling on the Windows Server computer to automatically start a sync session when files change on the server endpoint. So changes made to the on-premises file share are immediately detected and replicated to the Azure file share. Azure Files doesn't yet have change notification or journaling. So Azure File Sync has a scheduled job called a change detection job. This job is initiated every 24 hours. So if you change a file on the Azure file share, you might not see the change on the on-premises file share for at least 24 hours." https://docs.microsoft.com/en-us/learn/modules/extend-share-capacity-with-azure-file-sync/2-what-azure-file-sync

maktry 👍 2

I had a different answer, then read the answers below and got confused even more. Any one with on-prem server can test this please!

Fab10234 👍 27

According to what is saying MLM0607 the correct answer for the File1 is Endpoint1 because it is a cloud endpoint and it is scanned by the detection job every 24 hours and for the File2 the answer is Endpoint1, Endpoint2 and Endpoint3 because with the on-premises servers the file is scanned and synced automatically after it's being added.

polpum 👍 2

come in 15/01/2021

JayBee65 👍 7

LM0607's answer are File 1: Endpoint 1 only File 2: Endpoint 1, Endpoint 2 and Endpoint 3!

Acai 👍 1

This is too tricky, i'll be using this to think so pardon me. so you said in your response "you might not see the change on the on-premises file share for at least 24 hours." but they said "within 24 hrs" ( ͡° ͜ʖ ͡°) so 23 hrs and 59mins or less. So Mircosoft is playing word games with us, but this means if you add a file to an Azure File Share(Cloud Endpoint) 24hrs has to go by till it appears on a on prem server that's true. Another thing that's true is this, Microsoft says "we encourage you to primarily access the files through the Windows Server cache when the Azure file share is being used with Azure File Sync. This is because Azure Files today lacks an efficient change detection mechanism like Windows Server has, so changes to the Azure file share directly will take time to propagate back to the server endpoints. So if you make changes to the Cloud Endpoint, it won't be accessible until 24 hrs, also caching here has nothing to do with nothing. So file 1 should just be on endpoint 1 and file 2 which is added to on-prem Windows Server that can detect the change should be on all 3.

Acai 👍 1

Endpoint 1 is not on prem...

JayBee65 👍 5

No, Endpoint 1 is a cloud endpoint, with tiering, so file 1 will not appear on EP2 or EP3 unless the file is requested, so File 1 is EP1 only.

Shexo 👍 9

I am getting confused reading all of these comments, could someone be kind enough to state which are the correct answers for each of the file...

DodgyD 👍 1

I think... Box1: I would say Endpoint 1 and Endpoint3, because cloud tiering is enabled on endpoint3 so, file1 is cached locally there too. Box2: Endpoint1/2/3 because sync group makes it available in Endpoint1, it’s already on Endpoint2, and cloud tiering on endpoint3 makes it cached locally. there is scant information about this feature.

iamkl00t 👍 1

cloud tiering doesn't mean what you're suggesting... it means that only 'hot' files are synced to the local server, not that all files are 'cached' there

Seema_exam 👍 1

No "I think" pls

MLM0607 👍 45

I think the correct answer should be that the both files will be visible on both end points. Quote from : https://docs.microsoft.com/en-us/learn/modules/extend-share-capacity-with-azure-file-sync/2-what-azure-file-sync "How does it work? Azure File Sync uses a software-based agent that's installed on the on-premises server that you want to replicate. This agent communicates with the Storage Sync Service. Azure File Sync uses Windows USN journaling on the Windows Server computer to automatically start a sync session when files change on the server endpoint. So changes made to the on-premises file share are immediately detected and replicated to the Azure file share. Azure Files doesn't yet have change notification or journaling. So Azure File Sync has a scheduled job called a change detection job. This job is initiated every 24 hours. So if you change a file on the Azure file share, you might not see the change on the on-premises file share for at least 24 hours."

vince60370 👍 6

Just THANK YOU. No one seemed to have noticed it: Endpoint1 and 2 are ON PREMISE. So if there is a change ON PREMISE, it is IMMEDIATELY synchronized. Your link just perfectly explains it.

gekkehenkie84 👍 3

As per: You can make changes to any cloud endpoint or server endpoint in the sync group and have your files synced to the other endpoints in the sync group. If you make a change to the cloud endpoint (Azure file share) directly, changes first need to be discovered by an Azure File Sync change detection job. A change detection job is initiated for a cloud endpoint only once every 24 hours. Shouldn't this be all endpoints for both answers?

Kiano 👍 1

Completely agree

fedztedz 👍 16

Answer is not correct. - File 1 only on Endpoint 1 - File 2 only on Endpoint 1,2,3

waterzhong 👍 13

File 1: Endpoint 1, Endpoint 2 and Endpoint 3 File 2: Endpoint 1, Endpoint 2 and Endpoint 3

waterzhong 👍 2

When a file is tiered, the Azure File Sync file system filter (StorageSync.sys) replaces the file locally with a pointer, or reparse point. The reparse point represents a URL to the file in Azure Files.

xMilkyMan123 👍 2

Tell me what exactly you did in your Lab

janshal 👍 16

you waited 24 hour for the job to be sync? I think the answer is all endpoints because the syc job run every 24 hour so even if your created the file a second after the sync jobs started it will be sync within 24 hours

as7dfjasdf3 👍 17

File 1 will be detected by the Azure File Sync agents within 24h on the server endpoints, so that means that File1 will be on all three endpoints (A change detection job is initiated for a cloud endpoint only once every 24 hours). It will only get tiered on endpoint 3 once it is considered "cool" and needs to free up storage (When the file volume on a server exceeds the volume free space threshold you set, it will tier the coolest files to Azure Files until your free space percentage is met). File2 will get pushed to all three endpoints as well.

shnz03 👍 1

Good one! Thank you on the note about endpoint 3.

diligent176 👍 4

Correct! And this question is worded badly - "within 24 hours" could mean the sync has run or maybe not... "After 24 hours" would be more accurate. Yes the files get to all endpoints after 24 hours, that is the point of it. Tiering is not relevant, the file is still accessible from the endpoints.

Skankhunt 👍 57

Should be File 1: Endpoint 1 only File 2: Endpoint 1, Endpoint 2 and Endpoint 3

vince60370 👍 2

Not agree. Please read MLM0607's answer below.

prashantjoge 👍 3

This is correct. Confirmed it in labs

diligent176 👍 10

This is a poorly worded question. You don't know when the 24 hour sync will run. It may be 5 minutes from now, or 23 hours - hard to say. File1 will be available on all endpoints "no later than" 24 hours after it is created. Whether it is tiered (cached) or not is irrelevant - the file is still "available" on all endpoints.

Matkes 👍 11

File1 and File2 will be on each endpoint. You can make changes to any cloud endpoint or server endpoint in the sync group and have your files synced to the other endpoints in the sync group. If you make a change to the cloud endpoint (Azure file share) directly, changes first need to be discovered by an Azure File Sync change detection job. A change detection job is initiated for a cloud endpoint only once every 24 hours. https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-deployment-guide?tabs=azure-portal%2Cproactive-portal

vince60370 👍 1

@Matkes, your answer is correct but not your explanation. Please read MLM0607's answer below.

jeremyburrows 👍 1

The questions says within 24 hours. the change detection only runs once every 24 hours. So wouldn't file1 only be on endpoint 1? I don't see how it could be what is in the picture

ketan05 👍 3

So when we add any file on the cloud end point. Then the file will not be available on it?

Anon6969 👍 7

Anyone able to explain this question?

dandirindan 👍 3

is there any reason to all endoints why choice b is all, is there anyone to undesrtand

Comments & Corrections

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

Expert Analysis

Why the Answer Is Correct

File1 is created in Endpoint3 (Cloud). Because Cloud Tiering is enabled, the file exists as a 'stub' or metadata in the cloud share, but the local agent on Endpoint1 does not see it until the detection job runs. This job typically runs every 24 hours. Therefore, within 24 hours, File1 is only visible on Endpoint1 (where the agent is installed and presumably synced previously or via initial sync) or potentially not yet synced if strictly interpreted, but standard exam logic dictates that cloud-only additions take time to propagate to edge nodes. However, the most critical distinction is File2. File2 is added to Endpoint2 (On-Premises). The Azure File Sync agent uses Windows USN Journaling to detect changes instantly. These changes are uploaded to the Azure file share and then pushed to other connected endpoints (Endpoint1 and Endpoint3) almost immediately. Thus, File2 is available on Endpoint1, Endpoint2, and Endpoint3 within the timeframe.

Why Other Candidate Answers Are Wrong

Selecting Endpoint3 for File1 implies immediate propagation from the cloud to the on-premises server, which contradicts the asynchronous nature of the detection job. Selecting only Endpoint1 and 2 for File2 ignores the fact that the cloud endpoint (Endpoint3) receives the update from the source (Endpoint2) via the cloud backend, making it available there too.

Community Comment Notes

Community consensus highlights that on-premises changes sync automatically due to USN journaling, while cloud changes wait for the 24-hour scan. Some users noted exam variations changing 'within' to 'after', but the core technical principle remains: On-Prem = Instant; Cloud-Tiered New Content = Delayed.

Official Reference

https://docs.microsoft.com/en-us/azure/storage/files/storage-sync-files-planning#how-does-azure-file-sync-work

Exam Strategy

Memorize the sync triggers: On-premises uses USN Journaling for instant sync. Cloud tiering uses a detection job for periodic syncs (default 24 hours). When analyzing scenarios, identify the source location first; if it's on-prem, assume instant availability everywhere. If it's cloud-only new content, assume delay.

Frequently Asked Questions

Why isn't File1 available on Endpoint2 and 3 immediately?

File1 was added to the Cloud endpoint. The on-premises agents rely on a detection job to find new cloud content, which runs periodically (every 24 hours), not instantly.

How does Azure File Sync detect on-premises changes?

It uses the Windows USN Journaling feature on the server to monitor file system changes and trigger an immediate sync session with the Azure file share.

More AZ-104 FAQ →

Related Analysis

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