3102 無料問題集「Avaya Aura Session Manager and System Manager Implementation and Maintenance」

（A）If the Managed Bandwidth field has a value. Session Manager keeps track of the bandwidth in use based on the calls coming out of and going to that specific location and drops old calls when the bandwidth in use reaches the limit.

（B）If the Managed Bandwidth field is blank for a location no Call Admission Control is done
for that location.

（C）If the Managed Bandwidth field has a value, Session Manager keeps track of the bandwidth in use based on the calls coming out of and going to that specific location and sends an alarm to an administrator when new calls reach the bandwidth the limit.

（D）If the Managed Bandwidth field has a value. Session Manager keeps track of the bandwidth in use based on the calls coming out of and going to that specific location and denies new calls when the bandwidth in use reaches the limit.

（E）If the Managed Bandwidth field is blank for a location, the default Call Admission Control is done for that location. Session Manager keeps track of the bandwidth in use based on the calls coming out of and going to that specific location and denies new calls when the bandwidth in use reaches the limit.

（A）Delete the Session Manager Replica node in System Manager, verify the enrollment password is valid In System Manager and run the initTM command again in Session Manager.

（B）Reset the enrollment password.

（C）Verify the enrollment password is valid in System Manager and run the initTM command again in Session Manager.

（D）Run traceSM to monitor the synchronization events and restart the Security Module.

（A）Whether SMGR will abort and rollback the operation or continue processing records is entirely configurable.

（B）Whether SMGR will abort or continue processing records is entirely configurable; but you cannot rollback successfully imported users.

（C）It will abort the operation and roll back any successfully imported records from the import file.

（D）It will continue processing the rest of the import file and collate the failures into a single XML document that can be retrieved following the import.

（A）traceSM displays a ladder trace of the SIP requests going in and out of the Session Manager.

（B）initDRS displays the Session Manager Node registration and data replication.

（C）statapp displays the current status of the Session Manager services.

（D）swversion displays the Session Manager Release information.

（E）smconfig displays the network information and status the Session Manager.

（A）Call Admission Control is enabled on an Entity Link specifying a value for Managed Bandwidth on the Locations screen in Session Manager.

（B）Call Admission Control is enabled in the SIP Entity by specifying a value for Managed Bandwidth.

（C）Call Admission Control is enabled on a Location by specifying a value for Managed Bandwidth.

（D）Call Admission Control is enabled on the Session Manager instance by specifying a value for Managed Bandwidth.

（A）Timer B determines the maximum time period between a dispatched request and the anticipated "200 OK".

（B）Timer B determines the period of time a Session Manager waits for a response before canceling the request and perhaps routes it elsewhere.

（C）Timer B determines the length of time Session Manager allows a telephone to ring before canceling the call and routing it elsewhere.

（D）Timer B determines the maximum allowable call duration.

（A）service postgresq1 restart

（B）pg_resetxlog

（C）pg_clearwal

（D）pg_dump

（E）service wall restart