A seguir é apresentada uma lista de conceitos relativos à segurança da informação.

I elevação de privilégios

II estouro de buffer

III envenenamento de cache

IV ataque de dicionário

V negação de serviço

VI cross-side scripting

VII cryptoanálise

VIII colisão de pacotes

IX fraude de clique

X revocação de certificados

XI backdoor

XII botnet

XIII interface de loopback

XIV mascaramento

XV mecanismos fora de banda out-of-band

XVI roubo de sessão

XVII engenharia social

XVIII spoofing

XIX SYN flood

XX análise de vulnerabilidade

XXI baixa entropia

XXII detecção e análise de inferências

A seguir é apresentada uma lista de conceitos relativos à segurança da informação.

I elevação de privilégios

II estouro de buffer

III envenenamento de cache

IV ataque de dicionário

V negação de serviço

VI cross-side scripting

VII cryptoanálise

VIII colisão de pacotes

IX fraude de clique

X revocação de certificados

XI backdoor

XII botnet

XIII interface de loopback

XIV mascaramento

XV mecanismos fora de banda out-of-band

XVI roubo de sessão

XVII engenharia social

XVIII spoofing

XIX SYN flood

XX análise de vulnerabilidade

XXI baixa entropia

XXII detecção e análise de inferências

Estão associados à segurança de hardware, software, sistemas operacionais, aplicações e bancos de dados, respectivamente, os conceitos identificados por

The term redundancy refers to a parallel or alternate path in a system architecture to meet system requirements in two or more independent ways. The purpose of a redundant system is to improve reliability. There are two general approaches to redundancy implementation: system redundancy and component redundancy. System redundancy involves the connection of two identical systems in parallel between system inputs and system outputs. In the event of a failure of the active system, the inactive or backup system can be switched on to replace the failed system. A variation of system redundancy is the use of a hot backup system. In this approach, both prime and backup systems are in the “on” state. There are manual and automatic approaches to recognizing system failures and effecting a switchover from the failed system to the backup system.

Software and firmware play a dominant role in the implementation of redundant systems. Many of the built-in tests are in software or embedded in firmware. Setting and resetting the watchdog timer and updating the checkpoint restart memory are software functions. Switchover and restart are also software functions.

The concept of component redundancy suggests making redundant only those subsystems or components that are relatively unreliable. In many cases, by making a few critical components in a system redundant, one can provide enough improvement in overall reliability to meet the system reliability requirements. For example, in a redundant automobile braking system the brake pedal and linkage are not redundant (simplex) while the master brake cylinder is redundant. The same concerns in system redundancy implementation regarding failure detection and switch over are also found in component redundancy implementation. In the braking system just described, a failure of one master cylinder results in degraded braking performance. This system is better described as fault tolerant.

A. Behforooz, F. J. Hudson. Software engineering
fundamentals. F. J. Oxford University Press.

In the text, “better” is the opposite of

The term redundancy refers to a parallel or alternate path in a system architecture to meet system requirements in two or more independent ways. The purpose of a redundant system is to improve reliability. There are two general approaches to redundancy implementation: system redundancy and component redundancy. System redundancy involves the connection of two identical systems in parallel between system inputs and system outputs. In the event of a failure of the active system, the inactive or backup system can be switched on to replace the failed system. A variation of system redundancy is the use of a hot backup system. In this approach, both prime and backup systems are in the “on” state. There are manual and automatic approaches to recognizing system failures and effecting a switchover from the failed system to the backup system.

Software and firmware play a dominant role in the implementation of redundant systems. Many of the built-in tests are in software or embedded in firmware. Setting and resetting the watchdog timer and updating the checkpoint restart memory are software functions. Switchover and restart are also software functions.

The concept of component redundancy suggests making redundant only those subsystems or components that are relatively unreliable. In many cases, by making a few critical components in a system redundant, one can provide enough improvement in overall reliability to meet the system reliability requirements. For example, in a redundant automobile braking system the brake pedal and linkage are not redundant (simplex) while the master brake cylinder is redundant. The same concerns in system redundancy implementation regarding failure detection and switch over are also found in component redundancy implementation. In the braking system just described, a failure of one master cylinder results in degraded braking performance. This system is better described as fault tolerant.

A. Behforooz, F. J. Hudson. Software engineering
fundamentals. F. J. Oxford University Press.

In the text, “one” is

The term redundancy refers to a parallel or alternate path in a system architecture to meet system requirements in two or more independent ways. The purpose of a redundant system is to improve reliability. There are two general approaches to redundancy implementation: system redundancy and component redundancy. System redundancy involves the connection of two identical systems in parallel between system inputs and system outputs. In the event of a failure of the active system, the inactive or backup system can be switched on to replace the failed system. A variation of system redundancy is the use of a hot backup system. In this approach, both prime and backup systems are in the “on” state. There are manual and automatic approaches to recognizing system failures and effecting a switchover from the failed system to the backup system.

Software and firmware play a dominant role in the implementation of redundant systems. Many of the built-in tests are in software or embedded in firmware. Setting and resetting the watchdog timer and updating the checkpoint restart memory are software functions. Switchover and restart are also software functions.

