dynatrace

Un ActiveGate de entorno está enlazado de forma predeterminada a un único entorno. Verdadero. Falso.

Los instaladores de ActiveGates de entorno y ActiveGates de clúster se descargan respectivamente de... Sitio web de Dynatrace / Correo electrónico de licencias. Correo electrónico de licencias / Sitio web de Dynatrace. Sitio web de Dynatrace / Consola de administración de clústeres. Sitio web de Cluster Management Console / Dynatrace. Entorno de supervisión / Consola de administración de clústeres. Consola de administración de clústeres / Entorno de supervisión.

ActiveGates se puede utilizar para... Extraer datos de otras plataformas (por ejemplo, Azure, AWS, Kubernetes, etc.). Enviar alertas sobre problemas. Validación de licencias de Dynatrace. Descargar actualizaciones de OneAgent. Ejecución de extensiones. Supervisión de solicitudes SQL. Menor sobrecarga de red. Simplifique la gestión de cortafuegos. Supervisión de mainframes.

La implementación de ActiveGates... Disminuir el consumo de ancho de banda de la red. No tienen ningún impacto en el consumo de ancho de banda de la red. Aumentar el consumo de ancho de banda de la red.

Seleccione los diferentes tipos de ActiveGates. Monitoreo de ActiveGate. ActiveGate verde. ActiveGate de producción. Clúster ActiveGate. Entorno ActiveGate. ActiveGate rojo. ActiveGate azul.

Un ActiveGate es un componente necesario. Falso. Verdadero.

14.¿Dónde se pueden administrar usuarios y grupos en Dynatrace Managed?. Página Implementación de Dynatrace. Ticket de soporte. Sitio web de Dynatrace. Control en la nube. Consola de administración de clústeres. Console mangamente c.

13.¿Cómo se pueden crear nuevos entornos para Dynatrace Managed?. A través de la API REST del entorno de Dynatrace. A través de la página Implementar Dynatrace. A petición por correo electrónico. A través del sitio web de Dynatrace. A través de la API de REST de la consola de administración de clústeres. A través de la interfaz de usuario web de la consola de administración de clústeres.

12.Las actualizaciones administradas de Dynatrace se activan... Cuando hay más de 250 OneAgents conectados al clúster. Cuando el administrador de Dynatrace Managed hace clic en <Actualizar ahora>. A una hora establecida por el administrador de Dynatrace Managed. Cuando se llama al punto de conexión pertinente en la API de REST de la consola de administración de clústeres. Cuando hay más de 200 OneAgents conectados al clúster. Cuando Dynatrace lo fuerza.

1.Las actualizaciones del clúster administrado por Dynatrace son obligatorias. Verdadero. Falso.

10.Las versiones de OneAgent son compatibles con. 9 meses (Estándar) / 9 meses (Premium). 6 meses (Estándar) / 6 meses (Premium). 9 meses (Estándar) / 12 meses (Premium). 12 meses (Estándar) / 18 meses (Premium).

9.Las actualizaciones de OneAgent son obligatorias. Falso. Verdadero.

¿Para qué sirve Mission Control?(misión control no se usa en saas). Facturación de Dynatrace SaaS. Facturación de Dynatrace Managed. Utilización de licencias para Dynatrace Managed. Soporte remoto por parte de los empleados de Dynatrace para Dynatrace Managed. Comprimir el tráfico de OneAgent para Dynatrace Managed. Supervisión del estado del clúster para Dynatrace Managed. Supervisión del estado del clúster para Dynatrace SaaS. Comprima el tráfico de OneAgent para Dynatrace SaaS. Soporte remoto por parte de los empleados de Dynatrace para Dynatrace SaaS.

7.Dynatrace SaaS utiliza Mission Control. Falso. Verdadero.

Al observar la utilización de la CPU de un host en particular hace 18 días, ¿cuál es la resolución más alta que obtendrá de forma predeterminada?. 5 minutos. 3 días. 1 minuto. 1 día. 15 minutos. 1 hora.

4.Las métricas de Dynatrace se guardan para obtener el máximo. 6 meses. Sin límite. 35 días. 1 año. 5 años.

Dynatrace no se puede ejecutar en las instalaciones. Falso. Verdadero.

Un OneAgent es... Un almacén de datos que almacena datos de supervisión. Un motor que analiza los datos de monitorización. Un empleado de seguridad de Dynatrace. Un agente federal del departamento de ONE. Un software que envía datos de telemetría.

3.Why would you put a OneAgent on a database?. To capture SQL requests. To monitor the database's infrastructure health. To make the application faster. OneAgent on databases don't consume any licenses. To calculate the service score.

