5V0-35.21 Exam Dumps : VMware vRealize Operations Specialist

 vRealize Operations provides two types of pricing cards, cost-based and rate-based, to calculate the price associated with your virtual infrastructure. You can assign pricing cards to vCenters or Clusters, depending on the pricing strategy determined by vRealize Operations administrator. The pricing cards help you to set the price for each resource present in your virtual environment. You can customize the pricing card as per your requirement.

• Cost-based pricing card: A cost-based pricing card calculates the price based on the cost of the resources defined in vRealize Operations. You can specify a multiplication factor for each resource type, such as CPU, memory, storage, etc., to adjust the price according to your business needs. The price equation using cost is:  x = Price
• Rate-based pricing card: A rate-based pricing card calculates the price based on the rate of the resources defined by you. You can specify a rate for each resource type, such as CPU, memory, storage, etc., in terms of units, such as MHz, GB, etc. You can also specify the charging period and the power state for each resource type.The price equation using rate is:  x = Price

References: Pricing Overview; Add New Pricing Card

 According to the vRealize Operations Cloud Getting Started guide1 and the VMware Cloud Services documentation2, the invitation that an organization’s owner sends to a new user to consume VMware Cloud Services is valid for up to seven days before it is revoked. If the user does not accept the invitation within this period, the invitation expires and the user cannot join the organization. The organization’s owner can resend the invitation or revoke it if needed. The other options are not correct because they do not match the actual validity period of the invitation. References: 1: vRealize Operations Cloud Getting Started guide, page 92: VMware Cloud Services documentation, Add Users to Your Organization section.

According to the vRealize Operations User Guide1, Business Intent is a feature that allows the administrator to define the performance, efficiency, and consolidation goals for the clusters and hosts in the SDDC, and to specify the maximum amount of cluster resources to be reserved for burst capacity. Business Intent is applied to objects in vRealize Operations using vCenter Server tags, which are key:value labels that allow operators to add meta-data to vCenter Server objects. By tagging VMs, hosts, and/or clusters with specific tags, the administrator can create business-related placement constraints, such as VMs can only be placed on hosts/clusters with matching tags. For example, the tag OS: Linux can indicate a cluster or VM that is assigned to the category OS with a tag name of Linux. vRealize Operations then uses these tags to optimize the placement and balance of the workloads, and to perform automated remediation actions in the event of an issue. The other options are not correct because:

• Groups are not used to apply Business Intent to objects in vRealize Operations. Groups are collections of objects that share common characteristics, such as type, name, location, or relationship. Groups are used to organize objects for monitoring, analysis, alerting, or policy assignment, but not for workload placement or balance1.
• Policies are not used to apply Business Intent to objects in vRealize Operations. Policies are sets of configuration settings that define how vRealize Operations monitors and manages the objects in the SDDC. Policies are used to enable or disable alerts, metrics, properties, symptoms, recommendations, or actions for different types of objects, but not for workload placement or balance1.
• Roles are not used to apply Business Intent to objects in vRealize Operations. Roles are collections of permissions that define what actions a user can perform on the objects in the SDDC. Roles are used to control the access and visibility of the objects for different users, but not for workload placement or balance1. References: 1: vRealize Operations User Guide, pages 57-59, 62-63, 66-67, 70-71.