Quiz
High Availability (HA)
Este quiz tem tipos de pergunta que abrem no player de sempre.
Perguntas do quiz (34)
1All FortiManager devices in cluster must be same model and firmware
- AVerdadeiro
- BFalso
2Designed for one primary device and multiple secondary devices - Up to four secondary devices
- A(five devices in total)
- B(six devices in total)
3Supports geographical redundancy
- AHA sync is TLSv1.0 over TCP port 5199
- BHA sync is TLSv2.0 over TCP port 9951
4Each HA member operates independently - Unique IP for each FortiManager
- AVerdadeiro
- BFalso
5Upgrading the primary FortiManager not upgrades all secondary devices at the same time
- AVerdadeiro
- BFalso
6HA Synchronization
- Make all changes to the FortiManager database on primary device, then synchronize With one or more [blank_start]secondary devices[blank_end] - Purpose
- To replicate primary [blank_start]device database[blank_end]
- To promote secondary device(s) in case of [blank_start]primary device[blank_end] failure
- What is synchronized?
- All [blank_start]device configurations[blank_end] (including global databases)
- All [blank_start]configuration revisions[blank_end]
- What is not synchronized?
- [blank_start]Configuration settings[blank_end] for:
- interface. routes, HA, SNMP: log. FortiAnalyzer [blank_start]feature configuration[blank_end]
- FortiGuard
- Antivirus/IPS packages. web filter, [blank_start]antispam databases[blank_end]
- Local logs and Alert [blank_start]Message Console logs[blank_end] (data)
- [blank_start]FortiGate logs[blank_end] sent to FortiManager- Asecondary devices
- Bdevice database
- Cprimary device
- Ddevice configurations
- Econfiguration revisions
- FConfiguration settings
- Gfeature configuration
- Hantispam databases
- IMessage Console logs
- JFortiGate logs
7HA failure behavior
If primary FortiManager fails, you
- Must reconfigure all other [blank_start]secondary devices[blank_end] to point to new primary device
- Must manually reconfigure one of the secondary devices to become the [blank_start]primary device[blank_end]
- Don’t need to reboot devices when promoting from [blank_start]secondary to primary[blank_end]- Asecondary devices
- Bprimary devices
- Csecondary to primary
- Dprimary to secondary
- Eprimary device
- Fsecondary device
8HA Failure Behavior
If secondary FortiManager fails, you
- Can reconfigure [blank_start]primary device[blank_end] to remove the peer IP of the failed secondary device
- Can leave the configuration so that when [blank_start]secondary device[blank_end] comes online, it can resynchronize with the primary- Aprimary device
- Bsecondary device
- Csecondary device
- Dprimary device
9[blank_start]Heart Beat Interval[blank_end]: The time in seconds that a cluster member waits between sending heartbeat packets and expecting to receive a heartbeat packet from the other cluster member. By default, the heartbeat interval is 5 seconds.
[blank_start]Failover Threshold[blank_end]: The maximum number of heartbeat intervals that can occur without response before FortiManager assumes that the other cluster members have failed. By default, the failover threshold is 3. Based on the default settings, the failure detection time is 15 seconds (5 second heartbeat interval x 3 failovers).- AHeart Beat Interval
- BFailover Threshold
10Configure HA using System Settings (Choose 4)
- ASelect role
- BIP and serial number for cluster member
- CCluster ID and group password should be same for all members
- DCad add up to four secondary devices if roles is selected as Master
- ECad add up to four primary devices if roles is selected as Master
- FSelect HA type
11The HA heartbeat packets use TCP port [blank_start]5199[blank_end]. Run sniffers on TCP port [blank_start]5199[blank_end] to ensure clusters members are able to send and receive HA heartbeat packets.
Check event and [blank_start]alert message console[blank_end] for messages related to HA
Run [blank_start]real-time debugs[blank_end] to verify HA synchronization
Check HA status to confirm HA is fully synchronized- A5199
- B9951
- C5199
- D9951
- Ealert message console
- Falert fortiview
- Greal-time debugs
- Hreal-time diagnose
12Real time debugs
- Adiagnose debug application ha 255
diagnose debug enable - Bdiagnose debug application ha 9951
diagnose debug enable
- Adiagnose debug application ha 255
13What configuration is not synchronized between FortiManager HA cluster members?
- AA. FortiGuard database
- BB. Global database
14Which statement about a FortiManager HA cluster is true?
- AA. Each HA cluster member must have a unique IP address.
- BB. It supports active-active configuration.
15Periodically connects to FortiGuard servers
Downloads [blank_start]license statuses[blank_end] for managed devices
Syncs [blank_start]FortiGuard packages[blank_end]
Unless configured for closed [blank_start]network operation[blank_end]- Alicense statuses
- Blicense upgrade
- CFortiGuard packages
- DFortiguard renovation
- Enetwork operation
- Fnetwork maintenance
16Terminology used
- AFortigate:
FDS
FGD
FortiClient:
FCT
FGC
Public FortiGuard Distribution Network:
FDN - BFortiClient:
FDS
FGD
Fortigate:
FCT
FGC
Public FortiGuard Distribution Network:
FDN
- AFortigate:
17FortiManager Port and Protocol Usage
Uses TCP port [blank_start]443[blank_end] to obtain updates from public F DN
[blank_start]Four[blank_end] main FortiGuard services on FortiManager to create a replica of public FDN for FortiGate and FortiClient- A443
- B9951
- CFour
- DSix
- EFive
18Process
- AFortigate
FDS: fdslinkd
FGD: fdslinkd
FortiClient
FCT: fctlinkd
FGC: fctlinkd - BFortigate
FDS: fdslinke
FGD: fdslinke
FortiClient
FCT: fctlinke
FGC: fctlinke
- AFortigate
19Enabling Built-In FDS (FortiGuard) Two Steps
- AEnable service access settings on interface
Enable FortiGuard services - BEnable service access settings on system settings
Enable FortiGuard services on interface
- AEnable service access settings on interface
20Antivirus and IPS update services are enabled together
- AVerdadeiro
- BFalso
21Updates available for: (Choose 4)
- AFortigate
- BFortiClient
- CFortiAnalyzer
- DFortiMail
- EFortiSwitch
- FFortiAP
22How frequently FortiManager communicates with public FDN servers for AV/IPS updates?
- Aten minutes
- Bfive minutes
- Cone minute
23The [blank_start]Receive Status[blank_end] displays the package received, latest version, size, to be deployed version, and update history for the antivirus and lPS signature packages received from FortiGuard.
The [blank_start]Update History[blank_end] shows the update times, the events that occurred, the status of the updates, and the versions downloaded.- AReceive Status
- BUpdate History
24Main statuses: (Choose 5)
- AUp to down
- BUnknown
- CProblem
- DPending
- ENever Updated
- FUp to Date
- GLast Updated
25[blank_start]Up to Date[blank_end]: The latest package has been received by the FortiGate device
[blank_start]Never Updated[blank_end]: The device has never requested or received the package
[blank_start]Pending[blank_end]: The FortiGate device has an older version of the package because of an acceptable reason (such as the scheduled update time is pending)
[blank_start]Problem[blank_end]: The FortiGate device missed the scheduled query, or did not correctly receive the latest package
[blank_start]Unknown[blank_end]: The FortiGate device’s status is not currently known- AUp to Date
- BNever Updated
- CPending
- DProblem
- EUnknown
26Three main processes
- [blank_start]fgdlinkd[blank_end] - Responsible for downloading web filter and email filter databases
- [blank_start]fgdups[blank_end] - Responsible for database merging and consolidating smaller delta files into larger files
- [blank_start]fgdsrv[blank_end] - Serves FortiGate and FortiClient for web filter and email filler requests- Afgdlinkd
- Bfgdups
- Cfgdsrv
27Server override mode: Two modes
- ALoose:
Default mode
Allows fallback to the other FDN server
Strict:
FortiManager can access only configured override servers - BLoose:
FortiManager can access only configured override servers
Strict:
Default mode
Allows fallback to the other FDN server
- ALoose:
28Fortiguard Firmware Images Cache
SELECT ALL VOOOO- AFortigate
- BFAZ
- CFMG
- DFAP
- EFortiExtender
- FFortiSwitch
- GFortiClient
29Firmware upgrade can be done using:
- ASystem Information
On firmware tab on device manager pane - BSystem settings
On firmware tab on system information
- ASystem Information
30Devices are not required to be registered with FortiManager’s Device Manager to use the built—in FDS
- AVerdadeiro
- BFalso
31Unmanaged FortiGate can be configured to use FortiManager for FDS updates
- AVerdadeiro
- BFalso
32diagnose fmupdate view-serverlist [fdsl fctl fgdl fgcl fmtr]
- ATroubleshooting FortiGuard Connectivity
- BTroubleshooting FDS Connectivity
33On FortiManager, what is the fgdlinkd process responsible for? ‘
- AA. Serving FortiGate and FortiCIient URL~Iookup requests
- BB. Downloading web-filter and email-filter databases from public FortiGuard servers
34Which of the following statements about FortiManager used as a local FDS is true?
- AA. it uses lots of bandwidth because FortiManager needs to get updates from internet.
- BB. It provides updates for antivirus and lPS signatures only.
Informações
- Descrição
- NSE 5 6.0 - FortiManager Quiz sobre High Availability (HA), criado por Marcos Avila em 13-03-2020.
- Autor
- Marcos Avila
- Idioma
- Español
- Visualizações
- 0
- Etiquetas
- Avaliação
- Ainda sem avaliações Avalie este quiz