Free AWS SOA-C03 Actual Exam Questions - Question 15 Discussion
data must be available locally. The backup application can write only to block-based storage that is
compatible with the Portable Operating System Interface (POSIX).
Which backup solution will meet these requirements?
Maybe D. Since the backup app needs block storage with full local data availability, gateway-stored volumes are the only Storage Gateway option that keeps everything on-premise and supports POSIX-compatible block storage.
C/D? Cached volumes (C) don’t keep all data local, so they don’t meet the requirement. Stored volumes (D) keep full data locally and support block storage, making D the solid choice here.
Option C can't work because gateway-cached volumes keep only a subset of data locally, which doesn't meet the "all data must be available locally" requirement. So D is the better fit.
It’s D because only gateway-stored volumes store all data locally on-prem with block-level access.
This one definitely feels like D again. Gateway-stored volumes keep all the data on-premises, which is what the question stresses, and they provide block-level storage that works with POSIX. The other options either don’t store the full dataset locally or aren’t block storage, so they don’t really fit the requirement for the backup app.
D - The key point is having all data locally available as block storage, and gateway-stored volumes provide that exact setup with iSCSI access. Other options don’t guarantee full local data presence.
Probably C makes sense too because gateway-cached volumes keep a local cache and store the full data in AWS, which might still work if the app mainly needs local block access. It’s not fully local like D, but still block-based and POSIX compatible.
Option D, since it keeps all data locally with block storage, unlike cache-based options.
It’s D because gateway-stored volumes keep the full dataset on-premises and expose it as iSCSI block storage, which is POSIX compatible. The other options don’t offer local block storage directly.
D imo. Gateway-stored volumes keep the entire dataset on-premises, which is exactly what the question asks for. Since the backup software needs block storage compatible with POSIX, gateway-stored volumes fit because they expose iSCSI targets locally. The other options either use object storage (S3) or only cache a portion locally (gateway-cached), so they don’t fully meet the “all data must be available locally” requirement. Also, S3 and Glacier aren’t block storage and won’t work with legacy backup apps expecting POSIX block devices.
Guessing D is right because gateway-stored volumes keep all the data locally and expose it as block storage over iSCSI, which should work with the POSIX requirement. The other options either don’t offer block storage or don’t keep data fully local. Cached volumes (C) still rely on cloud storage and might not have all data locally at all times, so that doesn’t fit the requirement well. Seems like D fits best for a backup app needing full local access to block-level storage.
D. Gateway-stored volumes keep all data locally and expose block storage via iSCSI, which fits POSIX compatibility better than cached volumes that rely mostly on cloud storage. This matches the full local availability need.
Maybe D is the best fit here since gateway-stored volumes keep all data locally and present block storage via iSCSI, which should be compatible with POSIX. The key is that the data must be fully available on-premises, which rules out gateway-cached volumes (C) because they only cache a portion locally. S3 options (A and B) don’t provide block storage and wouldn’t meet the local availability requirement. So, D seems like the only choice that ticks all the boxes for this scenario.
C/D? Gateway-cached volumes also provide local cache with block storage, could fit too.
This one feels like D since gateway-stored volumes keep all data locally, matching the requirement for local availability and POSIX-compatible block storage. So, D.
Not C, because gateway-cached volumes store most data in AWS, not locally, so they don’t meet the requirement of having all data on-prem. D is better since gateway-stored keeps everything local.
D imo, since only gateway-stored volumes keep all data locally and offer the block storage interface needed. Cached volumes won’t meet the local data availability requirement fully.
D for sure, since only gateway-stored volumes keep all data on-prem and support block storage.
D. Only gateway-stored volumes keep all data on-site and provide the block storage interface the app needs. Cached volumes still rely on cloud storage for most data, which breaks the “all local” rule here.
D imo, because gateway-stored volumes provide full local storage access, unlike cached volumes that only keep a subset on-site. This ensures the backup app’s POSIX block storage needs are met with all data local.