¿Qué significan las líneas punteadas en SmartScape?. La conexión solía estar allí, pero no ha estado activa en las últimas 2 horas. La conexión es UDP en lugar de TCP. La conexión está ahí, pero el número de solicitudes es limitado. La conexión está prevista pero aún no confirmada.

5.Las entidades que se muestran en SmartScape se hacen con un período de tiempo. Que se configura en las zonas de administración. 2 horas. Que se selecciona en el selector de tiempo. 72 horas.

6.Los nombres de host se pueden cambiar. Sí, manualmente o a través de reglas de nomenclatura de host. Sí, manualmente o a través de reglas de agrupación de hosts. No.

7.¿Cuáles son algunas de las entidades que aparecen en la página Anfitriones?. Instancias de servicio. Hosts no supervisados (también conocidos como candidatos de supervisión). Servidores dedicados. Anfitriones que tienen problemas. Vms. Grupos de procesos.

8.¿Cuáles son algunas de las entidades que aparecen en la página de información general de la red?. Latencia. Conectividad. Aplicaciones. Interfaces. Ancho de banda. Hosts. Grupos de procesos. Servicios. Retransmisiones. Tráfico.

10.Un grupo de procesos puede contener instancias con tecnología diferente. Falso. Verdadero.

11.¿Debe un grupo de procesos contener instancias que hagan cosas diferentes?. No. No importa. Sí.

12.¿Cómo se puede cambiar la composición de los grupos de procesos?. Reglas de etiquetado de grupos de procesos. Reglas de detección de grupos de procesos. Reglas de actualización de grupos de procesos. Reglas de supervisión de grupos de procesos. Reglas de combinación de grupos de procesos. Reglas de nomenclatura de grupos de procesos. Reglas de división de grupos de procesos.

Se puede cambiar el nombre de los servicios. No. Sí, manualmente o a través de reglas de nomenclatura de servicios. Sí, manualmente o a través de reglas de detección de servicios.

14.Los servicios se pueden fusionar. Sí, pero solo después de ponerse en contacto con Dynatrace. Sí, a través de reglas establecidas a través de la API. No.

15.¿Dónde puedo encontrar fácilmente la raíz de contexto de un servicio de solicitud web?. Seguimiento del servicio. Flujo de servicio. Puntos de acceso de servicio. Sección de propiedades y etiquetas.

16.¿Cuáles son los elementos que Dynatrace tiene en cuenta por defecto a la hora de crear Servicios del tipo "Solicitud Web"?. Id. de aplicación web. Nombre del servidor web. Raíz de contexto. Tendencias en Twitter. Versión del servidor web. Acciones del NASDAQ. Sistema operativo. Ubicación física. Etiqueta de servidor web. Tiempo.

7.Si desea deshabilitar el monitoreo de Node.js en todas partes, pero aún así dejarlo habilitado en un host A en particular, ... No es posible. Conectar el host A con otro ActiveGate. Creación de una solicitud de clave en el host A. Deshabilite la supervisión de Node.js globalmente, habilítela en el host A. Deshabilite la supervisión de Node.js globalmente, use oneagentctl en el host A.

18.¿Por qué verías un servicio opaco?. El nivel de código visible no está disponible para esa tecnología. No hay ActiveGate presente. Se desconoce la tecnología de servicio. Ese servicio es una tecnología heredada.

Cuando un servicio realiza una llamada a otro servicio que no está supervisado por Dynatrace... Esas solicitudes se muestran como solicitudes a un servicio externo. Esas solicitudes se agruparán en "Otros". Esas solicitudes no aparecerán en Dynatrace. Esas solicitudes solo se muestran si pertenecen a un proveedor de servicios de terceros conocido.

21.¿Cuál es el punto de marcar un atributo de solicitud como que contiene datos confidenciales?. El valor del atributo request se cifra con una contraseña que solo conoce Dynatrace. El valor del atributo request nunca se captura para el cumplimiento del RGPD. El valor del atributo request se cifra con una contraseña que solo conocen los administradores autorizados. El valor del atributo request está enmascarado y solo es visible para los usuarios autorizados. No es posible.

22.Los grupos host se pueden configurar y/o modificar a través de la interfaz de usuario web. Verdadero. Falso.

3.Los grupos de hosts se pueden configurar a través de... API REST del entorno de supervisión. Instalador de OneAgent. API de REST de la consola de administración de clústeres. Interfaz de usuario web de Cluster Management Console. OneAgentConfig. OneAgentCTL. Interfaz de usuario web del entorno de supervisión.

3.For host tags, the prefix [Environment] indicates that. The tag was created via the Environment API. The tag was created using oneagenctl. The tag was created via the Configuration API. The tag was inherited from the host group. The tag was created using oneagentconfig. The tag was inherited from the environment.

