Dell PowerEdge Operate v2 Free Sample Questions

In iDRAC 10, generic LDAP connection settings are managed under the 'idrac.ldap' attribute group. To switch from the default STARTTLS mode on port 389 to dedicated LDAPS on port 636, the administrator must configure 'idrac.ldap.connection' to 'LDAPS' and 'idrac.ldap.port' to '636'. The group 'idrac.security.ldapmode' does not exist in the iDRAC 10 RACADM schema.

Both the iDRAC10 User's Guide license table and the Security Configuration Guide list directory services (Active Directory and LDAP) as unavailable on the factory-default Core license and included from Enterprise upward. BIOS Live Scanning, which checks the integrity and authenticity of the BIOS image in the primary ROM while the host is powered on, requires an iDRAC Datacenter license in both documents. Because the Datacenter license includes every Enterprise feature, it is the lowest single tier that meets both mandates. Enterprise alone (option B) lacks BIOS Live Scanning, Core (option C) lacks both features, and an OpenManage Enterprise plugin (option D) does not replace the iDRAC Datacenter license that BIOS Live Scanning requires.

iDRAC 10 introduces major architectural modernizations, deprecating and removing legacy management mechanisms including WSMan (in favor of standard RESTful Redfish APIs) and Group Manager (in favor of Dell OpenManage Enterprise for multi-server fleet management). Other removed features in iDRAC 10 include vFlash, Software RAID, TLS 1.1, Simple 2FA (email), and Local Key Management (LKM). Redfish, Remote RACADM, iSM, and IPMI remain supported.

Only one active instance of Local RACADM can execute concurrently on the host operating system due to locking of the internal kernel interface communicating with the BMC.

Local RACADM executes in-band within the host operating system and requires the installation of the Dell iDRACTools software package. Because Local RACADM communicates directly with the BMC via internal system interfaces, it requires administrative/root privileges on the host OS, and only one instance of Local RACADM can execute concurrently on the system. Supplying '-r', '-u', and '-p' parameters is characteristic of Remote RACADM, not Local RACADM.

The documented iDRAC 10 RACADM CLI syntax for virtual disk creation is 'racadm storage createvd: -rl [-wp {wt|wb|wbf}] [-rp {nra|ra|ara}] -pdkey: '. The write policy parameter for Write Back Force is '-wp wbf', the read policy parameter for Adaptive Read Ahead is '-rp ara', and physical drive FQDDs must be comma-separated under '-pdkey'.

In iDRAC 10 RACADM, a physical disk becomes a hot spare with 'racadm storage hotspare: -assign yes -type ghs', where ghs makes it a global hot spare (ghs is also the default when -type is omitted). Option A uses '-type dhs', which requests a dedicated hot spare and also needs '-vdkey: ' to name the virtual disk it protects. Options B and D use syntax that does not exist: the storage command (which can also be run as raid) has no sethotspare or assignhotspare operation.