The concept of component redundancy suggests making redundant only those subsystems or components that are relatively unreliable. In many cases, by making a few critical components in a system redundant, one can provide enough improvement in overall reliability to meet the system reliability requirements. For example, in a redundant automobile braking system the brake pedal and linkage are not redundant (simplex) while the master brake cylinder is redundant. The same concerns in system redundancy implementation regarding failure detection and switch over are also found in component redundancy implementation. In the braking system just described, a failure of one master cylinder results in degraded braking performance. This system is better described as fault tolerant.

A. Behforooz, F. J. Hudson. Software engineering
fundamentals. F. J. Oxford University Press.

Based on the text, choose the incorrect option.

The term redundancy refers to a parallel or alternate path in a system architecture to meet system requirements in two or more independent ways. The purpose of a redundant system is to improve reliability. There are two general approaches to redundancy implementation: system redundancy and component redundancy. System redundancy involves the connection of two identical systems in parallel between system inputs and system outputs. In the event of a failure of the active system, the inactive or backup system can be switched on to replace the failed system. A variation of system redundancy is the use of a hot backup system. In this approach, both prime and backup systems are in the “on” state. There are manual and automatic approaches to recognizing system failures and effecting a switchover from the failed system to the backup system.

Software and firmware play a dominant role in the implementation of redundant systems. Many of the built-in tests are in software or embedded in firmware. Setting and resetting the watchdog timer and updating the checkpoint restart memory are software functions. Switchover and restart are also software functions.

The concept of component redundancy suggests making redundant only those subsystems or components that are relatively unreliable. In many cases, by making a few critical components in a system redundant, one can provide enough improvement in overall reliability to meet the system reliability requirements. For example, in a redundant automobile braking system the brake pedal and linkage are not redundant (simplex) while the master brake cylinder is redundant. The same concerns in system redundancy implementation regarding failure detection and switch over are also found in component redundancy implementation. In the braking system just described, a failure of one master cylinder results in degraded braking performance. This system is better described as fault tolerant.

A. Behforooz, F. J. Hudson. Software engineering
fundamentals. F. J. Oxford University Press.

As found in the text, it is correct to state that

The term redundancy refers to a parallel or alternate path in a system architecture to meet system requirements in two or more independent ways. The purpose of a redundant system is to improve reliability. There are two general approaches to redundancy implementation: system redundancy and component redundancy. System redundancy involves the connection of two identical systems in parallel between system inputs and system outputs. In the event of a failure of the active system, the inactive or backup system can be switched on to replace the failed system. A variation of system redundancy is the use of a hot backup system. In this approach, both prime and backup systems are in the “on” state. There are manual and automatic approaches to recognizing system failures and effecting a switchover from the failed system to the backup system.

Software and firmware play a dominant role in the implementation of redundant systems. Many of the built-in tests are in software or embedded in firmware. Setting and resetting the watchdog timer and updating the checkpoint restart memory are software functions. Switchover and restart are also software functions.

The concept of component redundancy suggests making redundant only those subsystems or components that are relatively unreliable. In many cases, by making a few critical components in a system redundant, one can provide enough improvement in overall reliability to meet the system reliability requirements. For example, in a redundant automobile braking system the brake pedal and linkage are not redundant (simplex) while the master brake cylinder is redundant. The same concerns in system redundancy implementation regarding failure detection and switch over are also found in component redundancy implementation. In the braking system just described, a failure of one master cylinder results in degraded braking performance. This system is better described as fault tolerant.

A. Behforooz, F. J. Hudson. Software engineering
fundamentals. F. J. Oxford University Press.

According to the text, choose the option regarding hot backup systems.

The term redundancy refers to a parallel or alternate path in a system architecture to meet system requirements in two or more independent ways. The purpose of a redundant system is to improve reliability. There are two general approaches to redundancy implementation: system redundancy and component redundancy. System redundancy involves the connection of two identical systems in parallel between system inputs and system outputs. In the event of a failure of the active system, the inactive or backup system can be switched on to replace the failed system. A variation of system redundancy is the use of a hot backup system. In this approach, both prime and backup systems are in the “on” state. There are manual and automatic approaches to recognizing system failures and effecting a switchover from the failed system to the backup system.

Software and firmware play a dominant role in the implementation of redundant systems. Many of the built-in tests are in software or embedded in firmware. Setting and resetting the watchdog timer and updating the checkpoint restart memory are software functions. Switchover and restart are also software functions.

The concept of component redundancy suggests making redundant only those subsystems or components that are relatively unreliable. In many cases, by making a few critical components in a system redundant, one can provide enough improvement in overall reliability to meet the system reliability requirements. For example, in a redundant automobile braking system the brake pedal and linkage are not redundant (simplex) while the master brake cylinder is redundant. The same concerns in system redundancy implementation regarding failure detection and switch over are also found in component redundancy implementation. In the braking system just described, a failure of one master cylinder results in degraded braking performance. This system is better described as fault tolerant.

A. Behforooz, F. J. Hudson. Software engineering
fundamentals. F. J. Oxford University Press.

Taking into consideration what is found in the text, choose the correct option.