Exam SY0-601 topic 1 question 313 discussion

Code obfuscation is a technique used to make code more difficult to understand or reverse engineer. It involves transforming the code in a way that retains its functionality but makes it harder for an attacker to analyze and exploit any vulnerabilities present. One aspect of code obfuscation is to avoid code reuse, where common code patterns or functions are deliberately modified or transformed to make them less recognizable.

From Mike Meyers Guide: "The downside to code reuse is that bad actors know that Web apps rely on it. These libraries must run in memory to work for the app. Bad actors know they’re running and try to get access to this code and can cause lots of trouble if they do get access. Over the years, attacks have appeared that exploit the reused code, exposing previously unknown vulnerabilities. The IT industry’s response to these attacks varies from the no-execute (NX) bit, built into every CPU, to specialized tools designed to hide, disable, or scramble the reused code." Might help to shed some light.

D. Code obfuscation

Trick question to trip up programmers. Code reuse, in this case, is not about DRY (don't repeat yourself) nor about a dev team sharing code, but rather regarding reverse engineering of code. The term "Code Reuse" is used incorrectly by the exam author. It should be code exposure or reverse engineering. If you do think like a developer, you should see right away that A,B & C have nothing to do with code reuse (stored procs don't actually prevent code reuse in the software sense - think about it).

Code obfuscation is a technique used to make code more difficult to understand

B. Stored procedures... is the correct answer Stored procedures are database programs that are typically written in SQL and stored in the database itself. They encapsulate and execute specific functions or operations on the data within the database. One of the advantages of using stored procedures is that they can reduce vulnerabilities related to code reuse because they limit direct access to the database and its data. Instead of writing the same SQL code multiple times in different parts of the application, developers can encapsulate it within a stored procedure. This reduces the likelihood of SQL injection attacks and other security vulnerabilities associated with code duplication and reuse. Don't just blindly go with what the majority chooses on these answers. Do your own research. Stored procedures is certainly the right answer not Code obfuscation.

Stored procedures are basically functions. In programming, if any piece of code is going to be used more than once, you're supposed to wrap it in a function, and then call the function, instead of the same code. Code obfuscation is contrary to one of the coding practices - make your code as clean as possible, so that other developers don't waste time trying to learn what does each function do.

https://www.sciencedirect.com/science/article/pii/S0950584918301484

what kind of questions is this?? anyway the answer is D

I checked that option too, but that doesn't mean that developers from the same team can't use the code. In any case, it is the closest alternative to what I think.

D. code obfuscation seems the best way to do it

Hmmm! D seems like it . This will ensure other programmers are unable to reuse your code thereby reducing vulnerabilities in others code. 🤔