Exam:3V0-22.21N
Title: https://www.passcert.com/3V0-22.21N.html
Thesafer,easierwaytohelpyoupassanyITexams
1.Youaretaskedtoautomatetheinstallationanddeploymentofnewhostaddedintoyourcompany vSphereclusterusingAutoDeployEnsureAutoDeployandImageBuilderissettostartautomatically everytimevCenterServerisrestarted.UsethewebclientandVCSA0latoperformthisstep.
ConfirmthattheautodeploypluginisavailableinthewebinterfaceYoumayberequiredtologoutand logbackinafterenablingtheservices
ThevCenterserverisrequiredtoretrievesoftwarefromanonlinedepotYouaretousethedepot providedbelowandensurethatAutoDeployisalwaysrunningeven,withrestartofvCenterserverName FirstDepot
URLhttps//hostupdatevmwarecom/software/VUB/PRODUCTION/main/vmw-depot-indexxmlNote: ignoreerrorthatyoureceivedoncannotconnecttodepotThisisexpectedduetovCSAdonothave internetconnection
CreateadeployRuleonVCSA0labasedoninformationbelow.Youdonotneedtoapplytoanyhost atthistime
Name:Rule1
SpecifyRuletomatchVendor:Dell
Check'DoNotIncludeImageProfile"
Check'DoNotIncludeHostProfile"
Selecthostlocation:ChooseclusterPROD-A
Answer:
BeforeyoucanusevSphereESXiImageBuilderwiththevSphereWebClient,youmustverifythatthe serviceisenabledandrunning
Procedure
LogintoyourvCenterServersystembyusingthevSphereWebClient
OnthevSphereWebClientHomepage,clickAdministration
UnderSystemConfigurationclickServices
SelectImageBuilderService,clicktheActionsmenu,andselectEditStartupType
OnWindows,thevSphereESXiImageBuilderserviceisdisabledIntheEditStartupTypewindow,select ManualorAutomatictoenableAutoDeploy
OnthevCenterServerAppliance,thevSphereESXiImageBuilderservicebydefaultissettoManual. IfyouwanttheservicetostartautomaticallyuponOSstartup,selectAutomatic Ifyouselectthemanualstartuptype,youmuststarttheservicemanuallyuponOSstartupeverytimeyou wanttousetheservice
(Optional)ClicktheStarttheserviceicon.
(Optional)IfyouwanttousevSphereESXiImageBuilderwiththevSphereWebClient,logoutofthe vSphereWebClientandloginagain.
TheAutoDeployiconisvisibleontheHomepageofthevSphereWebClient
2YoursecurityteamisgettingreadyforanauditandwantstocheckthestatusofallESXIhosts' outstandingsecuritypatchesCreateanewfixedUpdateManagerbaselineforallsecurityESXihost patchesandnameit''Securitypatches''UsethepatchesavailableinthepatchrepositoryUseVCSA01a inthistask
BaselineName:SecurityPatches
BaselineType:HostPatch
Category:Security
Thesafer,easierwaytohelpyoupassanyITexams
Answer:
TheUpdateManagerdisplayssystemmanagedbaselinesthataregeneratedbyvSANThesebaselines appearbydefaultwhenyouusevSANclusterswithESXihostsofversion6.0Update2andlaterinyour vSphereinventoryIfyourvSphereenvironmentdoesnotcontainanyvSANclusters,nosystemmanaged baselinesarecreated
Thesystemmanagedbaselinesautomaticallyupdatetheircontentperiodically,whichrequiresUpdate ManagertohaveconstantaccesstotheInternetThevSANsystembaselinesaretypicallyrefreshed every24hours
YouusesystemmanagedbaselinestoupgradeyourvSANclusterstorecommendedcriticalpatches, drivers,updatesorthelatestsupportedESXihostversionforvSAN
SystemmanagedbaselinescannotbeeditedordeletedYoudonotattachsystemmanagedbaselinesto inventoryobjectsinyourvSphereenvironment.Youcancreateabaselinegroupofmultiplesystem managedbaselines,butyoucannotaddanyothertypeofbaslinetothatgroupSimilarly,youcannotadd asystemmanagedbaselinetoabaselinegroupthatcontainsupgrade,patch,andextensionbaselines.
3.Asamemberofthevirtualinfrastructureteam,youhavebeentaskedwithcreatinganewguest customizationspecificationanddeployingatestvirtualmachinefromanexistinglegacytemplate migratedfromanoldVMwareVI3environment
Tocompletethistask:
DeployanewvirtualmachinewiththenameVM-GuestCusttoesxi02avclasslocalinclusterPROD-A usingthefollowingdetails:
vCenterServer:vcsa01avdasslocal
Datastore:ProdDS01
Template;Core-Template
ThevirtualmachinerequiresanadditionalnetworkcardwiththetypeVMXNET3
CreateanewGuestCustomizationSpecwiththenameCustom-Specusingthefollowingdetails: ©Cust-Spec
OperatingSystem:WindowsServer2008R2
RegistrationSpec;
Name:vclass
Organization:VMware
ThecomputernamemustusethevirtualmachinenameTimezonemustbesettoAmerica/CentralTime NetworkSpecifications:
IPv4andIPv6aresettoDHCPbutrequireastaticDNSentryof172201010
Thecomputermustjointhedomainvclass.localusingthefollowingcredentials: Username:administrator
Password:VMware1!
Answer:
SelectMenu>PoliciesandProfiles,andunderPoliciesandProfiles,clickVMCustomization Specifications
ClicktheCreateanewspecificationicon
TheNewVMGuestCustomizationSpecificationwizardopens
OntheNameandtargetOSpage,enteranameanddescriptionforthecustomizationspecificationand selectWindowsasatargetguestOS
Thesafer,easierwaytohelpyoupassanyITexams
(Optional)SelecttheGenerateanewsecurityidentity(SID)optionandclickNext.
AWindowsSecurityID(SID)isusedinsomeWindowsoperatingsystemstouniquelyidentifysystems andusers.Ifyoudonotselectthisoption,thenewvirtualmachinehasthesameSIDasthevirtual machineortemplatefromwhichitwasclonedordeployed
DuplicateSIDsdonotcauseproblemswhenthecomputersarepartofadomainandonlydomainuser accountsareusedHowever,ifthecomputersarepartofaWorkgrouporlocaluseraccountsareused, duplicateSIDscancompromisefileaccesscontrolsFormoreinformation,seethedocumentationfor yourMicrosoftWindowsoperatingsystem
OntheSetRegistrationInformationpage,enterthevirtualmachineowner’snameandorganizationand clickNext
OntheComputernamepage,enteracomputernamefortheguestoperatingsystemandadomain name.
TheoperatingsystemusesthecomputernametoidentifyitselfonthenetworkOnLinuxsystems,itis calledthehostname.
OntheWindowslicensepage,providelicensinginformationfortheWindowsoperatingsystemandclick Next
Thesafer,easierwaytohelpyoupassanyITexams
OntheSetAdministratorPasswordpage,configuretheadministratorpasswordforthevirtualmachine andclickNext
Enterapasswordfortheadministratoraccountandconfirmthepasswordbytypingitagain.(Optional)
SelecttheAutomaticallylogonasAdministratorcheckboxtologusersintotheguestoperatingsystemas Administrator,andselectthenumberoftimestologinautomaticallyOntheTimezonepage,selectthe timezoneforthevirtualmachineandclickNext
(Optional)OntheRunOncepage,specifycommandstorunthefirsttimeauserlogsintotheguest operatingsystemandclickNext
SeetheMicrosoftSysprepdocumentationforinformationaboutRunOncecommands
OntheNetworkpage,selectthetypeofnetworksettingstoapplytotheguestoperatingsystemandclick Next
SelectUsestandardnetworksettingssothatvCenterServerconfiguresallnetworkinterfacesfroma DHCPserverbyusingthedefaultsettings
SelectManuallyselectcustomsettingsandconfigureeachnetworkinterfaceyourself.
Selectanetworkadapterfromthelistoraddanewone
FortheselectedNIC,clicktheverticalellipsisiconandselectEdit.
TheEditNetworkdialogboxopens
ClicktheIPv4tabtoconfigurethevirtualmachinetouseIPv4network.
YoucanconfigureallthesettingsatthatstageoryoucanselectthePrompttheuserforanIPv4address whenthespecificationisusedoptionInthatcase,vCenterServerpromptsforanIPaddresswhenyou selecttoapplythatcustomizationspecificationduringcloningordeploymentWiththatoption,youcan alsoconfigurethegatewaysduringcloningordeploymentClicktheIPv6tabtoconfigurethevirtual machinetouseIPv6network
YoucanconfigureallthesettingsatthatstageoryoucanselectthePrompttheuserforanaddresswhen thespecificationisusedoptionInthatcase,vCenterServerpromptsforanIPaddresswhenyouselect toapplythatcustomizationspecificationduringcloningordeploymentWiththatoption,youcanalso configurethegatewaysduringcloningordeployment
OptionWorkgroupWindowsDomain
ClicktheDNStabtospecifyDNSserverdetails.
ClickWINStospecifyprimaryandsecondaryWINSserverinformation
ClickOKtoclosetheEditNetworkdialogbox.
OntheSetWorkgrouporDomainpage,selecthowthevirtualmachineparticipatesinthenetworkand clickNext.
OntheReadytocompletepage,reviewthedetailsandclickFinishtosaveyourchanges
4Thecompany'sITstrategyistoadoptinnovativeandemergingtechnologiessuchassoftware-defined storagesolutionTheITteamhasdecidedtoruntheirbusiness-criticalworkloadsonanall-flashVirtual SAN(vSAN)asitprovidesexcellentperformance
TheITteamhaspurchasedserversthatarecompatiblewithvSANHowever,allthesolid-statedrives
Thesafer,easierwaytohelpyoupassanyITexams
(SSD)intheserversareshownincorrectlyashard-diskdrives(HDD)instead.
Inaddition,someofthesolid-statedrives(SSD)willbeusedforotherpurposesinsteadofvSANand shouldnotbepartofthevSANcluster.
ThesearetherequirementsforthevSANcluster:
•Ineachserver,usethe3GBSSDasthecachetierandthe11GBSSDasthecapacitytier
•AsaresultthevSANclusterwilluseatotalofsixSSDs(threeSSDsforcachingandthreeSSDsfor capacity
•EnsureallthedisksthatwillbeusedforvSANareshowncorrectlyasSSDs
•Providestoragesavingsbyusingdeduplicationandcompression
Next,theITteamwantstoimprovetheperformanceandavailabilityofthebusiness-criticalworkloadson thevSAN-datastore
Ensurethefollowingconfigurationswillbeappliedonexistingandnewworkloadslocatedon vSAN-datastore:
Numberofdiskstripesperobject:2
Primaryleveloffailurestotolerate:2
Failuretolerancemethod:RAID-1(Mirroring)
Forceprovisioning;Yes
Thenewconfigurationsshouldbeappliedbydefault.
YoumaycreatenewstoragepolicybutdonoteditthedefaultvSANstoragepolicyasitmaybeusedby othervSANclustersinthefutureNamethepolicy"NewvSANDefault'Nate-Alltasksshouldbe executedinPROD-Ahostcluster
Answer:
VMwarevSphereESXicanuselocallyattachedSSDs(SolidStateDisk)andflashdevicesinmultiple waysSinceSSDsoffermuchhigherthroughputandmuchlowerlatencythantraditionalmagnetichard disksthebenefitsareclearWhileofferinglowerthroughputandhigherlatency,flashdevicessuchas USBorSATADOMcanalsobeappropriateforsomeusecasesThepotentialdrawbacktousingSSDs andflashdevicestorageisthattheendurancecanbesignificantlylessthantraditionalmagneticdisks anditcanvarybasedontheworkloadtypeaswellasfactorssuchasthedrivecapacity,underlyingflash technology,etc.
ThisKBoutlinestheminimumSSDandflashdevicerecommendationsbasedondifferenttechnologies andusecasescenarios.
SSDandFlashDeviceUseCases
Anon-exhaustivesurveyofvarioususagemodelsinvSphereenvironmentarelistedbelow.Hostswap cache
ThisusagemodelhasbeensupportedsincevSphere5.1forSATAandSCSIconnectedSSDs.USBand lowendSATAorSCSIflashdevicesarenotsupported
TheworkloadisheavilyinfluencedbythedegreeofhostmemoryovercommitmentRegulardatastore A(local)SSDisusedinsteadofaharddiskdrive
ThisusagemodelhasbeensupportedsincevSphere70forSATAandSCSIconnectedSSDs ThereiscurrentlynosupportforUSBconnectedSSDsorforlowendflashdevicesregardlessof connectiontype vSphereFlashReadCache(akaVirtualFlash)
ThisusagemodelhasbeensupportedsincevSphere55forSATAandSCSIconnectedSSDs ThereisnosupportforUSBconnectedSSDsorforlowendflashdevices
Thesafer,easierwaytohelpyoupassanyITexams
vSAN
ThisusagemodelhasbeensupportedsincevSphere55forSATAandSCSISSDsFormoreinformation, seethevSANHardwareQuickReferenceGuide.
vSphereESXiBootDisk
AUSBflashdriveorSATADOMorlocalSSDcanbechosenastheinstallimageforESXi,thevSphere hypervisor,whichthenbootsfromtheflashdevice
ThisusagemodelhasbeensupportedsincevSphere35forUSBflashdevicesandvSphere40for SCSI/SATAconnecteddevices
InstallationtoSATAandSCSIconnectedSSD,SATADOMandflashdevicescreatesafullinstallimage whichincludesaloggingpartition(seebelow)whereasinstallationtoaUSBdevicecreatesaboot diskimagewithoutaloggingpartition
vSphereESXiCoredumpdevice
Thedefaultsizeforthecoredumppartitionis25GiBwhichisabout27GBandtheinstallercreatesa coredumppartitiononthebootdevicedeviceforvSphere5.5andabove.Afterinstallationthepartition canberesizedifnecessaryusingpartedUtilFormoreinformation,seethevSpheredocumentation AnySATADOMorSATA/SCSISSDmaybeconfiguredwithacoredumppartition.
ThisusagemodelhasbeensupportedfromvSphere35forbootUSBflashdevicesandsincevSphere 4.0foranySATAorSCSIconnectedSSDthatislocal.
ThisusagemodelalsoappliestoAutodeployhostswhichhavenobootdisk vSphereESXiLoggingdevice
ASATADOMorlocalSATA/SCSISSDischosenasthelocationforthevSphereloggingpartition (/scratchpartition)ThispartitionmaybebutneednotbeonthebootdiskandthisappliestoAutodeploy hostswhichlackabootdisk
ThisusagemodelhasbeensupportedsincevSphere70foranySATAorSCSIconnectedSSDthatis localSATADOMsthatmeettherequirementsetforthinTable1arealsosupported
ThisusagemodelcanbesupportedinafuturereleaseofvSphereforUSBflashdevicesthatmeetthe requirementsetforthinTable1
SSDEnduranceCriteria
TheflashindustryoftenusesTeraBytesWritten(TBW)asabenchmarkforSSDendurance.TBWisthe numberofterabytesthatcanbewrittentothedeviceoveritsusefullifeMostdeviceshavedistinctTBW ratingsforsequentialandrandomIOworkloads,withthelatterbeingmuchlowerduetoWrite AmplificationFactor(WAF)(definedbelow)OthermeasuresofendurancecommonlyusedareDWPD (DriveWritesPerDay)andP/E(Program/Erase)cycles.
Conversionformulasareprovidedhere:
ConvertingDWPD(DriveWritesPerDay)toTBW(TerabytesWritten):
TBW=DWPD*Warranty(inYears)*365*Capacity(inGB)/1,000(GBperTB)
ConvertingFlashP/ECyclesperCelltoTBW(TerabytesWritten):
TBW=Capacity(inGB)*(P/ECyclesperCell)/(1,000(GBperTB)*WAF)
WAFisameasureoftheinducedwritescausedbyinherentpropertiesofflashtechnologyDuetothe differencebetweenthestorageblocksize(512bytes),theflashcellsize(typically4KiBor8KiBbytes) andtheminimumflasherasesizeofmanycellsonewritecanforceanumberofinducedwritesdueto copies,garbagecollection,etcForsequentialworkloadstypicalWAFsfallintherangeofsingledigits whileforrandomworkloadsWAFscanapproachorevenexceed100Table1containsworkload characterizationforthevariousworkloadsexceptingtheDatastoreandvSphereFlashReadCache
workloadswhichdependonthecharacteristicsoftheVirtualMachinesworkloadsbeingrunandthus cannotbecharacterizedhereAWAFfromthetablecanbeusedwiththeaboveP/EtoTBWformula