A developer's web application connects to MySQL with the root account because “it always works”. What should be done instead?
L'application web d'un développeur se connecte à MySQL avec le compte root parce que « ça marche toujours ». Que faut-il faire à la place ?
Answers
AGive the app its own account with only the permissions it needsDonner à l'application son propre compte, avec uniquement les autorisations nécessaires
BKeep using root, but change its password once a year and write it in the codeContinuer d'utiliser root, mais changer son mot de passe une fois par an et l'écrire dans le code
CShare the root password with all developersPartager le mot de passe root avec tous les développeurs
DDisable the database passwordDésactiver le mot de passe de la base
The answer and explanation are in the full bank.
This question is one of 2,831 in the paid banks. Each comes with the correct answer and the reasoning behind it, not just a mark.
Unlock for 5,000 RWFMIFOTRA exam practicealigned to Practice set: Database Management·1 mark·Easy
More Database questions
- What is the main role of a database management system (DBMS) such as PostgreSQL, MySQL or SQL Server?
- In a relational table called Applicants, what does a single row represent?
- Which two properties must every primary key value have?
- The Employees table has a DistrictID column that must always refer to an existing row in the Districts table. What enforces this rule?
- An ExamResults table records one score per candidate per paper. Neither CandidateID nor PaperID is unique on its own. What is a suitable primary key?
- A designer gives each applicant an auto-generated ApplicantID as the primary key, and stores the national ID number as a separate unique column. Why use this surrogate key?
- One district has many sectors, and each sector belongs to exactly one district. What type of relationship is this?
- Each trainee can attend many courses, and each course has many trainees. How is this relationship stored in a relational database?