Pearson 1CP2 - 3.2 - Robust Software

Software that is able to handle erroneous inputs, without crashing, is often referred to as...

• mistake-proof
• robust

• iron-clad

• resolute

What do we call a flaw in a program that compromises security, that can be exploited by an attacker to gain access to a computer system?

• code vulnerability

• code defect

• malware
• code bug

C and C++ allow access to memory directly, which means hackers can exploit this and gain a foothold in the system. What type of vulnerability is this?

• Language specific vulnerability

• Memory leak vulnerability
• SQL injection vulnerability
• Cross-site scripting vulnerability

How can having a properly thought-through design affect the development of a program?

• It may make it easier for mistakes to be picked up and the correct data types to be applied.

• It can lead to decreased efficiency, longer development time, and higher maintenance costs.

• It's easier to write well-structured, robust code when it is properly planned.

• It has no impact on the development process.

How can not sticking to agreed coding practices and standards affect the development of a program?

• It can improve code readability and maintainability
• It can enhance code performance and security
• It can lead to better collaboration among team members
• It can lead to inconsistencies in the codebase, making it harder for developers to work together.

What shoud programmers do as opposed to providing a quick fix for a problem?

• Ignore the problem and move on
• Spend the time identifying and fixing the root cause of the problem

• Blame others for the issue
• Create more problems to distract from the original one

Why should programmers avoid writing unstructured code instead of separating it into subprograms?

• To increase efficiency, reduce readability, and complicate code management
• To make debugging more challenging

• To encourage confusion, discourage collaboration, and limit code scalability
• Properly structured code is easier to read and debug

Why might the use of 3rd party libraries prevent software from being fully robust?

• Third party libraries always have better performance than in-house solutions
• Third party libraries may contain bugs, security vulnerabilities, or compatibility issues.
• Using 3rd party libraries violates software licensing agreements
• Third party libraries are always up-to-date with the latest security patches

Why might not fully testing software, before its release, be problematic?

• Testing software is unnecessary
• Complete testing leads to faster release times
• Incomplete testing may result in undetected bugs, security vulnerabilities, and performance issues.
• Bugs enhance user experience

What example of good programming practice involves other programmers examining the code in order to spot instances of poor programming, find any vulnerabilities in the code or check its efficiency?

• Code Validation
• Code Audit
• Code Inspection
• Code Review