First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.
Continue in the practice tool above to load more questions, 50 at a time.
Question 1Turbonomic Architecture, Deployment, and Installation
A customer wants to deploy Turbonomic on-premises with the highest availability for the platform components and their persistent data. Which deployment pattern should the administrator plan for?
- Two standalone all-in-one VMs managed independently without clustering
- A single VM running containers with a shared NFS mount
- A multi-node Kubernetes cluster with replicated persistent volumes across nodes Correct answer.
- A single all-in-one VM with local disk storage
Explanation
High availability in an on-premises Turbonomic deployment depends on running the platform on a multi-node Kubernetes cluster so that control-plane and application pods can be rescheduled, with persistent volumes replicated or backed by resilient storage. A single VM, whether all-in-one or with NFS, leaves a single point of failure. Two unclustered VMs do not provide automatic failover.
Question 2Turbonomic Architecture, Deployment, and Installation
Which component of the Turbonomic platform is responsible for discovering and collecting data from the target environments?
- Target probes Correct answer.
- The Market UI
- The supply chain engine
- The reporting database
Explanation
Targets are configured per environment and the associated probes perform discovery and metric collection from those targets. The supply chain engine consumes that data to build the model, while the UI and database are presentation and storage layers. Probes are therefore the collection layer.
Question 3Turbonomic Architecture, Deployment, and Installation
An administrator needs to add a vCenter target so Turbonomic can discover VMs and hosts. What must be supplied when creating the target?
- The vCenter address and credentials with read permissions, plus validation of the connection Correct answer.
- The ESXi root password for every host in the cluster
- A copy of the vCenter database backup
- A Kubernetes kubeconfig for the vCenter appliance
Explanation
Adding a target requires the endpoint address and an account whose permissions allow the probe to read inventory and metrics, and the connection must be validated before the target is saved. Database backups, per-host root credentials, and kubeconfigs are not part of target configuration.
Question 4Turbonomic Architecture, Deployment, and Installation
After adding a new target, an administrator notices no entities appear in the supply chain. Which action is the most appropriate first step?
- Reinstall the Turbonomic platform
- Delete and recreate the user account in the UI
- Check the target's validation status and probe logs for connection or permission errors Correct answer.
- Disable all other targets to isolate the new one
Explanation
A failed or partially failing target validation usually indicates credential, network, or permission problems, and the probe logs show the specific error. Reviewing validation status and logs is the fastest diagnostic. Reinstalling, deleting users, or disabling other targets does not address the underlying collection failure.
Question 5Turbonomic Architecture, Deployment, and Installation
What is the primary purpose of the Turbonomic supply chain?
- To store historical audit records for compliance
- To model the relationships among entities such as datacenters, hosts, VMs, and applications for analysis Correct answer.
- To provide single sign-on for platform users
- To schedule operating system patching of hypervisors
Explanation
The supply chain is a dependency model that connects infrastructure and workload entities so that analysis can trace how actions and constraints propagate. It is not an audit store, an authentication service, or a patching tool. Understanding this model is essential for interpreting recommendations.
Question 6Turbonomic Architecture, Deployment, and Installation
An administrator must ensure Turbonomic can issue actions against a vCenter target. Which account configuration is required?
- An account with permissions sufficient for the intended actions, such as power operations and migration Correct answer.
- A domain administrator account with unrestricted rights
- A local ESXi account shared across all hosts
- A read-only account, because Turbonomic never changes the environment
Explanation
Discovery only needs read permissions, but executing actions requires permissions that match those actions, such as virtual machine power operations and migrations. Least-privilege accounts scoped to the required actions are preferred. A read-only account cannot execute actions, and unrestricted administrator rights exceed what is needed.
Question 7Turbonomic Architecture, Deployment, and Installation
Which protocol and port range does an administrator typically need to permit so that the Turbonomic platform components can communicate internally in a Kubernetes-based deployment?
- FTP on port 21 for metric transfer
- Internal cluster networking between pods and services, plus required target endpoints Correct answer.
- Only outbound HTTPS to the internet
- SMB on port 445 between all nodes
Explanation
Platform components communicate over internal cluster networking, and each target requires connectivity to its management endpoint. Firewall planning must cover both internal pod and service traffic and outbound target access. SMB, FTP, and general internet access are not the internal communication mechanism.
Question 8Turbonomic Architecture, Deployment, and Installation
A customer asks how Turbonomic obtains the utilization metrics used for analysis. What is the correct description?
- Metrics are entered manually by administrators each day
- Metrics are estimated from license counts
- Metrics are pulled only from a data warehouse the customer maintains
- Metrics are collected from targets through probes and normalized into a common model Correct answer.
Explanation
Probes collect metrics from each configured target, and Turbonomic normalizes them into a consistent model so entities from different environments can be compared and analyzed together. Manual entry, license-based estimates, and external warehouses are not the collection mechanism.
Question 9Turbonomic Architecture, Deployment, and Installation
During installation planning, an administrator must size the environment. Which factor most directly drives the resource requirements of the Turbonomic platform?
- The number of managed entities and the frequency of metric collection Correct answer.
- The number of browser sessions opened per day
- The color scheme selected in the UI
- The number of saved reports
Explanation
Platform sizing is driven primarily by the scale of the managed environment, meaning the count of entities and the volume and frequency of collected metrics. Browser sessions, UI preferences, and saved reports have negligible effect on platform resource needs.
Question 10Turbonomic Architecture, Deployment, and Installation
Which statement best describes the role of the Turbonomic API in an enterprise deployment?
- It is used only for license activation
- It replaces the need for any targets
- It provides the hypervisor kernel for hosts
- It allows automation and integration with external systems for configuration and actions Correct answer.
Explanation
The API exposes platform capabilities so administrators and integrators can automate configuration, query the model, and trigger or approve actions from external tooling. It does not replace targets, handle license activation, or provide hypervisor functionality.
Question 11Turbonomic Architecture, Deployment, and Installation
An administrator is deploying Turbonomic into an existing Kubernetes cluster and must confirm prerequisites. Which prerequisite is essential?
- A default StorageClass capable of provisioning persistent volumes Correct answer.
- A dedicated physical load balancer appliance
- A Windows domain controller on the same subnet
- An SMTP relay reachable from every node
Explanation
The platform requires persistent storage for its components, so a working default StorageClass or equivalent persistent volume provisioning must exist before installation. A domain controller, SMTP relay, and dedicated hardware load balancer are not essential prerequisites for the deployment itself.
Question 12Turbonomic Architecture, Deployment, and Installation
What distinguishes a cloud deployment of Turbonomic from an on-premises deployment in terms of administration?
- Cloud deployments eliminate the need for credentials
- Cloud deployments do not use targets
- Cloud deployments shift platform infrastructure management to the provider while target configuration remains the administrator's responsibility Correct answer.
- Cloud deployments cannot analyze on-premises workloads
Explanation
In a cloud-hosted deployment the provider manages the underlying platform infrastructure, but administrators still configure targets, credentials, and policies. Targets and credentials remain necessary, and on-premises environments can still be analyzed through reachable targets.
Question 13Turbonomic Architecture, Deployment, and Installation
Which item must an administrator back up to preserve Turbonomic platform configuration such as targets and policies?
- The browser cache on administrator workstations
- The platform database and configuration data Correct answer.
- The target systems' own operating system disks
- The hypervisor ISO images
Explanation
Targets, policies, and other platform settings live in the platform's database and configuration data, so those are what must be backed up and restorable. Hypervisor images, browser caches, and target OS disks do not contain Turbonomic configuration.
Question 14Turbonomic Architecture, Deployment, and Installation
After an upgrade of the Turbonomic platform, an administrator finds that a previously working target now fails validation. What is the most likely explanation to investigate first?
- The UI theme was reset
- The supply chain engine was permanently removed
- The license expired for the target system
- The target's certificate or credentials changed and are no longer accepted Correct answer.
Explanation
Validation failures after an upgrade commonly stem from expired or rotated certificates, changed service accounts, or stricter TLS requirements. Investigating certificate and credential validity is the most direct path. The supply chain engine, UI theme, and target licensing are not plausible causes.
Question 15Turbonomic Architecture, Deployment, and Installation
Which Turbonomic capability lets an administrator control how actions are executed, for example requiring manual approval before changes are made?
- The target discovery schedule
- Action mode settings in policies Correct answer.
- The supply chain filter
- The user password policy
Explanation
Policies include action mode settings that determine whether actions are recommended, require approval, or execute automatically. Discovery schedules, supply chain filters, and password policies control different concerns and do not govern action execution.
Question 16Turbonomic Architecture, Deployment, and Installation
An administrator wants recommendations to reflect a maintenance window during which certain hosts must remain untouched. Which mechanism is appropriate?
- Deleting the hosts from the target
- Applying a policy that constrains actions on those hosts, such as a scope or constraint Correct answer.
- Disabling the entire target permanently
- Removing the hosts from the supply chain by editing the database
Explanation
Policies and scopes let administrators constrain or suppress actions for specific entities without losing discovery or data collection. Deleting hosts, disabling the target, or editing the database would remove visibility and is not the supported approach.
Question 17Turbonomic Architecture, Deployment, and Installation
What is the function of the Turbonomic Market UI?
- It authenticates target systems
- It visualizes the supply chain and presents recommended actions for review Correct answer.
- It stores raw metrics in a relational schema
- It compiles the platform binaries during installation
Explanation
The Market UI is the primary interface for exploring the supply chain, viewing utilization and risk, and reviewing or executing recommended actions. It is not the metric store, an authentication service for targets, or a build tool.
Question 18Turbonomic Architecture, Deployment, and Installation
An administrator needs to integrate Turbonomic with an external ticketing system so that recommended actions create tickets. Which approach is most appropriate?
- Configure the target probe to write tickets directly
- Store recommendations in the reporting database and hope the ticketing system reads it
- Manually copy recommendations into tickets each day
- Use the API or supported webhook-style integration to send action data to the ticketing system Correct answer.
Explanation
Integrations are built on the API or supported notification mechanisms, which can pass action details to external systems such as ticketing platforms. Manual copying, probe-level ticket creation, and hoping an external system reads the database are not reliable integration patterns.
Question 19Turbonomic Architecture, Deployment, and Installation
Which consideration is most important when placing a Turbonomic target for a network segment that is isolated by a firewall?
- Ensuring the required management ports are reachable from the platform to the target endpoint Correct answer.
- Ensuring the target runs the same OS as the platform
- Ensuring the target has internet access to download Turbonomic
- Ensuring the target is in the same subnet as the administrator's laptop
Explanation
An isolated segment still works as long as the platform can reach the target's management endpoint on the required ports. The target does not need to download Turbonomic, match the platform OS, or share a subnet with the administrator's workstation.
Question 20Turbonomic Architecture, Deployment, and Installation
What does validating a target connection accomplish during configuration?
- It deletes existing entities from the supply chain
- It upgrades the target management software
- It confirms the platform can authenticate and communicate with the target before saving Correct answer.
- It permanently locks the target settings
Explanation
Validation tests authentication and connectivity so configuration errors surface before the target is committed. It does not lock settings, remove entities, or upgrade target software. Catching problems early avoids silent collection failures.
Question 21Turbonomic Architecture, Deployment, and Installation
An administrator observes that the platform is consuming more memory than expected shortly after onboarding a large environment. Which explanation is most plausible?
- The UI theme uses additional memory per browser tab
- The license file size increased
- The target credentials are stored in memory only
- The supply chain model grew with the number of discovered entities and requires more memory to analyze Correct answer.
Explanation
The platform holds a model of discovered entities and their relationships, so a large environment increases memory demand for analysis. UI themes, credential storage, and license file size are negligible or unrelated factors. Sizing must account for entity scale.
Question 22Turbonomic Architecture, Deployment, and Installation
Which statement correctly describes how targets relate to the supply chain?
- Each target contributes discovered entities and metrics that are merged into a shared supply chain model Correct answer.
- Targets replace the need for policies
- Each target has its own isolated supply chain that cannot be combined
- Targets are only used for licensing
Explanation
Multiple targets feed entities and metrics into one shared supply chain so that cross-environment relationships can be analyzed together. Targets do not create isolated models, serve licensing, or replace policies. This shared model is central to how Turbonomic reasons about the environment.
Question 23Turbonomic Architecture, Deployment, and Installation
An administrator must restore the Turbonomic platform after a failure. Which sequence is most appropriate?
- Recreate all users manually before restoring the database
- Delete all policies, then restore the platform
- Restore the platform database and configuration to a compatible platform version, then verify targets and data collection Correct answer.
- Reinstall targets before restoring the platform
Explanation
Recovery restores the platform database and configuration to a compatible version, after which targets and collection are verified. Targets are external systems and are not reinstalled as part of platform recovery, and deleting policies or recreating users before the restore would discard or duplicate configuration.
Question 24Turbonomic Architecture, Deployment, and Installation
Which practice best supports secure administration of a Turbonomic deployment?
- Storing target credentials in a shared spreadsheet
- Disabling audit logging to reduce overhead
- Sharing a single administrator account among the team
- Using individual accounts with role-based access and integrating with enterprise identity where supported Correct answer.
Explanation
Individual accounts with role-based access preserve accountability and limit privileges, and identity integration centralizes authentication. Shared accounts, spreadsheets of credentials, and disabled audit logging weaken security and traceability.
Question 25Turbonomic Architecture, Deployment, and Installation
A customer wants Turbonomic to analyze workloads in a public cloud account. What must the administrator configure?
- A separate platform instance per cloud region
- A target for the cloud provider with credentials that allow inventory and metric read access Correct answer.
- A VPN tunnel from every workload to the platform
- A local agent installed on every cloud VM
Explanation
Public cloud analysis uses a cloud target configured with credentials that permit reading inventory and metrics through the provider API. Per-VM agents, mandatory tunnels from every workload, and one platform instance per region are not required.
Question 26Turbonomic Architecture, Deployment, and Installation
An administrator is planning a new Turbonomic deployment and needs to understand the platform's core architectural components. Which statement accurately describes the relationship between the Turbonomic Market and the supply chain?
- The Market is the user interface that displays the supply chain and allows administrators to review and execute actions. Correct answer.
- The Market is the persistence layer that stores historical utilization data for reporting and auditing.
- The Market is the data collection engine that polls targets and normalizes metrics into a common model.
- The Market is the component that authenticates users and enforces role-based access control across the platform.
Explanation
The Turbonomic Market is the primary UI where the supply chain is visualized and where administrators review, approve, or execute actions. It is not responsible for authentication, data collection, or persistence, which are handled by other platform services.
Question 27Turbonomic Architecture, Deployment, and Installation
During installation planning, an administrator must ensure the Turbonomic platform can communicate with a vCenter target. Which network configuration is required for the platform to collect data from vCenter?
- Allow outbound HTTPS (TCP 443) from the Turbonomic platform to the vCenter Server. Correct answer.
- Allow bidirectional UDP on port 514 for syslog forwarding between vCenter and Turbonomic.
- Allow outbound SSH (TCP 22) from the Turbonomic platform to the vCenter Server.
- Allow inbound HTTPS (TCP 443) from vCenter to the Turbonomic platform.
Explanation
Turbonomic communicates with vCenter over the vSphere API, which uses HTTPS on TCP 443. The platform initiates the connection, so outbound HTTPS from Turbonomic to vCenter must be permitted.
Question 28Turbonomic Architecture, Deployment, and Installation
An administrator is deploying Turbonomic in a highly available configuration on-premises. Which statement best describes the recommended approach for the platform's database tier?
- Deploy the database on a shared NFS mount accessed by multiple Turbonomic instances simultaneously.
- Configure the database with replication or clustering supported by the platform to avoid a single point of failure. Correct answer.
- Rely on vSphere High Availability to restart the database VM automatically without additional configuration.
- Use a single database instance because Turbonomic does not support database redundancy.
Explanation
For high availability, the Turbonomic database tier should be configured with the replication or clustering mechanisms supported by the platform so that a database failure does not cause a full outage. Simply placing the database on shared storage or relying on VM restart does not provide the same level of protection.
Question 29Turbonomic Architecture, Deployment, and Installation
An administrator needs to install Turbonomic on a Kubernetes cluster. Which prerequisite must be satisfied before the installation can proceed?
- The cluster must be running on a single node to simplify networking.
- The cluster must have a default StorageClass defined for persistent volume provisioning. Correct answer.
- The cluster must have the Istio service mesh installed and configured.
- The cluster must use Docker as the container runtime exclusively.
Explanation
Turbonomic requires persistent storage for its components, so a default StorageClass must be available in the Kubernetes cluster to dynamically provision persistent volumes. Single-node clusters, Istio, and a specific container runtime are not installation prerequisites.
Question 30Turbonomic Architecture, Deployment, and Installation
An administrator is troubleshooting a Turbonomic deployment where the platform components cannot reach a target in a segmented network. The target's API is reachable from the administrator's workstation but not from the Turbonomic instance. Which action should the administrator take first to diagnose the issue?
- Reinstall the Turbonomic platform to reset all network configurations.
- Change the target's API port to a well-known port that is likely to be open.
- Verify that the Turbonomic instance's network route and firewall rules allow outbound traffic to the target's API endpoint. Correct answer.
- Disable the target's firewall entirely to allow all traffic from the Turbonomic instance.
Explanation
When a target is reachable from one host but not from Turbonomic, the most likely cause is a network path or firewall rule blocking outbound traffic from the Turbonomic instance. The administrator should first verify routing and firewall rules between Turbonomic and the target's API endpoint.
Question 31Platform Configuration, Licensing, and User Administration
In Turbonomic, which licensing construct determines the number of Virtual Machines that may be actively managed at the same time?
- The number of purchased license packs Correct answer.
- The cluster scope defined in the cloud account
- The license edition attached to the instance
- The number of enabled user accounts
Explanation
Turbonomic licenses are sold and applied as packs, and each pack grants a fixed quantity of managed VMs (or other licensed entities). The administrator applies license packs to the instance, and total capacity is the sum of those packs. Edition (Standard plus or Premium) changes the features available, not the managed-VM count.
Question 32Platform Configuration, Licensing, and User Administration
An administrator wants a new team member to view dashboards and run plans but never change policies or the platform configuration. Which built-in role should be assigned?
- Deployer
- Advisor Correct answer.
- Administrator
- Observer
Explanation
The Advisor role allows a user to explore the environment and run what-if plans without executing actions or editing policies. That matches the requirement of visibility plus planning while preventing configuration change. Administrator grants full control, and Observer is read-only with no plan execution.
Question 33Platform Configuration, Licensing, and User Administration
Which authentication mechanism lets an enterprise administrator map Turbonomic roles from existing directory groups rather than creating each user manually?
- API-only token authentication
- Shared administrator credentials
- Local user database with manual provisioning
- SAML single sign-on with group-to-role mapping Correct answer.
Explanation
Configuring SAML SSO against an identity provider lets Turbonomic consume group assertions and map directory groups to platform roles. Users then authenticate through the IdP and inherit the mapped role automatically. Local accounts and shared credentials require per-user maintenance and do not scale with directory groups.
Question 34Platform Configuration, Licensing, and User Administration
A license pack has been applied but the platform reports that managed VM capacity is exhausted. What is the correct first administrative step?
- Delete unused user accounts to free capacity
- Add additional license packs to raise managed-VM capacity Correct answer.
- Disable the cloud targets to reduce the VM count
- Restart the platform to re-evaluate licensing
Explanation
Managed-VM capacity is a direct function of the applied license packs, so exhausting it requires adding packs. User accounts and target settings are unrelated to the licensed entity count. A restart does not change purchased capacity.
Question 35Platform Configuration, Licensing, and User Administration
Which Turbonomic component must be reachable by users' browsers for the standard web UI to load in a self-hosted deployment?
- The database replication port
- The Kubernetes API server
- The Turbonomic web service endpoint Correct answer.
- The SMTP relay
Explanation
The web UI is served by the platform's web service endpoint, so browsers must be able to reach it over the network. The Kubernetes API server, database replication, and SMTP are internal or ancillary services not used for UI access.
Question 36Platform Configuration, Licensing, and User Administration
What is the purpose of defining scope in Turbonomic before enabling actions?
- To choose the language of the user interface
- To restrict which entities are analyzed and where actions may be executed Correct answer.
- To assign license packs to specific users
- To set the retention period for audit logs
Explanation
Scope determines the targets, groups, and clusters that the platform analyzes and can act upon. Constraining scope prevents unexpected changes in sensitive or out-of-policy environments. Licensing, log retention, and UI language are configured elsewhere.
Question 37Platform Configuration, Licensing, and User Administration
Which practice best protects the built-in administrator account in a production Turbonomic instance?
- Using the account for all API integrations
- Sharing the credential across the operations team
- Storing the credential in the default configuration file
- Disabling the account after creating named administrator users Correct answer.
Explanation
Named accounts with assigned roles provide accountability, so the built-in administrator should be reserved for break-glass use and disabled once named administrators exist. Sharing or embedding the credential in files removes traceability and increases exposure. API integrations should use dedicated credentials.
Question 38Platform Configuration, Licensing, and User Administration
Which item is required before Turbonomic can generate cost and utilization data for a public cloud account?
- A separate license per cloud region
- A local user account for each VM
- A configured cloud target with valid credentials Correct answer.
- An installed on-premises hypervisor
Explanation
Public cloud data is collected through a cloud target that authenticates with the provider using valid credentials. Without a working target the platform cannot discover or analyze those resources. Hypervisors are relevant only to on-premises targets, and licensing is not sold per region.
Question 39Platform Configuration, Licensing, and User Administration
An administrator must ensure that only a subset of production workloads can ever be resized automatically. Which combination achieves this with least privilege?
- Disable all targets outside business hours
- Create a scoped group for approved workloads and set automation policy on that group Correct answer.
- Enable global automation and rely on users to avoid production
- Grant all users the Administrator role and review changes weekly
Explanation
Automation policy can be applied at the group level, so defining a group of approved workloads and enabling action execution only there limits automated changes. Global automation with user discipline is not an enforceable control. Broad administrator access and target scheduling do not restrict which workloads may be resized.
Question 40Platform Configuration, Licensing, and User Administration
Which statement correctly distinguishes the Observer role from the Advisor role in Turbonomic?
- Observer can execute actions; Advisor cannot
- Observer can edit policies; Advisor can only view them
- Observer and Advisor differ only in UI language
- Observer is read-only; Advisor can also run plans Correct answer.
Explanation
Observer provides read-only visibility into the environment. Advisor adds the ability to run planning scenarios and what-if analyses without executing actions or changing policy. Neither role grants action execution or policy editing.
Question 41Platform Configuration, Licensing, and User Administration
During SAML configuration, users authenticate successfully at the identity provider but receive no permissions in Turbonomic. What is the most likely cause?
- Group or attribute assertions are not mapped to a Turbonomic role Correct answer.
- The license pack count is too low
- The cloud target credentials have expired
- The browser cache is full
Explanation
Successful IdP authentication without authorization usually means the assertion's group or attribute values do not match any configured role mapping. The platform authenticates the user but assigns no role. License count, target credentials, and browser state do not affect role assignment.
Question 42Platform Configuration, Licensing, and User Administration
Which configuration ensures that a newly added cluster is analyzed but never automatically modified?
- Assign all users the Deployer role for that cluster
- Exclude the cluster from scope entirely
- Add the cluster to scope with full automation enabled
- Add the cluster to scope and set its automation policy to recommend only Correct answer.
Explanation
Including the cluster in scope enables analysis, while a recommend-only automation level produces actions for review without execution. Excluding it prevents analysis altogether, and full automation permits automatic changes. User roles do not govern automated action execution.
Question 43Platform Configuration, Licensing, and User Administration
An administrator wants to validate the effect of a proposed resize policy before applying it to production. Which capability should be used?
- A planning scenario that simulates the policy change Correct answer.
- A license pack increase
- An audit log export
- A new cloud target registration
Explanation
Planning scenarios let administrators model changes such as policy edits and review projected effects before committing them. License changes, target registration, and log export do not simulate policy outcomes.
Question 44Platform Configuration, Licensing, and User Administration
Which action is required to grant a service account permission to call the Turbonomic API without interactive login?
- Create a local user with a strong password and share it
- Enable SAML for the service account
- Assign the Observer role to the built-in administrator
- Create an API-only user and generate credentials for programmatic access Correct answer.
Explanation
Programmatic access is provided through a dedicated API-only user whose credentials are used by the integration. This avoids interactive login and keeps automation separate from human accounts. Sharing a password or reusing the built-in administrator undermines accountability.
Question 45Platform Configuration, Licensing, and User Administration
A company purchases Premium edition but expects features available only in a higher tier. What should the administrator verify first?
- The time zone configured for the instance
- The number of user accounts created
- The retention setting on the audit log
- The edition and feature entitlements recorded for the applied license Correct answer.
Explanation
Feature availability follows the edition entitlement associated with the applied license, so the administrator should confirm which edition is actually recorded. If the recorded edition is lower than expected, the license application must be corrected. User counts, log retention, and time zone do not affect feature entitlements.
Question 46Platform Configuration, Licensing, and User Administration
Which setting determines how long action and login records remain available for compliance review in Turbonomic?
- The license pack quantity
- The scope definition
- The audit log retention configuration Correct answer.
- The SAML assertion lifetime
Explanation
Audit log retention controls how long historical records of actions and user activity are preserved. License packs govern capacity, scope governs analysis coverage, and assertion lifetime governs session validity at the IdP.
Question 47Platform Configuration, Licensing, and User Administration
An administrator needs to prevent a business unit from seeing another unit's workloads while allowing both to use the same platform. What is the appropriate approach?
- Disable the API for one business unit
- Deploy a separate instance per business unit
- Remove the Observer role from all users
- Use scoped groups and role assignments limited to each unit's entities Correct answer.
Explanation
Scoped groups combined with role assignments restrict what each user can view and act upon within a shared instance. This provides isolation without duplicating infrastructure. Separate instances are heavier than necessary, and disabling the API or removing roles does not create per-unit separation.
Question 48Platform Configuration, Licensing, and User Administration
Which task belongs to platform configuration rather than to daily optimization operations?
- Running a placement plan for a cluster
- Reviewing a utilization chart for a VM
- Registering a new hypervisor target and validating its credentials Correct answer.
- Approving a pending resize action
Explanation
Registering targets and validating credentials is an administrative configuration task that establishes the data foundation. Approving actions, reviewing charts, and running plans are routine operational activities performed within the configured environment.
Question 49Platform Configuration, Licensing, and User Administration
After applying a new license file, an administrator notices the platform still reports the previous edition. What is the most appropriate next step?
- Reboot every managed VM
- Disable SAML authentication
- Delete and recreate all user accounts
- Confirm the license was successfully applied and check the recorded entitlement Correct answer.
Explanation
The recorded entitlement should be verified to confirm the new license was accepted by the platform. If it was not applied successfully, the license upload must be repeated. Rebooting VMs, recreating users, or disabling SSO does not change license state.
Question 50Platform Configuration, Licensing, and User Administration
An organization requires that all administrative actions be attributable to individuals while still allowing a break-glass account. Which design satisfies both requirements?
- A single shared administrator account with a change log
- Individual Observer accounts only
- Named accounts with individual roles plus a disabled-by-default emergency administrator Correct answer.
- Federated accounts with no role mapping
Explanation
Named accounts provide attribution in the audit trail, and a disabled break-glass administrator can be enabled only during emergencies. Shared accounts obscure who performed an action, Observer-only access cannot administer the platform, and federated accounts without role mapping receive no permissions.