Q: 8
When configuring inter-tenancy VCN peering, what is the purpose of the "peer ID" provided by the
requesting tenancy to the accepting tenancy?
Options
Discussion
Going With B, is correct here. Had something like this in a mock and the peer ID always meant the unique OCID for the Remote Peering Connection, not for auth or CIDR. Pretty sure they use it to link both sides during setup. Anyone disagree?
Yeah, B is the right call. The peer ID lets the accepting tenancy know exactly which Remote Peering Connection to connect to in the other tenancy-it's basically the OCID pointer. It's not for auth or CIDR and definitely not about security rules. I've double-checked Oracle docs on this, so 99% sure here. Anyone see it used differently?
Pretty sure it's B. The peer ID is just there to uniquely ID the Remote Peering Connection, not for authentication or network details. If anyone thinks otherwise let me know.
Makes sense, so it's B. The peer ID is really just the OCID of the RPC, not user authentication or CIDR. I think Oracle doc even mentions this process directly. Let me know if I'm off here.
A is wrong, B. Only the peer ID actually maps to the RPC OCID across tenancies. Saw a similar question in exam reviews and they noted this catch.
Be respectful. No spam.
