Answer:
Option 2 i.e., instance methods is the correct answer to the following question.
Explanation:
Because the instance method or function is the function that needed the class object to be called.
<u>For Example:</u>
//header file
#include <iostream>
using namespace std;
//define class
class Test
{
public:
//instance method
void getins()
{
cout<<"I AM Instance method";
}
};
int main()
{
//creating object
Test obj;
//calling of instance method through class object
obj.getins();
}
<u>Output</u>:
I AM Instance method
Answer:
day=int(input(“Enter today’s day numerically: ”))
if(day ==15 or day ==30):
print(“It’s payday!”)
if(day !=15 and day !=30):
print(“Sorry, not a payday.”)
Explanation:Good luck!
Answer:
Options A and C.
Explanation:
In Oracle Cloud Infrastructure the two options which allows you to increase disk performance are;
1. Terminate the compute instance preserving the boot volume. Create a new compute instance using a VM Dense IO shape using the boot volume preserved.
2. Create a backup of the boot volume. Create a new compute instance a VM Dense IO shape and restore the backup.
Answer: Explanation:
Salting alters the hash of a password so that it does not physically match the hash of another password. A salt and password are concatenated and processed with a cryptographic hash function. Salt prevents use of rainbow and hash tables to attacking and cracking passwords.
For example, a user has the password, "password000" and is put through a SHA1 hash. In the password database, all of the users with the password "password000" will have the exact same hash, because of the nature of hashing functions. So, if an attacker breaches the database and brute force the password of the user mentioned above, he could look for all the hashes that match the original user's and would know their passwords are also "password000".
By applying a salt, the password hashes would no longer be identical to one another, even though the actual password is still the same. This requires the attacker to go in and attempt to brute force the second password (which has a different salt), even though it may be the same as the first.
In conclusion, it prevents an attacker from uncovering one password and subsequently uncovering multiple others.
