A2010-577 無料問題集「IBM Assess: IBM Tivoli Endpoint Manager V8.2 Implementation」

（A）Master operator

（B）Non-master operator

（C）Non-master operator with custom content privileges

（D）Non-master operator with unmanaged assets privileges set to Show All

（A）The Internet DMZ relay must have a host record present in DNS.

（B）The Internet DMZ relay does not require a DNS record if used with the task - BES Client Setting: Name Override.

（C）The Internet DMZ relay does not require a DNS record if used with the task - BES Relay Setting: Name Override.

（D）The Internet DMZ relay must have both host and PTR records present in DNS.

（A）The client keeps reporting this information to the new TEM server.

（B）The client saves this information locally for possible future audit.

（C）The client keeps reporting this information to the old TEM server as long as it is online

（D）This information is no longer reported on by the client.

（A）Domain Debugger

（B）Presentation Debugger

（C）TEM Diagnostics

（D）Fixlet Debugger

（A）TEM Masthead and password

（B）TEM Private Key and password

（C）SQL Server Admin credentials

（D）LDAP/AD Domain credentials

（A）Access the relay diagnostic page on the TEM server at http://127.0.0.1:52311/rd and modify the Client Download Speed setting.

（B）Access the TEM console, select File > Preferences, under the bandwidth throttling section, update the Bytes/sec value for the default download throttling for clients.

（C）Access the TEM Administration Tool, select System Options, select bandwidth throttling, and update the Bytes/sec value for the default download throttling for clients.

（D）Access the TEM console, take action on the task BES Client Setting: Download Throttling, in the Action Parameter window set the Bytes/sec value, and click OK.

（A）This request is made to add additional data to the .pvk file for the user.

（B）This is an indication that the upgrade failed for the console.

（C）This request is to verify the user prior to migrating the user to a local account.

（D）This is done to store the .pvk files in the BFEnterprise database.

（A）Log into the client, right-click on the client dashboard icon in the tool tray, and select the option Enable Power Management Dashboard

（B）Access the TEM Administration tool, select System Options, under the Client section select the option Enable Client Dashboard for Power Management

（C）Access the TEM Console, select the Systems Lifecycle domain, select the Power Management folder, select Setup and Configuration, and take action on the task Enable Client Dashboard

（D）Access the TEM Console, under All Content domain select computers folder, right-click on the agent, and select Enable Client Dashboard for Power Management

（A）The non-master's install of the TEM Console is an older version than the server version of TEM

（B）Increase the RAM for the system running the TEM Console

（C）Uninstall and reinstall their console

（D）Have the operator clear the cache and then close and relaunch the console session

（A）BigFix Labs *NIX Client Deployment Wizard

（B）Red Hat Satellite Server

（C）Custom scripts using SSH

（D）TEM Client Deployment Wizard