¡GoConqr estrena diseño! Cuéntanos qué te parece.

Regístrate gratis

Test

High Availability (HA)

Marcos Avila 34 preguntas

Hacer el test

Este test tiene tipos de pregunta que se abren en el reproductor de siempre.

Preguntas del test (34)

  1. 1All FortiManager devices in cluster must be same model and firmware
    1. AVerdadero
    2. BFalso
  2. 2Designed for one primary device and multiple secondary devices - Up to four secondary devices
    1. A(five devices in total)
    2. B(six devices in total)
  3. 3Supports geographical redundancy
    1. AHA sync is TLSv1.0 over TCP port 5199
    2. BHA sync is TLSv2.0 over TCP port 9951
  4. 4Each HA member operates independently - Unique IP for each FortiManager
    1. AVerdadero
    2. BFalso
  5. 5Upgrading the primary FortiManager not upgrades all secondary devices at the same time
    1. AVerdadero
    2. BFalso
  6. 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
    1. Asecondary devices
    2. Bdevice database
    3. Cprimary device
    4. Ddevice configurations
    5. Econfiguration revisions
    6. FConfiguration settings
    7. Gfeature configuration
    8. Hantispam databases
    9. IMessage Console logs
    10. JFortiGate logs
  7. 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]


    1. Asecondary devices
    2. Bprimary devices
    3. Csecondary to primary
    4. Dprimary to secondary
    5. Eprimary device
    6. Fsecondary device
  8. 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
    1. Aprimary device
    2. Bsecondary device
    3. Csecondary device
    4. Dprimary device
  9. 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).
    1. AHeart Beat Interval
    2. BFailover Threshold
  10. 10Configure HA using System Settings (Choose 4)
    1. ASelect role
    2. BIP and serial number for cluster member
    3. CCluster ID and group password should be same for all members
    4. DCad add up to four secondary devices if roles is selected as Master
    5. ECad add up to four primary devices if roles is selected as Master
    6. FSelect HA type

Información

Descripción
NSE 5 6.0 - FortiManager Test sobre High Availability (HA), creado por Marcos Avila el 13/03/2020.
Idioma
Español
Visitas
0
Etiquetas
nse 5 6.0 - fortimanager
Valoración
Aún sin valoraciones
Valora este test
Valora este test

Escríbenos

¿Sobre qué es tu mensaje?

¿Qué te parece el nuevo diseño?

¿Te gusta?