Follow the frame
Work out how frames and packets move between PC2 and the server SRV1, which is on another subnet behind R1. Ping the server from PC2, look at the ARP and MAC tables on the way, and answer. Packet Walk (in the toolbar) shows every hop if you want to check your thinking.
How it works: this is VulnTech NetLab, a network simulator running in your browser. Click a device in the diagram to open its console and type commands, just like on real equipment (? shows help, Tab finishes a word). Click a cable to inspect it. Tasks tick themselves off as you complete them; questions are answered in the box under each task. Your work is kept if you reload; Reset starts the network over.
Solution explanation
10.9.9.10 isn't in PC2's subnet, so PC2 ARPs for its gateway 10.1.1.1 and sends every frame to R1's MAC on Gi0/0, with 10.9.9.10 still the destination IP. R1 takes the packet out of the frame, looks up 10.9.9.0/24, ARPs for the server on Gi0/1 and puts the same packet in a new frame. MAC addresses change at every hop; IP addresses don't (until NAT, later). That is also why the first ping was lost: R1 dropped it while ARPing for the server.
Show solution
[PC2]
ping -c 3 10.9.9.10
ip neigh
[R1]
enable
show ip arp
show interfaces g0/0