Q: 4
What capability does Oracle Cloud Infrastructure (OCI) Storage Gateway provide for connecting on-
premises applications with OCI Object Storage?
Options
Discussion
D imo, since Storage Gateway sits in the middle and lets legacy apps use NFS to talk to object storage. No re-coding for REST needed, that's the point. Unless I'm missing something subtle in the question wording.
Looks like it’s D since Storage Gateway translates NFS to Object Storage, so the apps don’t need changes for REST support. That’s how OCI bridges legacy systems. Let me know if I missed some trick here.
Option D Storage Gateway uses NFS so on-premises apps can write to Object Storage without touching REST APIs. The no code change part is key here, but if I'm missing some OCI nuance let me know.
C not D. I was under the impression Storage Gateway does NFS but apps still need tweaks for REST APIs on the backend side. Maybe I'm wrong here, but C feels close if you have to adapt for API use.
Feels like D, because Storage Gateway lets apps use NFS without needing REST API changes. Pretty sure that's what Oracle designed it for.
D tbh, since apps just use NFS with Storage Gateway, no need to touch REST. Could be missing some OCI gotcha but this matches what I’ve seen in other practice sets.
You don’t need to rewrite your apps for REST, so D fits best. NFS protocol is used as a bridge. Pretty sure about this, but always open for corrections if anyone knows an edge case.
Its D, no REST API changes needed for the apps since NFS is used as the bridge to Object Storage.
NFS bridge lets you use existing apps as-is, so D. No application changes for REST needed in this setup.
Be respectful. No spam.
