Explanation
On premise: customizable,specific requirements,resources
Cloud: scale, built-in automated backup, strong stable internet

To establish an eBGP session between R1 and R2, the correct action is to configure R1 with the neighbor statement that specifies R2's IP address and its autonomous system (AS) number. This is done by using the command neighbor 2.2.2.2 remote-as 65002 under the BGP process on R1. This configuration tells R1 that it should establish a BGP session with a neighbor at IP address 2.2.2.2 which is in AS 65002. References: The Implementing and Operating Cisco Service Provider Network Core Technologies (SPCOR) course provides detailed instructions on configuring BGP sessions in a service provider environment

The script is missing an event to trigger the EEM applet. In Cisco EEM (Embedded Event Manager), an event is a specific occurrence on a network device that is detected by EEM. The "event none" statement is used in EEM scripts when the applet is not triggered by any system events but can be manually run. In this case, since the script aims to apply an access list, it doesn't need to be triggered automatically by any system events but can be invoked as required.
References: Implementing and Operating Cisco Service Provider Network Core Technologies source documents or study guide

SD-Access Wireless Architecture Control Plane Node -A Closer Look
Fabric Control-Plane Node is based on a LISP Map Server / Resolver
Runs the LISP Endpoint ID Database to provide overlay reachability information
+ A simple Host Database, that tracks Endpoint ID to Edge Node bindings (RLOCs)+ Host Database supports multiple types of Endpoint ID (EID), such as IPv4 /32, IPv6 /128* or MAC/48 + Receives prefix registrations from Edge Nodes for wired clients, and from Fabric mode WLCs for wireless clients + Resolves lookup requests from FE to locate Endpoints + Updates Fabric Edge nodes, Border nodes with wireless client mobility and RLOC information