What is the role of the "Perimeter" profile in Autonomous Threat Prevention?

The correct answer is A. The Perimeter profile is designed for perimeter gateway protection, where traffic commonly flows north-south between internal users/servers and external networks such as the internet. Official R82 Autonomous Threat Prevention documentation describes perimeter profiles as optimized for perimeter gateways to prevent cyberattacks and protect users browsing the web, data centers, incoming email, and FTP. Option B and D describe the Monitor profile concept, where detection/simulation can occur without enforcement impact. Option C is misleading: Recommended for Perimeter may be a default or recommended profile in many deployments, but not every security deployment should use the same perimeter profile. Cloud/data center, internal network, and guest network profiles exist because different segments have different traffic patterns and risk models. The core role of the Perimeter profile is strong protection for external-facing north-south exposure. Reference topics: Autonomous Threat Prevention Profiles, Recommended for Perimeter, Strict Security for Perimeter, north-south traffic protection.