You should be able to explain what you are doing.
Perguntas de entrevista de Technical Support Engineer 2
28 Perguntas de entrevista compartilhadas pelos candidatos | technical support engineer 2
1. Tell me of a time you went out of your way to help a colleague. Explain what happened and what the results was. 2. Tell me about a project or task you were involved in your current job or past role. Explain what the problem, how you were a part of the project.
Excel experience for windows OS.
How is your experience with Azure?
What is the purpose of GPOs?
Technical questions on windows, linux, and networking
Tell me about yourself, your previous experience. She asked a few question about mu current job. Difficulties and success
Question 1 - Integration Not Working I’m not seeing the metric system.disk.directory.file.bytes in my Datadog account. I’m trying to monitor our application directory and I have installed a Windows Datadog Agent onto our environment. This is what we have so far for the integration: init_config: instances: - directory: "C:\Users\projects\prod-application" I know I saved the configuration, directly after saving it I then checked the platform, and I’m still not receiving the metric. I tried uninstalling the Agent and setting up the integration again, but it tells me: 2021-07-19 08:06:22 UTC | CORE | INFO | (pkg/metadata/host/host.go:169 in getPublicIPv4) | No public IPv4 address found 2021-07-19 09:12:05 UTC | CORE | ERROR | (pkg/util/azure/diagnosis.go:21 in diagnose) | Azure HostAliases: unable to query metadata endpoint: status code 404 trying to GET http://111.254.167.255/metadata/instance/compute/vmId?api-version=201 7-04-02 2021-07-19 09:12:05 UTC | CORE | ERROR | (pkg/util/azure/diagnosis.go:21 in diagnose) | Azure HostAliases: unable to query metadata endpoint: status code 404 trying to GET http://169.254.169.254/metadata/instance/compute/vmId?api-version=201 7-04-02 2021-07-19 09:12:17 UTC | CORE | WARN | (pkg/autodiscovery/providers/file.go:192 in collectEntry) | C:\ProgramData\Datadog\conf.d\directory.d\conf.yaml is not a valid config file: yaml: line 3: found unknown escape character 2021-07-19 09:12:20 UTC | CORE | INFO | (pkg/serializer/serializer.go:374 in sendMetadata) | Sent metadata payload, size (raw/compressed): 1331/379 bytes. Can you let me know what I’m doing wrong so I can get this integration up and running?
1. FC protocol layers 2. SAN basics 3. Cloud Computing basics
Questions on virtualization, VMware products, ESXi services etc
Exibindo 1 a 10 perguntas de entrevista