4.Metadata typically changes frequently. True. False.

How do you manage which URLs are grouped in which application?. Application address rules. Application grouping rules. Application segmentation rules. Application monitoring rules. Application detection rules.

How can Dynatrace RUM know that it's the same user that accesses an application?. Persistent cake. Persistent cookie. Browser version. Operating system. Geographic location. FaceID. Browser fingerprint.

7.Why would you enable JavaScript framework in your application settings?. Measure Apdex scores. Limit the number of consumed licenses. Get better support for XHR requests. Speed up known and supported JavaScript frameworks.

Dynatrace Real User Monitoring is not possible without using a OneAgent. True. False.

9.How does the Real User Monitoring JavaScript tag automatically end up in HTML pages?. It's injected by the RUM browser extension. It's injected by the ActiveGate. It's added by the web developer. It's injected by the OneAgent that sits on the frontend (e.g. web server). It's not needed for RUM.

10.When would it make sense to use agentless RUM?. To enable session replay. To monitor an application when you cannot install a OneAgent on the frontend servers. Agentless RUM is not possible. To monitor databases with minimum overhead. To minimize monitoring overhead. To monitor an application when you cannot modify the HTML.

12.What is Apdex?. Apdex is the name of the AI engine of Dynatrace that figures out the root cause of problems. Apdex is a measure of response time based against a set threshold. Apdex is short for Application Dexterity and measures how usable an application UI is. Apdex is the name of the JavaScript library injected by Dynatrace into HTML pages.

13.What is a conversion goal?. An overall score of the user experience for a particular user session. Successful updates of the injected RUM JavaScript. A metric that indicates how much time the environment didn't detect any issues. A specific milestone that indicates some type of objective that you want to track.

14.What is the user experience score?. A metric that categorizes every user session monitored with RUM. A metric that categorizes every user action monitored with RUM. A metric that measures how many users are accessing a specific application. A metric that predicts what the user experience will be for a certain user monitored by RUM. A metric that predicts the credit score of a particular user of an application monitored by RUM.

15.What is visually complete?. A point-in-location metric that measures when the visual area of a page has finished loading. A point-in-time metric that measures when a OneAgent has finished processing a web page. A point-in-time metric that measures when a OneAgent has finished analyzing a web page. A point-in-time metric that measures when the visual area of a page has finished loading.

A lower speed index is better than a higher one. True. False.

Users monitored by RUM can be named based on their user account through the feature. It's not possible. Key user action. User tags. Key request.

19.When is a web RUM session considered to be finished?. When the JavaScript function dtrum.endSession() is called. After 15 minutes of browser inactivity. When the session duration reaches 8 hours. After 35 minutes of browser inactivity. Once the limit of 200 user actions per session is reached. After 30 minutes of browser inactivity. When the JavaScript function dtrum.timeoutSession() is called. When the user closes their browser (*). When the session duration reaches 1 hour. Once the limit of 250 user actions per session is reached.

Session replay relies on screen share permissions. False. True.

21.When is a mobile RUM session considered to be finished?. After 35 minutes of app inactivity. After 10 minutes of app inactivity (*). When the user or the mobile operating system closes or force stops the app (*). When the Dynatrace SDK API function endVisit() is called. When the Dynatrace SDK API function endSession() is called. When the session duration reaches 6 hours. When the session duration reaches 1 hour. When the session duration reaches 4 hours. After 30 minutes of app inactivity.

What are the available options for iOS instrumentation?. Maple plugin. Carthage. CofeePods. Gradle plugin. Alexandria. OneAgent SDK. Swift Package Manager. Troy. CocoaPods.

What are the available options for Android instrumentation?. OneAgent SDK. Gradle plugin. Carthage. Snap Package Manager. Alexandria. Swift Package Manager. Management profiles. Mobile VM.

Dynatrace Synthetic Monitoring is for public Internet-facing applications only. False. True.

3.What are the different types of Synthetic Monitors that exist. Browser clickpath monitor. HTTP monitor. Browser single-URL monitor. Tomcat monitor. SOAP monitor. MySQL monitor. CHEESE monitor.

4.What browser is used by Dynatrace synthetic browser monitors?. Chromium/Chrome. Brave. Tor Browser. Edge.

5.What device options can be changed for synthetic browser monitors?. Bandwidth (throttling). Device type (desktop, mobile, etc.). OS version. Screen orientation (portrait vs landscape). Screen size. App version. Battery level. VPN endpoint. Connection latency. SSL/TLS version.

What is content validation in Dynatrace?. A check against the presence or absence of a page element in Synthetic Monitoring. An automated check done by the RUM JavaScript agent to check if another agent is already injected. A security check done on all monitored web requests against a public database of know exploits. A check done by the Synthetic Monitoring browser extension. An automated check against adult material on the monitored web application.

