1. | MetaFrame supports three main categories of printer types. They are _________________.
| ||||||||
A1: | Answer A is correct. The three categories of supported printers are client, network, and local printers. Answer B is incorrect because both client local and client network printers are actually classified simply as client printers, and server local printers are equivalent to local printers. The actual network printers category is missing from this list. Answer C is incorrect because server printers could represent either network or local printers. Answer D is incorrect because it refers to printer driver properties, not supported printer types. | ||||||||
2. | When a printer is shared off a MetaFrame server, it is considered to be a ___________________ printer to the farm. (Choose the answer that best completes the sentence .)
| ||||||||
A2: | Answer D is correct. When a printer is connected to a server running MPS, that printer is considered to be a local printer to the farm. Answer A is incorrect. A network printer is a printer shared off a server that is not also running MetaFrame. Answer B is incorrect because server printer is not one of the printer categories for MetaFrame. Answer C is incorrect because a client printer is any printer that is configured on a client device, whether it is a printer directly attached to the client or a printer that is mapped to a share on the network. | ||||||||
3. | Before a printer driver can be replicated to other servers in the farm, you must first ______________. (Choose the answer that best completes the sentence.)
| ||||||||
A3: | Answer B is correct. Before a driver can be replicated, it must exist on at least one server in the farm. This driver can be installed on any server and replicated to any other server running the same Windows platform. Answer A is incorrect because there is no single setting that must be toggled to enable or disable printer replication in the farm. Answer C is incorrect because client printer mapping entries are created to allow a client running one type of printer driver to seamlessly be configured to use an alternative driver when logged in to the server. This setting dictates what association to make between the client and server printer drivers; it has no bearing on the function of driver replication. Answer D is incorrect because no one server must be designated as the replication source. | ||||||||
4. | When a printer is imported from a Windows print server that is not running MetaFrame, what printer management actions are not available? (Choose all that apply.)
| ||||||||
A4: | Answer A is correct. When a printer is imported from a standard Windows print server, the Replicate Drivers action is not available. A printer driver must exist on at least one MetaFrame server before it can be replicated. Answers B, C, and D are incorrect. All these printer management actions can still be performed, even if the printer was imported from a Windows print server that was not running MetaFrame. | ||||||||
5. | The printer bandwidth limitations apply to what types of printers? (Choose all that apply.)
| ||||||||
A5: | Only answer C is correct. The printer bandwidth limitations apply only to client-mapped printers. Local and network printers (answers A and B) are not throttled using this bandwidth setting. Answer D is also incorrect. Regardless of whether a network printer is mapped manually or through some automated scripting method, bandwidth restrictions are not imposed on that printer. As long as the printer is mapped back through the MPS client, printer bandwidth is controlled through the Bandwidth tab in Printer Management. | ||||||||
6. | Which of the following tasks cannot be performed from the Printer Drivers tab for a MetaFrame server? (Choose all that apply.)
| ||||||||
A6: | Answers B, C, and D are all tasks that cannot be performed from the Printer Drivers tab for a specific MetaFrame server. This must be performed from the Drivers node under Printer Management. One way to remember this is that each of these tasks involves settings that could affect all servers in the farm, not just one individual server. Answer A is the only task that can be performed on an individual server's printer drivers and so is not the correct answer to this question. | ||||||||
7. | A user named Marie connects to your MetaFrame server, but her local printer is not available when she logs on. Assuming that the printer is functioning properly on Marie's local device, which of the following are likely causes for the problem? (Choose all that apply.)
| ||||||||
A7: | Answers B, C, and D are all valid reasons why Marie's printer may not be mapping properly. If no matching driver is installed on the server, her printer would not map if the universal printer driver was also disabled. If her local printer driver name differs from the corresponding driver on the server, the printer would not map without a corresponding driver mapping definition. It is also possible that client printer mapping has been disabled on the MetaFrame server, preventing Marie's client-based printer from appearing. The only answer that is not valid is A. There is no such thing as a printer compatibility issue with MetaFrame. It is possible that a printer may not function properly on a Terminal Server, but this is a Windows issue, not a MetaFrame issue. | ||||||||
8. | Where can the printer driver mapping information be found on each MetaFrame server in the farm?
| ||||||||
A8: | Answer B is correct. Each server has a file called WTSPRNT.INF that contains the printer driver mapping information defined in the Management Console. Answer C is incorrect. While printer driver mapping information is stored in the central data store for the farm, it is also stored in the WTSPRNT.INF file. Answer A is incorrect. Printer driver mapping information has never been stored in the Registry. Similarly, answer D is also incorrect. Although the local host cache maintains a subset of the main data store information, it does not contain printer driver mapping information. | ||||||||
9. | MetaFrame provides more than one type of universal printer driver. Select only the valid universal drivers from the following list.
| ||||||||
A9: | Answers B and C are the only two valid UPDs in the list. The third valid driver, called PCL4, is the only UPD not in this list. Neither answer A nor D represents a valid universal printer driver supplied with MPS 3.0. PCL4c is incorrect because the UPD driver is simply PCL4, without the c suffix. | ||||||||
10. | Where would you go to configure the behavior of universal printer driver use in your MetaFrame server farm?
| ||||||||
A10: | Answer A is correct. The options for using UPDs in client printer creation are managed within the properties of the Printer Management node. From here, you can dictate whether a native or universal driver will be used. Although both answers B and C describe valid properties for the Drivers and Printers node, neither location manages information on the universal printer drivers. The final answer, D, is incorrect because there are no such UPD properties within the Drivers node. | ||||||||
11. | A universal printer driver can be used for which of the following printers? (Choose all that apply.)
| ||||||||
A11: | Only answer A is correct. Universal printer drivers can be employed only for auto-created client printers. All other printer types depend on the availability of a suitable driver on the MetaFrame server, so answers B, C, and D are incorrect. | ||||||||
12. | An order of precedence is followed when determining whether client auto-created printers are enabled and what settings are used. Choose the answer that correctly lists the order of precedence for these properties from highest to lowest .
| ||||||||
A12: | Answer C is correct. User policies always take precedence over other client printer auto-creation settings. Farm properties are the next highest, but by default they use the connection settings on the individual servers, which in turn look to individual user settings by default. Therefore, answers A, B, and D are incorrect. | ||||||||
13. | Network printer auto-creation has been configured for a printer based on membership in the group called Printers. User Joe is complaining that he cannot see this printer within his MetaFrame session. What are possible reasons for his printer not being available? (Choose all that apply.)
| ||||||||
A13: | Answers A and C are correct. If the auto-creation was configured but Joe has not logged off and back on, he cannot pick up the network printer mapping. He may also not be a part of the group, so he will not receive that mapping during logon. Answer B is not correct in this case. Auto-created network printers do not rely on a client driver at all, so Joe would not be affected by any driver name mismatch that may exist. Answer D is also incorrect. If the print server had not yet been imported, you would not have been able to configure the auto-creation of the network printer. The printer will appear in the Printer Management node only if it has been imported or it is being shared off a MetaFrame server in the farm. |