Refer to the exhibit. You need to configure a Fibre Channel device alias named TEST for a device that is attached to port fc 1/9 of a Cisco Nexus Series switch in a Cisco UCS system. Which command set should you use?
A. SITE-A-MDS-Fabric-A# configure terminal
SITE-A-MDS-Fabric-A (config)# device-alias database
SITE-A-MDS-Fabric-A (config-device-alias-db)# device-alias name TEST pwwn
50:00:14:42:d0:0 c:f5:20
SITE-A-MDS-Fabric-A (config-device-alias-db)# exit
B. SITE-A-MDS-Fabric-A# configure terminal
SITE-A-MDS-Fabric-A (config)# device-alias database
SITE-A-MDS-Fabric-A (config-device-alias-db)# device-alias name TEST pwwn
50:00:14:40:47:b0:0 c:f5
SITE-A-MDS-Fabric-A (config-device-alias-db)# device-alias commit
C. SITE-A-MDS-Fabric-A# configure terminal
SITE-A-MDS-Fabric-A (config)# device-alias database
SITE-A-MDS-Fabric-A (config-device-alias-db)# device-alias name TEST pwwn
50:00:14:42:d0:0 c:f5:20
SITE-A-MDS-Fabric-A (config-device-alias-db)# device-alias commit
D. SITE-A-MDS-Fabric-A# device-alias database
SITE-A-MDS-Fabric-A (config-device-alias-db)# device-alias name TEST pwwn
50:00:14:40:47:b0:0 c:f5
SITE-A-MDS-Fabric-A (config-device-alias-db)# device-alias commit
Configuring Device-Alias
switch# conf t
switch(config)
switch(config)# device-alias database
switch(config-device-alias-db)# device-alias name HOST pwwn 21:01:00:e0:8b:39:a9:07
switch(config-device-alias-db)# device-alias name TARGET1 pwwn21:00:00:20:37:af:a5:93
switch(config-device-alias-db)# device-alias name TARGET2 pwwn 21:00:00:20:37:af:a5:3d
switch(config-device-alias-db)#exit
switch(config)#device-alias commit
https://www.cisco.com/c/en/us/support/docs/storage-networking/storage-networking/200230-SAN-How-To-Zoning-Methods.html
C is correct.
https://www.ciscolive.com/c/dam/r/ciscolive/us/docs/2018/pdf/BRKSAN-2883.pdf (Page 41)
A is correct, the “device-alias commit” does not exist
C is correct
Reference:
https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5000/sw/configuration/guide/cli/CLIConfigurationGuide/ddas.html#67656
Committing Changes
If you commit the changes made to the pending database, the following events occur:
1.blank.gif The pending database content overwrites the effective database content.
2.blank.gif The pending database is distributed to the switches in the fabric and the effective database on those switches is overwritten with the new changes.
3.blank.gif The pending database is emptied of its contents.
4.blank.gif The fabric lock is released for this feature.
To commit the changes, perform this task:
Command
Purpose
Step 1
switch# configuration terminal
switch(config)#
Enters configuration mode.
Step 2
switch(config)# device-alias commit
Commits the changes made to the currently active session.