Free NSE7_PBC-7.2 Exam Braindumps (page: 3)

Page 2 of 8

Refer to the exhibit.



Your senior administrator successfully configured a FortiGate fabric connector with the Azure resource manager, and created a dynamic address object on the FortiGate VM to connect with a windows server in Microsoft Azure. However, there is now an error on the dynamic address object, and you must resolve the issue.

How do you resolve this issue?

  1. Run diagnose debug application azd -l on FortiGate.
  2. In the Microsoft Azure portal, set the correct tag values for the windows server.
  3. In the Microsoft Azure portal, access the windows server, obtain the private IP address, and assign the IP address under the FortiGate-VM AzureLab address object.
  4. Delete the address object and recreate a new address object with the type set to FQDN.

Answer(s): B

Explanation:

https://docs.fortinet.com/document/fortigate-public-cloud/6.2.0/azure-administration- guide/985498/troubleshooting-azure-fabric-connector



Refer to the exhibit.



You are deploying a FortiGate-VM in Microsoft Azure using the PAYG/On-demand licensing model. After you configure the FortiGate-VM, the validation process fails, displaying the error shown in the exhibit.

What caused the validation process to fail?

  1. You selected the incorrect resource group.
  2. You selected the Bring Your Own License (BYOL) licensing mode.
  3. You selected the PAYG/On-demand licensing model, but did not select correct virtual machine size.
  4. You selected the PAYG/On-demand licensing model, but did not associate a valid Azure subscription.

Answer(s): D

Explanation:

https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-setup- guide/organize-resources



An Amazon Web Services (AWS) auto-scale FortiGate cluster has just experienced a scale-down event, terminating a FortiGate in availability zone C.

This has now black-holed the private subnet in this availability zone.

What action will the worker node automatically perform to restore access to the black-holed subnet?

  1. The worker node applies a route table from a non-black-holed subnet to the black-holed subnet.
  2. The worker node moves the virtual IP of the terminated FortiGate to a running FortiGate on the worker node's private subnet interface.
  3. The worker node modifies the route table applied to the black-holed subnet changing its default route to point to a running FortiGate on the worker node's private subnet interface.
  4. The worker node migrates the subnet to a different availability zone.

Answer(s): C

Explanation:

Official documentation, failover process on a single AZ, https://github.com/fortinet/aws- cloudformation-templates/blob/main/FGCP/7.0/SingleAZ/README.md#failover-process || Outbound failover is provided by reassigning the secondary IP addresses of ENI1\port2 from FortiGate 1's private interface to FortiGate 2's private interface. ##Additionally any route targets referencing FortiGate 1's private interface will be updated to reference FortiGate 2's private interface.##
https://github.com/fortinet/aws-cloudformation-templates/tree/master/LambdaAA- RouteFailover/6.0



Which two statements about the Amazon Cloud Services (AWS) network access control lists (ACLs) are true? (Choose two.)

  1. Network ACLs are stateless, and inbound and outbound rules are used for traffic filtering.
  2. Network ACLs are stateful, and inbound and outbound rules are used for traffic filtering.
  3. Network ACLs must be manually applied to virtual network interfaces.
  4. Network ACLs support allow rules and deny rules.

Answer(s): A,D

Explanation:

https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html https://aws.amazon.com/premiumsupport/knowledge-center/security-network-acl-vpc-endpoint/ -Network ACLs are stateless. You must define rules for both outbound and inbound traffic.






Post your Comments and Discuss Fortinet NSE7_PBC-7.2 exam with other Community members:

NSE7_PBC-7.2 Discussions & Posts