7.How does the AI engine of Dynatrace figure out what the root cause is of a problem?. It sends a request to Mission Control which then does a full analysis based on environments and historical data of all Dynatrace customers. It check through all the past problems to see what the root cause was in the past. It makes random guesses. It uses a deterministic approach with a causation model to analyze dependencies to figure out which components are most likely the root cause of the problem. It considers the first component that experiences an issue as the root cause of all other connected issues. It uses a combustion model to analyze dependencies and get velocity ratings to choose the most likely root cause.

Which baselines dimensions are used for Applications?. Geolocation. Bandwidth. User action. ISP. Touch interface vs mouse interface. Browser. Operating system. Screen resolution. IP address.

9.Which baselines dimensions are used for Services?. Service quality. Service method. Service level. Service method group. Service context root. Service name.

10.Application traffic drops and traffic spikes anomaly detection. Don't exist. Are based on the application's traffic over a period of 14 days. Are based on the application's traffic over a period of 28 days. Are based on the application's traffic over a period of 7 days.

11.Select all severity levels that exist in Dynatrace. Failure. Error. Extreme. Slowdown. Custom. Issue. Info. Monitoring unavailable. Availability. Resource.

12.The correct order of the severity levels from most severe to least severe is. Availability > Error > Slowdown > Resource. Failure > Availability > Slowdown > Resource. Availability > Failure > Slowdown > Resource. Slowdown > Failure > Availability > Slowdown.

3.How can the availability and performance of internal non-Internet facing applications be measured?. A synthetic HTTP monitor that runs on an Environment ActiveGate that's set up as a private location. A synthetic browser monitor that runs on a private location hosted by Dynatrace. By deploying OneAgents on the relevant servers. A synthetic browser monitor that runs on an Environment ActiveGate that's set up as a private location. A synthetic HTTP monitor that runs on a Cluster ActiveGate that's set up as a private location. By using the self-monitoring capabilities of Mission Control. A synthetic CHEESE monitor that runs on an Environment ActiveGate that's set up as a private location. A synthetic CHEESE monitor that runs on a Cluster ActiveGate that's set up as a private location.

4.Tags can be used as filters for maintenance windows. True. False.

Tags can be used as filters for maintenance windows. True. False.

15.What are use cases for maintenance windows in Dynatrace?. To disable problem detection. To disable Real User Monitoring. To disable alerting. To enable infrastructure monitoring. To disable the OneAgent.

16.What's the purpose of unplanned maintenance windows?. They're defined proactively for an ongoing outage. They're defined retroactively for bank holidays. They're defined retroactively for an ongoing outage. They're defined proactively for bank holidays.

17.What are the built-in reports that exist in Dynatrace?. Availability report. Service quality report. Apdex report. Davis report. Service speed report.

18.How is the Dynatrace score calculated?. It's an average of the Applications score, Services score, and Infrastructure score. It's a percentage of time that no issues were detected by Dynatrace. There's no such thing. It's an average of the Applications score, Services score, and Responsiveness score. It's a global score compared to the average Applications scores.

19.How is the Application score calculated?. It considers the application's average Speed index value and percentage of user actions that are not affected by problems. It considers the application's average Apdex value and percentage of user sessions that are not affected by problems. It considers the application's average visually complete value and percentage of user actions that are not affected by problems. It considers the application's average visually complete value and percentage of user sessions that are not affected by problems. It considers the application's average Speed index value and percentage of user sessions that are not affected by problems.

How is the Services score calculated?. It's the percentage of service calls that were successful and unaffected by problems. It's the percentage of service calls that were slower than the baseline compared to last month. It's the percentage of service calls that were slower than the baseline compared to last week. It's the percentage of service calls that were faster than the baseline compared to last week. It's the percentage of service calls that were unsuccessful and affected by problems. There's no such thing.

21.How is the Infrastructure score calculated?. It's the percentage of host time during which no problems were encountered. It's the percentage of host time during which problems were encountered. It's the weighted percentage of used CPU and memory on all hosts. It's the percentage of host time during which no resource contention problems were encountered. It's the weighted percentage of free CPU and memory on all hosts.

How is the Responsiveness score calculated?. There's no such thing. It's a normal average of Apdex, Speed index, and user experience score. It's the percentage of fast pages compared to slow pages. It's the average of Visually complete of all applications. It's a weighted average of Apdex, Speed index, and user experience score.

23.Management zones. Cannot span monitoring environments. Can overlap. Can be used a filter. Can be used to limit access to certain entities. Cannot overlap. Can be created via the OneAgent command line tool. Can span monitoring environments. Depend on process groups.