Q: 12
Your organization uses a combination of OCI and AWS. Applications in OCI frequently access services hosted in AWS. You are experiencing slow and inconsistent data transfer speeds when transferring large files between the two clouds. You have a Site-to-Site VPN, but are considering other options. Which option is NOT a valid design consideration for improving the data transfer performance between OCI and AWS?
Options
Discussion
C, checking compute pricing doesn't change inter-cloud network speed. B looks tricky but it's legit for boosting transfer rates.
C , compute pricing isn’t about transfer performance at all. I think it’s not related to the actual data transfer speed issues.
Not sure B is a trap here, but C doesn’t impact network performance. Compute pricing isn’t about bandwidth or transfer speed.
C tbh, pricing compute isn't going to help your transfer issues between clouds. Easy trap since B looks expensive but still valid for performance.
Option C, Compute pricing doesn't really touch transfer performance, so it's not a valid design consideration for boosting data speed between OCI and AWS I think. Open to other takes if I'm off base.
B/C? I was thinking B at first since adding a dedicated interconnect sounds overkill if VPN exists, but C is probably a trap. Pricing compute doesn't really touch network speed, right? If I'm missing something on B let me know.
This popped up in my mock, pretty sure it's C. Compute pricing doesn't really affect transfer throughput at all.
Its C here. Pricing compute resources isn't about network throughput or transfer speed, that's a bit of a red herring. B could look odd but it's an actual design move to boost bandwidth between clouds.
C is right here. Saw something like this on a recent test-compute resource pricing is about cost not performance, so it wouldn't really factor into network design for inter-cloud transfers.
B , because using a dedicated interconnect seems expensive and not always needed if VPN is already set up. Network latency usually has more to do with distance and optimization than throwing in another provider option, I think. Open to pushback here though.
Be respectful. No spam.