- Home
- Server Administration
- LPIC-1 Linux Administrator 102
76.
Your Internet connection has gone down for several hours. What is true of email sent by
your users to off-site recipients via a properly configured local SMTP server?
- A.The SMTP server will refuse to accept email from local clients during the outage.
- B.Email will be neither delayed nor lost.
- C.All email sent during the outage will be lost.
- D.Email will be delayed by a few hours but not lost.
- E.Recipients will have to retrieve the mail via POP or IMAP.
- Answer & Explanation
- Report
Answer : [D]
Explanation :
Explanation :
| SMTP servers accept local email for delivery even if their Internet connections are down. If the SMTP server can’t contact recipient servers, the SMTP server holds the email and attempts delivery later, so option D is correct. Because SMTP servers don’t check on the availability of remote servers until after email is accepted for delivery, option A is incorrect. Option B can’t possibly be correct unless the server has a backup Internet connection, which wasn’t specified in the question. Option C isn’t correct because the SMTP server will hold the mail and attempt delivery later. How recipients retrieve their mail is not under your control, so option E is incorrect. |
77.
You examine your /etc/aliases file and find it contains the following line:
root: jody
What can you conclude from this?
root: jody
What can you conclude from this?
- A.Email addressed to jody on this system will be sent to the local user root.
- B.Email addressed to root on this system will be sent to the local user jody.
- C.The local user jody has broken into the system and acquired root privileges.
- D.The local user jody has permission to read email directly from root’s mail queue.
- E.The administrator may log in using either username: root or jody. S
- Answer & Explanation
- Report
Answer : [B]
Explanation :
Explanation :
| The /etc/aliases file configures system-wide email forwarding. The specified line does as option B describes. A configuration like this one is common. Option A has things reversed. Option C is not a valid conclusion from this evidence alone, although an intruder may conceivably be interested in redirecting root’s email; so if jody shouldn’t be receiving root’s email, this should be investigated further. Although the effect of option D (jody reading root’s email) is nearly identical to the correct answer’s effect, they are different; jody cannot directly access the file or directory that is root’s email queue. Instead, the described configuration redirects root’s email into jody’s email queue. Thus, option D is incorrect. Because /etc/aliases is an email configuration file, not an account configuration file, it can’t have the effect described in option E. |
78.
You’ve just installed MySQL and run it by typing mysql. How would you create a database
called fish to store data on different varieties of fish?
- A.Type NEW DATABASE fish; at the mysql> prompt.
- B.Type CREATE DATABASE fish; at the mysql> prompt
- C.Type NEW DATABASE FISH; at the mysql> prompt.
- D.Type DATABASE CREATE fish; at the mysql> prompt.
- E.Type DB CREATE fish; at the mysql> prompt.
- Answer & Explanation
- Report
Answer : [B]
Explanation :
Explanation :
| The CREATE DATABASE command creates a new database with the specified name. Because SQL commands are case-insensitive, this command may be typed in uppercase or lowercase, and option B is correct. Options A and C both use the incorrect command NEW rather than CREATE, and option C specifies the database name as FISH rather than fish. (Database names are case-sensitive.) Option D reverses the order of the CREATE and DATABASE keywords. Option E uses the fictitious command DB. |
79.
Which of the following are true statements about SQL tables? (Select two.)
- A.Multiple tables may exist in a single SQL database.
- B.Tables may be combined for cross-table searches using the DROP command.
- C.Tables consist of rows, each of which holds attributes, and columns, each of which defines a specific database item.
- D.Careful table design can reduce the amount of data entry and database storage size.
- E.Tables are stored on disk using a lossy compression algorithm.
- Answer & Explanation
- Report
Answer : [A, D]
Explanation :
Explanation :
| A single database may hold multiple tables, as option A suggests. Option D is also correct; by splitting data across tables (such as into tables describing objects generically and specifically), databases can be more space-efficient. Option B is incorrect because the DROP command doesn’t combine tables; it deletes a table! Option C is incorrect because it reverses the meaning of rows and columns in a SQL table. A lossy compression algorithm, as the name suggests, deliberately corrupts or loses some data—an unacceptable option for a text database, making option E incorrect. (Lossy compression is used for some audio and video file formats, though.) |
80.
What is the effect of the following SQL command, assuming the various names and data exist?
mysql> UPDATE stars SET magnitude=2.25 WHERE starname=’Mintaka’;
mysql> UPDATE stars SET magnitude=2.25 WHERE starname=’Mintaka’;
- A.It returns database entries from the stars table for all stars with magnitude of 2.25 and starname of Mintaka.
- B.It sets the value of the stars field in the magnitude set to Mintaka, using a precision of 2.25.
- C.It sets the value of the magnitude field to 2.25 for any item in the stars table with the starname of Mintaka.
- D.It combines the stars and magnitude=2.25 tables, returning all items for which starname is Mintaka.
- E.It updates the stars database, creating a new entry with a starname of Mintaka and a magnitude of 2.25.
- Answer & Explanation
- Report
Answer : [C]
Explanation :
Explanation :
| The UPDATE command modifies existing database table entries, and in this case it does so as option C describes. Option B also describes an update operation, but in a confused and incorrect way. Options A and D both describe database retrieval operations, but UPDATE doesn’t retrieve data. Option E mistakenly identifies stars as a database name, but it’s a table name; and it mistakenly identifies the operation as adding a new entry (INSERT in SQL) rather than as modifying an existing entry (UPDATE in SQL). |
|
|
||||||||||||||||||||||||||||
