3V0-22.21 Exam Dumps – Our Features

You have just deployed a new vCenter Server Appliance. Vcsa0la. and are required to back up to configuration after deployment. To complete this task, perform an unencrypted backup of the vCenter Server Appliance using the following details:* Use the FTP protocol to backup the appliance* FTP Server Location: 172.20.10.10/* FTP Username: administrator* FTP Password: VMware1!Note: Make sure you include the / at the end of the Server Location

• Explanation:
  Prerequisites
  You must have an FTP, FTPS, HTTP, HTTPS, or SCP server up and running with sufficient disk space to store the backup.
  Dedicate a separate folder on your server for each file-based backup.
  Procedure
  In a Web browser, go to thevCenter Server ApplianceManagement Interface, https://appliance-IP-address-or-FQDN:5480.
  Log in as root.
  In thevCenter Server ApplianceManagement Interface, clickSummary.
  ClickBackup.
  TheBackup Appliancewizard opens.
  Enter the backup protocol and location details.
  Option
  Description
  Backup protocol
  Select the protocol to use to connect to your backup server. You can select FTP, FTPS, HTTP, HTTPS, or SCP.
  For FTP, FTPS, HTTP, or HTTPS the path is relative to the home directory configured for the service. For SCP, the path is absolute to the remote systems root directory.
  Backup location
  Enter the server address and backup folder in which to store the backup files.
  Port
  Enter the default or custom port of the backup server.
  User name
  Enter a user name of a user withwriteprivileges on the backup server.
  Password
  Enter the password of the user withwriteprivileges on the backup server.
  (Optional)SelectEncrypt Backup Datato encrypt your backup file and enter a password for the encryption.
  If you select to encrypt the backup data, you must use the encryption password for the restore procedure.
  ClickNext.
  On the Select parts to backup page, review the data that is backed up by default.
  (Optional)SelectStats, Events, and Tasksto back up additional historical data from the database.
  (Optional)In theDescriptiontext box, enter a description of the backup and clickNext.
  On the Ready to complete page, review the summary information for the backup and clickFinish.
  TheBackup Progresswindow opens and indicates the progress of the backup operation.
  After the backup process finishes, clickOKto close theBackup Progresswindow.
  Results
  You successfully created a backup file of thevCenter Server Appliance.
  

Your security team is getting ready for an audit and wants to check the status of all ESXI hosts' outstanding security patches. Create a new fixed Update Manager baseline for all security ESXi host patches and name it ''Security patches. ''Use the patches available in the patch repository. Use VCSA01a in this task.Baseline Name: Security PatchesBaseline Type: Host PatchCategory: Security

• Explanation:
  The Update Manager displays system managed baselines that are generated by vSAN. These baselines appear by default when you use vSAN clusters with ESXi hosts of version 6.0 Update 2 and later in your vSphere inventory. If your vSphere environment does not contain any vSAN clusters, no system managed baselines are created.
  The system managed baselines automatically update their content periodically, which requires Update Manager to have constant access to the Internet. The vSAN system baselines are typically refreshed every 24 hours.
  You use system managed baselines to upgrade your vSAN clusters to recommended critical patches, drivers, updates or the latest supported ESXi host version for vSAN.
  System managed baselines cannot be edited or deleted. You do not attach system managed baselines to inventory objects in your vSphere environment. You can create a baseline group of multiple system managed baselines, but you cannot add any other type of basline to that group. Similarly, you cannot add a system managed baseline to a baseline group that contains upgrade, patch, and extension baselines.
  

A vSphere administrator has deployed a new server. The VM will have a workload which is prodApp1 to the following specifications:* The VM should never have any memory contention while powered on. even if the host that it resides* Configure the virtual machine for high latency sensitivity.

• Send us your suggestions.
  

The current vSphere environment will be adding new ESXi hosts that will be used to create a QA compute cluster. This cluster should have HA properties specific to the workloads that will be running in it.In preparation of adding the new hosts, create the new cluster. QA-Cluster in. Datacenter-PROD on vcsa0la.vclass.local with the following HA requirements:* The cluster should not contain any ESXi hosts or VMs* Hosts should be monitored.* VMs should be restarted in the event of a host failure.* VMs should be restarted if guest heartbeats are not detected.* In the case of a host becoming isolated, shutdown and restart VMs.* If there is an All Paths Down event, any affected VMs must be moved to another host.* Reserve 10% of memory and CPU for failover capacity.Part 2You have been given a requirement for a virtual machine to have no downtime when an ESXi host failure occurs. Configure Fault Tolerance on VM1-FT in the PROD-B cluster. Use any compatible secondary host and datastore. Configure the following advanced cluster settings. Use SAN01 as the storage during configuration.das.isolationaddress0 172.20.10.11dass.igoreRedundantNetWarining trueNote: ignore any related host, customer, or bandwidth warnings as long as fault tolerance is configured and VM1-FT is running.

• Send us your suggestions.
  

The company's IT strategy is to adopt innovative and emerging technologies such as software-defined storage solution. The IT team has decided to run their business-critical workloads on an all-flash Virtual SAN (vSAN) as it provides excellent performance.The IT team has purchased servers that are compatible with vSAN. However, all the solid-state drives (SSD) in the servers are shown incorrectly as hard-disk drives (HDD) instead.In addition, some of the solid-state drives (SSD) will be used for other purposes instead of vSAN and should not be part of the vSAN cluster. These are the requirements for the vSAN cluster:*In each server, use the 3GB SSD as the cache tier and the 11GB SSD as the capacity tier* As a result the vSAN cluster will use a total of six SSDs (three SSDs for caching and three SSDs for capacity* Ensure all the disks that will be used for vSAN are shown correctly as SSDs* Provide storage savings by using deduplication and compression.Next, the IT team wants to improve the performance and availability of the business-critical workloads on the vSAN-datastore.Ensure the following configurations will be applied on existing and new workloads located on vSAN-datastore:Number of disk stripes per object: 2Primary level of failures to tolerate: 2Failure tolerance method: RAID-1 (Mirroring)Force provisioning; YesThe new configurations should be applied by default.You may create new storage policy but do not edit the default vSAN storage policy as it may be used by other vSAN clusters in the future. Name the policy 'New vSAN Default'.Nate-. All tasks should be executed in PROD-A host cluster.

• Explanation:
  VMware vSphere ESXi can use locally attached SSDs (Solid State Disk) and flash devices in multiple ways. Since SSDs offer much higher throughput and much lower latency than traditional magnetic hard disks the benefits are clear. While offering lower throughput and higher latency, flash devices such as USB or SATADOM can also be appropriate for some use cases. The potential drawback to using SSDs and flash device storage is that the endurance can be significantly less than traditional magnetic disks and it can vary based on the workload type as well as factors such as the drive capacity, underlying flash technology, etc.
  This KB outlines the minimum SSD and flash device recommendations based on different technologies and use case scenarios.
  SSD and Flash Device Use Cases
  A non-exhaustive survey of various usage models in vSphere environment are listed below.
  Host swap cache
  This usage model has been supported since vSphere 5.1 for SATA and SCSI connected SSDs. USB and low end SATA or SCSI flash devices are not supported.
  The workload is heavily influenced by the degree of host memory over commitment.
  Regular datastore
  A (local) SSD is used instead of a hard disk drive.
  This usage model has been supported since vSphere 7.0 for SATA and SCSI connected SSDs.
  There is currently no support for USB connected SSDs or for low end flash devices regardless of connection type.
  vSphere Flash Read Cache (aka Virtual Flash)
  This usage model has been supported since vSphere 5.5 for SATA and SCSI connected SSDs.
  There is no support for USB connected SSDs or for low end flash devices.
  vSAN
  This usage model has been supported since vSphere 5.5 for SATA and SCSI SSDs. For more information, see thevSAN Hardware Quick Reference Guide.
  vSphere ESXi Boot Disk
  A USB flash drive or SATADOM or local SSD can be chosen as the install image for ESXi, the vSphere hypervisor, which then boots from the flash device.
  This usage model has been supported since vSphere 3.5 for USB flash devices and vSphere 4.0 for SCSI/SATA connected devices.
  Installation to SATA and SCSI connected SSD, SATADOM and flash devices creates a full install image which includes a logging partition (see below) whereas installation to a USB device creates a boot disk image without a logging partition.
  vSphere ESXi Coredump device
  The default size for the coredump partition is 2.5 GiB which is about 2.7 GB and the installer creates a coredump partition on the boot device for vSphere 5.5 and above. After installation the partition can be resized if necessary using partedUtil. For more information, see thevSphere documentation.
  Any SATADOM or SATA/SCSI SSD may be configured with a coredump partition.
  This usage model has been supported from vSphere 3.5 for boot USB flash devices and since vSphere 4.0 for any SATA or SCSI connected SSD that is local.
  This usage model also applies to Autodeploy hosts which have no boot disk.
  vSphere ESXi Logging device
  A SATADOM or local SATA/SCSI SSD is chosen as the location for the vSphere logging partition (/scratchpartition). This partition may be but need not be on the boot disk and this applies to Autodeploy hosts which lack a boot disk.
  This usage model has been supported since vSphere 7.0 for any SATA or SCSI connected SSD that is local. SATADOMs that meet the requirement set forth in Table 1 are also supported.
  This usage model can be supported in a future release of vSphere for USB flash devices that meet the requirement set forth in Table 1.
  SSD Endurance Criteria
  The flash industry often uses Tera Bytes Written (TBW) as a benchmark for SSD endurance. TBW is the number of terabytes that can be written to the device over its useful life. Most devices have distinct TBW ratings for sequential and random IO workloads, with the latter being much lower due to Write Amplification Factor (WAF) (defined below). Other measures of endurance commonly used are DWPD (Drive Writes Per Day) and P/E (Program/Erase) cycles.
  Conversion formulas are provided here:
  Converting DWPD (Drive Writes Per Day) to TBW (Terabytes Written):
  TBW = DWPD * Warranty (in Years) * 365 * Capacity (in GB) / 1,000 (GB per TB)
  Converting Flash P/E Cycles per Cell to TBW (Terabytes Written):
  TBW = Capacity (in GB) * (P/E Cycles per Cell) / (1,000 (GB per TB) * WAF)
  WAF is a measure of the induced writes caused by inherent properties of flash technology. Due to the difference between the storage block size (512 bytes), the flash cell size (typically 4KiB or 8KiB bytes) and the minimum flash erase size of many cells one write can force a number of induced writes due to copies, garbage collection, etc. For sequential workloads typical WAFs fall in the range of single digits while for random workloads WAFs can approach or even exceed 100. Table 1 contains workload characterization for the various workloads excepting the Datastore and vSphere Flash Read Cache workloads which depend on the characteristics of the Virtual Machines workloads being run and thus cannot be characterized here. A WAF from the table can be used with the above P/E to TBW formula.
  

Your team is experiencing intermittent issues with esxi0la and you have been asked to configure the host to export its syslog data to a preconfigured syslog collector.To complete this task, you must:* Configure esxi0la.vciass.local to send syslog events to an external syslog collector on 172.20.10.10.* Ensure that the ESXi host security policies allow the syslog traffic to pass.

• Send us your suggestions.
  

You are tasked to automate the installation and deployment of new host added into your company vSphere cluster using Auto Deploy. Ensure Auto Deploy and Image Builder is set to start automatically every time vCenter Server is restarted. Use the web client and VCSA0la to perform this step.Confirm that the auto deploy plugin is available in the web interface. You may be required to logout and log back in after enabling the services.The vCenter server is required to retrieve software from an online depot. You are to use the depot provided below and ensure that Auto Deploy is always running even, with restart of vCenter server.Name FirstDepotURL https / / hostupdate.vmware.com/software/VUB/PRODUCTION/main/vmw-depot-index.xmlNote: ignore error that you received on cannot connect to depot. This is expected due to vCSA do not have internet connection.Create a deploy Rule on VCSA0la based on information below. You do not need to apply to any host at this time.Name: Rule1Specify Rule to match Vendor: DellCheck 'Do Not Include Image Profile'Check 'Do Not Include Host Profile'Select host location: Choose cluster PROD-A

• Explanation:
  Before you can use vSphere ESXi Image Builder with thevSphere Web Client, you must verify that the service is enabled and running.
  Procedure
  Log in to yourvCenter Serversystem by using thevSphere Web Client.
  On thevSphere Web ClientHome page, clickAdministration.
  UnderSystem ConfigurationclickServices.
  SelectImageBuilder Service, click theActionsmenu, and selectEdit Startup Type.
  On Windows, the vSphere ESXi Image Builder service is disabled. In theEdit Startup Typewindow, selectManualorAutomaticto enable Auto Deploy.
  On thevCenter Server Appliance, the vSphere ESXi Image Builder service by default is set toManual. If you want the service to start automatically upon OS startup, selectAutomatic.
  If you select the manual startup type, you must start the service manually upon OS startup every time you want to use the service.
  (Optional)Click theStart the serviceicon.
  (Optional)If you want to use vSphere ESXi Image Builder with thevSphere Web Client, log out of thevSphere Web Clientand log in again.
  TheAuto Deployicon is visible on the Home page of thevSphere Web Client.
  

As a member of the virtual infrastructure team, you have been tasked with creating a new guest customization specification and deploying a test virtual machine from an existing legacy template migrated from an old VMware VI3 environmentTo complete this task:Deploy a new virtual machine with the name VM-GuestCust to esxi02a.vclass.local in cluster PROD-A using the following details:vCenter Server: vcsa01a.vdass.localDatastore: ProdDS01Template; Core-TemplateThe virtual machine requires an additional network card with the type VMXNET3.Create a new Guest Customization Spec with the name Custom-Spec using the following details: Cust-SpecOperating System: Windows Server 2008 R2Registration Spec;Name: vclassOrganization: VMwareThe computer name must use the virtual machine name . Timezone must be set to America/Central TimeNetwork Specifications:IPv4 and IPv6 are set to DHCP but require a static DNS entry of 172.20.10.10The computer must join the domain vclass.local using the following credentials:Username: administratorPassword: VMware1!

• Explanation:
  Select Menu > Policies and Profiles, and under Policies and Profiles, click VM Customization Specifications.
  Click the Create a new specification icon.
  The New VM Guest Customization Specification wizard opens.
  On the Name and target OS page, enter a name and description for the customization specification and select Windows as a target guest OS.
  (Optional) Select the Generate a new security identity (SID) option and click Next.
  A Windows Security ID (SID) is used in some Windows operating systems to uniquely identify systems and users. If you do not select this option, the new virtual machine has the same SID as the virtual machine or template from which it was cloned or deployed.
  Duplicate SIDs do not cause problems when the computers are part of a domain and only domain user accounts are used. However, if the computers are part of a Workgroup or local user accounts are used, duplicate SIDs can compromise file access controls. For more information, see the documentation for your Microsoft Windows operating system.
  On the Set Registration Information page, enter the virtual machine owner's name and organization and click Next.
  On the Computer name page, enter a computer name for the guest operating system and a domain name.
  The operating system uses the computer name to identify itself on the network. On Linux systems, it is called the host name.
  Option
  Action
  Use the virtual machine name
  Select this option to use the virtual machine name. The computer name that vCenter Server creates is identical to the name of the virtual machine on which the guest operating system is running. If the name exceeds 63 characters, it is truncated.
  Enter a name in the Clone/Deploy wizard
  Select this option to be prompted to enter a name during cloning or deployment.
  Enter a name
  Enter a name.
  The name can contain alphanumeric characters and a hyphen (-). It cannot contain a period (.), blank spaces, or special characters, and cannot contain digits only. Names are not case-sensitive.
  (Optional) To ensure that the name is unique, select the Append a numeric value check box.
  This action appends a hyphen followed by a numeric value to the virtual machine name. The name is truncated if it exceeds 63 characters when combined with the numeric value.
  Generate a name using the custom application configured with vCenter Server
  Optional: Enter a parameter that can be passed to the custom application.
  On the Windows license page, provide licensing information for the Windows operating system and click Next.
  Option
  Action
  For nonserver operating systems
  Type the Windows product key for the new guest operating system.
  For server operating systems
  Type the Windows product key for the new guest operating system.
  Select Include Server License Information.
  Select either Per seat or Per server.
  If you select Per server, enter the maximum number of simultaneous connections for the server to accept.
  On the Set Administrator Password page, configure the administrator password for the virtual machine and click Next.
  Enter a password for the administrator account and confirm the password by typing it again.
  (Optional) Select the Automatically logon as Administrator check box to log users in to the guest operating system as Administrator, and select the number of times to log in automatically.
  On the Time zone page, select the time zone for the virtual machine and click Next.
  (Optional) On the Run Once page, specify commands to run the first time a user logs in to the guest operating system and click Next.
  See the Microsoft Sysprep documentation for information about RunOnce commands.
  On the Network page, select the type of network settings to apply to the guest operating system and click Next.
  Select Use standard network settings so that vCenter Server configures all network interfaces from a DHCP server by using the default settings.
  Select Manually select custom settings and configure each network interface yourself.
  Select a network adapter from the list or add a new one.
  For the selected NIC, click the vertical ellipsis icon and select Edit.
  The Edit Network dialog box opens.
  Click the IPv4 tab to configure the virtual machine to use IPv4 network.
  You can configure all the settings at that stage or you can select the Prompt the user for an IPv4 address when the specification is used option. In that case, vCenter Server prompts for an IP address when you select to apply that customization specification during cloning or deployment. With that option, you can also configure the gateways during cloning or deployment.
  Click the IPv6 tab to configure the virtual machine to use IPv6 network.
  You can configure all the settings at that stage or you can select the Prompt the user for an address when the specification is used option. In that case, vCenter Server prompts for an IP address when you select to apply that customization specification during cloning or deployment. With that option, you can also configure the gateways during cloning or deployment.
  Click the DNS tab to specify DNS server details.
  Click WINS to specify primary and secondary WINS server information.
  Click OK to close the Edit Network dialog box.
  On the Set Workgroup or Domain page, select how the virtual machine participates in the network and click Next.
  Option
  Action
  Workgroup
  Enter a workgroup name. For example, MSHOME.
  Windows Server Domain
  Enter the domain name.
  To add a computer to the specified domain, enter the user name and password for a user account that has permission.
  On the Ready to complete page, review the details and click Finish to save your changes.
  

The Virtual Infrastructure team wants to share a VM Template from vcsa0la to vcsa0lb via content libraries. Ensure that the content in the libraries is synchronized only when needed.* Name of Published Content Library in vcsa0la: CL01* Name of Subscribed Content Library in vcsa0lb: CL02* For both content libraries, use the local datastore: SAN01* VM Template to be shared: Core-TemplateAfter the Core-Template has been synchronized from CL01 to CL02. deploy a virtual machine from VM-Template on vcsa0lb* Name of virtual machine: CL-VM* Host for virtual machine: sxi03b

• Send us your suggestions.
  

You have been asked to create a new datastore for the Production cluster; however, the ESXi host esxi02a is not able to add the datastore. Your storage team has determined that there is nothing incorrect with the storage presentation.Troubleshoot why host esxi02a is not able to create the datastore. Add the datastore to the host once the proper configuration has been applied, and then reboot the host!Use the following information to complete this task;* ESXi host: esxi02a* Datastore Name: new_datastore* Datastore target: iSCSI Target* Datastore LUN: 4* Reboot the host

• Explanation:
  Cannot create a new datastore from vCenter Server or directly from the vSphere Client
  Creating a new datastore fails
  The Add Storage Wizard reports the error:
  
  An error occurred during host configuration.
  Call ''HostDatastoreSystem.QueryVmfsDatastoreCreateOptions'' for object ''ha-datastoresystem'' on ESXi ''xxx.xxx.xxx.xx failed.
  An internal error occurred in the vsphere client.
  Cause
  This issue may occur if:
  The size of the LUN is more than 2TB - 512 bytes. The maximum LUN size in vSphere 4 is 2TB - 512 bytes. For more information on this limitation, seeTroubleshooting a LUN that is extended in size past the 2TB/2047GB limit (1004230).
  The LUN being presented was used as an RDM earlier and does not have a valid partition table.
  The LUN being presented was used as a disk device on an other operating system and does not have a valid partition table.
  The LUN contains a GPT partition that cannot be removed.
  Resolution
  To prevent this issue:
  Ensure that the LUN size is less than 2TB - 512 bytes or 2047GB. If the LUN is larger then 2TB - 512 bytes, delete it from your Storage Array and recreate it with a size less than the 2TB - 512 bytes limit.
  If the disk was used by another operating system in the past (I.E.: it was an RDM, or Linux, FreeBSD, or other filesystem) or contains a GPT partition, you must delete the partition information.For more information