When configuring inter-tenancy VCN peering, what is the purpose of the "peer ID" provided by the requesting tenancy to the accepting tenancy?

Context: Inter-tenancy VCN peering connects VCNs across different OCI tenancies using Remote Peering Connections (RPCs).
Option A: Authentication of the root user is handled by IAM policies, not the peer ID, which is a technical identifier—incorrect.
Option B: The peer ID is the OCID of the RPC created by the requesting tenancy. It uniquely identifies the RPC, allowing the accepting tenancy to target and establish the peering—correct.
Option C: CIDR blocks are part of VCN configuration and shared separately, not via the peer ID— incorrect.
Option D: Security rules are defined by NSGs or security lists, not the peer ID—incorrect. Conclusion: The peer ID’s purpose is to identify the requesting tenancy’s RPC, making Option B the correct answer. From Oracle’s documentation: "For inter-tenancy peering, the requesting tenancy provides the OCID of its Remote Peering Connection (RPC), known as the peer ID, to the accepting tenancy. The accepting tenancy uses this ID to establish the peering." This confirms Option B. Reference: Remote VCN Peering Across Tenancies - Oracle Help Center (docs.oracle.com/en-us/iaas/Content/Network/Tasks/remoteVCNpeering.htm#cross-tenancy).