AP Cybersecurity: 5.5B - CFUs

Between the user and the application, filtering all traffic before it reaches the server

After the runtime checks, monitoring memory usage

Inside the database, checking stored data after it is saved

Only on the user’s device before requests are sent

The runtime check terminates the program due to large input

The application stores the comment with no issues

The WAF blocks the request because it detects a script tag

The database automatically removes the script without detection

The runtime check terminates the program due to buffer overflow

The application processes all requests normally

The WAF detects unusual traffic patterns and blocks the requests

The buffer increases in size to handle the requests

Encryption key mismatches

Hardware failures in memory

Buffer overflow attacks caused by large inputs

Cross-site scripting and injection attacks

It exceeds the memory size of the buffer

It matches known patterns used in injection attacks

It causes the application to crash immediately

It contains too many characters for the database

The database will reject it before execution

The WAF may allow it through because it does not detect a known pattern

The runtime check will automatically block it before processing

The WAF will always block it regardless of content

To store user data securely in memory buffers

To encrypt all user input before processing

To monitor and filter incoming and outgoing web traffic for malicious activity

To increase the size of buffers for large inputs

The runtime check detects a buffer overflow and terminates the program

The system automatically increases buffer size to fit the input

The WAF blocks the request after it reaches the application

The application ignores the extra input without issue

A database table that stores user credentials

A firewall that filters incoming traffic

A program that encrypts user data

A section of memory used to store user input

They prevent all types of cyberattacks

They are designed to hold a specific expected amount of data

They are only used for temporary storage of logs

They automatically expand to fit any input

To store additional user data if needed

To filter malicious web traffic

To speed up database queries

To detect if the buffer has been overflowed

Automatically fixes the corrupted memory and continues

Terminates the program to prevent further damage

Ignores the change and continues processing

Sends the request back to the WAF for analysis

A user enters a script tag in a comment

A user sends too many requests in a short time

A user enters data that exceeds the buffer’s allocated size

A user logs in with an incorrect password

Runtime checks that detect buffer overflows

Stronger password requirements

A WAF that filters traffic patterns

Encryption of user data

The WAF only works after the runtime check fails

Both perform the same function at different times

The WAF filters suspicious traffic first, and runtime checks handle issues that occur inside the application

The runtime check filters all incoming traffic before the WAF

The WAF is unnecessary if runtime checks exist

The database is responsible for stopping large inputs

The application should remove runtime checks

The WAF does not detect all threats, and runtime checks provide a second layer of defense

It may not detect attacks that do not match known patterns

It replaces the need for runtime checks

It cannot monitor web traffic

It only works for buffer overflow attacks

The application automatically removed malicious content

The input contains no suspicious patterns and fits within buffer limits

The runtime check ignored a buffer overflow

The WAF failed to detect a hidden attack

They protect against different types of threats at different stages

Only one is needed if configured correctly

They are required for database storage

They both detect the exact same types of attacks

A WAF focuses on detecting patterns and traffic behavior, not memory overflow issues

A WAF replaces runtime checks entirely

A WAF directly monitors memory usage

A WAF increases buffer size automatically