A. Delete and re-add the security group.

B. Check the NSX Security policy to ensure the security group has been used in a policy.

C. Go into vCenter/NSX and push the objects to Panorama

D. Go into Panorama and synchronize the Address objects with NSX

A. does not integrate natively with VXLAN tagging, network equipment can convert VXLAN flows to VLANs and send those VLANs to Palo Alto Networks firewalls

B. does not integrate with VXLAN tagging, so virtual appliances cannot be provided, but hardware appliances can be offered at the data center gateway border

C. integrates with VXLAN. but scripting is necessary, and Professional Services should be engaged

D. integrates fully into VXLAN architectures if they are provided by VMware

A. Configure the rule in Panorama and push it to NSX-V Manager.

B. Add a network introspective service and select Redirect to Service under Action.

C. Select Fabric > Access Policies > Quick Start and follow the prompts

D. Select Steering Rules > 3rd Party Firewalls > Palo Alto Networks and then populate the object with the required details

A. Egress-Slot

B. Round Robin

C. Ingress-Slot

D. Hash

A. The only difference is in the architecture - where the Console is hosted

B. Only Prisma Cloud Compute offers API based cloud protection.

C. Prisma Cloud Enterprise does not offer workload protection.

D. Prisma Cloud Compute offers lowered runtime defensive capabilities because there is no PANW cloud hosted component.

A. Create security groups and mark them as exchangeable.

B. Create security groups with tags marked as shareable.

C. Create security groups and use them in an NSX-to-Palo Alto Networks redirection policy.

D. Create security groups only.