Why you should use Docker Online Test?

The Teste do Docker makes use of scenario-based questions to test for on-the-job skills as opposed to theoretical knowledge, ensuring that candidates who do well on this screening test have the relavant skills. The questions are designed to covered following on-the-job aspects: Entendendo o básico e os conceitos do Docker Criando, gerenciando e implantando imagens do Docker Trabalhando com contêineres do Docker e seu ciclo de vida Compreendendo a rede do Docker e a comunicação entre recipientes Gerenciando volumes do docker e dados persistentes Trabalhando com o Docker compor para definir e gerenciar aplicativos multi-containers Implantando e gerenciando serviços usando o Docker Swarm Implementando práticas e políticas de segurança do Docker Orquestrando recipientes do Docker para implantações em larga escala

Docker Online Test

Q: What topics are covered in the Docker Online Test?

Docker Basics Imagens do Docker Docker Recipulações Docker Networking Volumes do Docker Docker compor Docker Swarm Segurança do Docker Orquestração do Docker Docker Solução de problemas

About the test:

O teste do Docker usa MCQs baseados em cenários para avaliar os candidatos sobre sua proficiência no trabalho com contêineres do Docker, seu conhecimento da arquitetura do docker, interface da linha de comando do Docker, sintaxe do dockerfile, rede de docker, volumes de docker e composição do docker. Essas habilidades/tópicos -chave são importantes para avaliar a capacidade de um candidato de implantar e gerenciar aplicativos usando o Docker.

Covered skills:

Docker Basics
Docker Recipulações
Volumes do Docker
Docker Swarm
Orquestração do Docker

Imagens do Docker
Docker Networking
Docker compor
Segurança do Docker
Docker Solução de problemas

Preview this test

Ver Scorecard de amostra

9 reasons why

Adaface Docker Test is the most accurate way to shortlist Desenvolvedor do Dockers

Reason #1

Tests for on-the-job skills

The Docker Online Test helps recruiters and hiring managers identify qualified candidates from a pool of resumes, and helps in taking objective hiring decisions. It reduces the administrative overhead of interviewing too many candidates and saves time by filtering out unqualified candidates at the first step of the hiring process.

The test screens for the following skills that hiring managers look for in candidates:

Capacidade de entender e explicar o básico do Docker
Capacidade de criar, gerenciar e personalizar imagens do Docker
Capacidade de lançar, gerenciar e solucionar problemas de contêineres do Docker
Capacidade de configurar e gerenciar redes do Docker
Capacidade de trabalhar com volumes do Docker e persistência de dados
Capacidade de usar o Docker compor para aplicativos multi-containers
Capacidade de implantar e gerenciar serviços usando o Docker Swarm
Capacidade de implementar medidas de segurança no ambiente do Docker
Capacidade de entender e implementar o Docker Orchestration
Capacidade de solucionar problemas comuns no ambiente do Docker

Reason #2

No trick questions

Traditional assessment tools use trick questions and puzzles for the screening, which creates a lot of frustration among candidates about having to go through irrelevant screening assessments.

View sample questions

The main reason we started Adaface is that traditional pre-employment assessment platforms are not a fair way for companies to evaluate candidates. At Adaface, our mission is to help companies find great candidates by assessing on-the-job skills required for a role.

Why we started Adaface

Preview this test

Ver Scorecard de amostra

Reason #3

Non-googleable questions

We have a very high focus on the quality of questions that test for on-the-job skills. Every question is non-googleable and we have a very high bar for the level of subject matter experts we onboard to create these questions. We have crawlers to check if any of the questions are leaked online. If/ when a question gets leaked, we get an alert. We change the question for you & let you know.

How we design questions

Estes são apenas uma pequena amostra da nossa biblioteca de mais de 10.000 perguntas. As perguntas reais sobre isso Teste do Docker será não-googleable.

🧐 Question
Medium Docker Multistage Build Analysis Multistage Builds Optimization	Solve
Consider the following Dockerfile, which utilizes multistage builds. The aim is to build a lightweight, optimized image that just runs the application. The Dockerfile first defines a base image that includes Node.js and npm, then it creates an intermediate image to install the npm dependencies. Afterwards, it runs the tests in another stage and finally, creates the release image. Which of the following statements are true? A: The final image will include the test scripts. B: If a test fails, the final image will not be created. C: The node_modules directory in the final image comes from the base image. D: The final image will only contain the necessary application files and dependencies. E: If the application's source code changes, only the release stage needs to be rebuilt.
Easy Docker Networking and Volume Mounting Interplay Networking Volume Mounting	Solve
You have two docker containers, X and Y. Container X is running a web service listening on port 8080, and container Y is supposed to consume this service. Both containers are created from images that don't have any special network configurations. Container X has a Dockerfile as follows: And, you build and run it with the following commands: Container Y is also running alpine with python installed, and it's supposed to read data from the `/app/data` directory and send a GET request to `http://localhost:8080` every 5 minutes. The Dockerfile for container B is: And you run it with: Assuming all the python scripts work perfectly and firewall isn't blocking any connections, you find that container Y can't access the web service of container X via `http://localhost:8080` and also it can't read the data in `/app/data` directory. What could be the potential reason(s)? A: Y can't access X's web service because they're in different Docker networks. B: Y can't read the data because the volume is not shared correctly. C: Both A and B are correct. D: Both A and B are incorrect.
Medium Dockerfile Optimization Dockerfile Multi-stage builds Layer Caching	Solve
You have been asked to optimize a Dockerfile for a Python application that involves a heavy dependency installation. Here is the Dockerfile you are starting with: Given that the application's source code changes frequently but the dependencies listed in requirements.txt rarely change, how can you optimize this Dockerfile to take advantage of Docker's layer caching, reducing the build time? A: Move the `RUN pip install` command to before the `COPY` command. B: Change `COPY . /app` to `COPY ./app.py /app` and move the `RUN pip install` command to before the `COPY` command. C: Add `RUN pip cache purge` before `RUN pip install`. D: Replace the base image with `python:3.8-slim`. E: Implement multi-stage builds.
Medium Dockerfile Updates Cache	Solve
Check the following Dockerfile used for a project (STAGE 1): We created an image from this Dockerfile on Dec 14 2021. A couple of weeks after Dec 14 2021, Ubuntu released new security updates to their repository. After 2 months, we modified the file (STAGE 2): Couple of weeks later, we further modified the file to add a local file ada.txt to /ada.txt (STAGE 3): (Note that ada.txt exists in /home/adaface and the dockerfile exists in /home/code folders) Pick correct statements: A: If we run “docker build .” at STAGE 2, new Ubuntu updates will be fetched because apt-get update will be run again since cache is invalidated for all lines/layers of Dockerfile when a new line is added. B: If we run “docker build .” at STAGE 2, new Ubuntu updates will not be fetched since cache is invalidated only for last two lines of the updated Dockerfile. Since the first two commands remain the same, cached layers are re-used skipping apt get update. C: To skip Cache, “docker build -no-cache .” can be used at STAGE 2. This will ensure new Ubuntu updates are picked up. D: Docker command “docker build .” at STAGE 3 works as expected and adds local file ada.txt to the image. E: Docker command “docker build .” at STAGE 3 gives an error “no such file or directory” since /home/adaface/ada.txt is not part of the Dockerfile context.
Medium Efficient Dockerfile Dockerfile	Solve
Review the following Dockerfiles that work on two projects (project and project2): All Docker files have the same end result: - ‘project’ is cloned from git. After running few commands, ‘project’ code is removed. - ‘project2’ is copied from file system and permissions to the folder is changed. Pick the correct statements: A: File 1 is the most efficient of all. B: File 2 is the most efficient of all. C: File 3 is the most efficient of all. D: File 4 is the most efficient of all. E: Merging multiple RUN commands into a single RUN command is efficient for ‘project’ since each RUN command creates a new layer with changed files and folders. Deleting files with RUN only marks these files as deleted but does not reclaim disk space. F: Copying ‘project2’ files and changing ownership in two separate commands will result in two layers since Docker duplicates all the files twice.

	🧐 Question	🔧 Skill
	Medium Docker Multistage Build Analysis Multistage Builds Optimization	3 mins Docker	Solve
Consider the following Dockerfile, which utilizes multistage builds. The aim is to build a lightweight, optimized image that just runs the application. The Dockerfile first defines a base image that includes Node.js and npm, then it creates an intermediate image to install the npm dependencies. Afterwards, it runs the tests in another stage and finally, creates the release image. Which of the following statements are true? A: The final image will include the test scripts. B: If a test fails, the final image will not be created. C: The node_modules directory in the final image comes from the base image. D: The final image will only contain the necessary application files and dependencies. E: If the application's source code changes, only the release stage needs to be rebuilt.
	Easy Docker Networking and Volume Mounting Interplay Networking Volume Mounting	3 mins Docker	Solve
You have two docker containers, X and Y. Container X is running a web service listening on port 8080, and container Y is supposed to consume this service. Both containers are created from images that don't have any special network configurations. Container X has a Dockerfile as follows: And, you build and run it with the following commands: Container Y is also running alpine with python installed, and it's supposed to read data from the `/app/data` directory and send a GET request to `http://localhost:8080` every 5 minutes. The Dockerfile for container B is: And you run it with: Assuming all the python scripts work perfectly and firewall isn't blocking any connections, you find that container Y can't access the web service of container X via `http://localhost:8080` and also it can't read the data in `/app/data` directory. What could be the potential reason(s)? A: Y can't access X's web service because they're in different Docker networks. B: Y can't read the data because the volume is not shared correctly. C: Both A and B are correct. D: Both A and B are incorrect.
	Medium Dockerfile Optimization Dockerfile Multi-stage builds Layer Caching	2 mins Docker	Solve
You have been asked to optimize a Dockerfile for a Python application that involves a heavy dependency installation. Here is the Dockerfile you are starting with: Given that the application's source code changes frequently but the dependencies listed in requirements.txt rarely change, how can you optimize this Dockerfile to take advantage of Docker's layer caching, reducing the build time? A: Move the `RUN pip install` command to before the `COPY` command. B: Change `COPY . /app` to `COPY ./app.py /app` and move the `RUN pip install` command to before the `COPY` command. C: Add `RUN pip cache purge` before `RUN pip install`. D: Replace the base image with `python:3.8-slim`. E: Implement multi-stage builds.
	Medium Dockerfile Updates Cache	2 mins Docker	Solve
Check the following Dockerfile used for a project (STAGE 1): We created an image from this Dockerfile on Dec 14 2021. A couple of weeks after Dec 14 2021, Ubuntu released new security updates to their repository. After 2 months, we modified the file (STAGE 2): Couple of weeks later, we further modified the file to add a local file ada.txt to /ada.txt (STAGE 3): (Note that ada.txt exists in /home/adaface and the dockerfile exists in /home/code folders) Pick correct statements: A: If we run “docker build .” at STAGE 2, new Ubuntu updates will be fetched because apt-get update will be run again since cache is invalidated for all lines/layers of Dockerfile when a new line is added. B: If we run “docker build .” at STAGE 2, new Ubuntu updates will not be fetched since cache is invalidated only for last two lines of the updated Dockerfile. Since the first two commands remain the same, cached layers are re-used skipping apt get update. C: To skip Cache, “docker build -no-cache .” can be used at STAGE 2. This will ensure new Ubuntu updates are picked up. D: Docker command “docker build .” at STAGE 3 works as expected and adds local file ada.txt to the image. E: Docker command “docker build .” at STAGE 3 gives an error “no such file or directory” since /home/adaface/ada.txt is not part of the Dockerfile context.
	Medium Efficient Dockerfile Dockerfile	2 mins Docker	Solve
Review the following Dockerfiles that work on two projects (project and project2): All Docker files have the same end result: - ‘project’ is cloned from git. After running few commands, ‘project’ code is removed. - ‘project2’ is copied from file system and permissions to the folder is changed. Pick the correct statements: A: File 1 is the most efficient of all. B: File 2 is the most efficient of all. C: File 3 is the most efficient of all. D: File 4 is the most efficient of all. E: Merging multiple RUN commands into a single RUN command is efficient for ‘project’ since each RUN command creates a new layer with changed files and folders. Deleting files with RUN only marks these files as deleted but does not reclaim disk space. F: Copying ‘project2’ files and changing ownership in two separate commands will result in two layers since Docker duplicates all the files twice.

	🧐 Question	🔧 Skill	💪 Difficulty	⌛ Time
	Docker Multistage Build Analysis Multistage Builds Optimization	Docker	Medium	3 mins	Solve
Consider the following Dockerfile, which utilizes multistage builds. The aim is to build a lightweight, optimized image that just runs the application. The Dockerfile first defines a base image that includes Node.js and npm, then it creates an intermediate image to install the npm dependencies. Afterwards, it runs the tests in another stage and finally, creates the release image. Which of the following statements are true? A: The final image will include the test scripts. B: If a test fails, the final image will not be created. C: The node_modules directory in the final image comes from the base image. D: The final image will only contain the necessary application files and dependencies. E: If the application's source code changes, only the release stage needs to be rebuilt.
	Docker Networking and Volume Mounting Interplay Networking Volume Mounting	Docker	Easy	3 mins	Solve
You have two docker containers, X and Y. Container X is running a web service listening on port 8080, and container Y is supposed to consume this service. Both containers are created from images that don't have any special network configurations. Container X has a Dockerfile as follows: And, you build and run it with the following commands: Container Y is also running alpine with python installed, and it's supposed to read data from the `/app/data` directory and send a GET request to `http://localhost:8080` every 5 minutes. The Dockerfile for container B is: And you run it with: Assuming all the python scripts work perfectly and firewall isn't blocking any connections, you find that container Y can't access the web service of container X via `http://localhost:8080` and also it can't read the data in `/app/data` directory. What could be the potential reason(s)? A: Y can't access X's web service because they're in different Docker networks. B: Y can't read the data because the volume is not shared correctly. C: Both A and B are correct. D: Both A and B are incorrect.
	Dockerfile Optimization Dockerfile Multi-stage builds Layer Caching	Docker	Medium	2 mins	Solve
You have been asked to optimize a Dockerfile for a Python application that involves a heavy dependency installation. Here is the Dockerfile you are starting with: Given that the application's source code changes frequently but the dependencies listed in requirements.txt rarely change, how can you optimize this Dockerfile to take advantage of Docker's layer caching, reducing the build time? A: Move the `RUN pip install` command to before the `COPY` command. B: Change `COPY . /app` to `COPY ./app.py /app` and move the `RUN pip install` command to before the `COPY` command. C: Add `RUN pip cache purge` before `RUN pip install`. D: Replace the base image with `python:3.8-slim`. E: Implement multi-stage builds.
	Dockerfile Updates Cache	Docker	Medium	2 mins	Solve
Check the following Dockerfile used for a project (STAGE 1): We created an image from this Dockerfile on Dec 14 2021. A couple of weeks after Dec 14 2021, Ubuntu released new security updates to their repository. After 2 months, we modified the file (STAGE 2): Couple of weeks later, we further modified the file to add a local file ada.txt to /ada.txt (STAGE 3): (Note that ada.txt exists in /home/adaface and the dockerfile exists in /home/code folders) Pick correct statements: A: If we run “docker build .” at STAGE 2, new Ubuntu updates will be fetched because apt-get update will be run again since cache is invalidated for all lines/layers of Dockerfile when a new line is added. B: If we run “docker build .” at STAGE 2, new Ubuntu updates will not be fetched since cache is invalidated only for last two lines of the updated Dockerfile. Since the first two commands remain the same, cached layers are re-used skipping apt get update. C: To skip Cache, “docker build -no-cache .” can be used at STAGE 2. This will ensure new Ubuntu updates are picked up. D: Docker command “docker build .” at STAGE 3 works as expected and adds local file ada.txt to the image. E: Docker command “docker build .” at STAGE 3 gives an error “no such file or directory” since /home/adaface/ada.txt is not part of the Dockerfile context.
	Efficient Dockerfile Dockerfile	Docker	Medium	2 mins	Solve
Review the following Dockerfiles that work on two projects (project and project2): All Docker files have the same end result: - ‘project’ is cloned from git. After running few commands, ‘project’ code is removed. - ‘project2’ is copied from file system and permissions to the folder is changed. Pick the correct statements: A: File 1 is the most efficient of all. B: File 2 is the most efficient of all. C: File 3 is the most efficient of all. D: File 4 is the most efficient of all. E: Merging multiple RUN commands into a single RUN command is efficient for ‘project’ since each RUN command creates a new layer with changed files and folders. Deleting files with RUN only marks these files as deleted but does not reclaim disk space. F: Copying ‘project2’ files and changing ownership in two separate commands will result in two layers since Docker duplicates all the files twice.

Reason #4

1200+ customers in 75 countries

Com o Adaface, conseguimos otimizar nosso processo de seleção inicial em mais de 75%, liberando um tempo precioso tanto para os gerentes de contratação quanto para nossa equipe de aquisição de talentos!

Brandon Lee, Chefe de Pessoas, Love, Bonito

Preview this test

Ver Scorecard de amostra

Reason #5

Designed for elimination, not selection

The most important thing while implementing the pre-employment Teste do Docker in your hiring process is that it is an elimination tool, not a selection tool. In other words: you want to use the test to eliminate the candidates who do poorly on the test, not to select the candidates who come out at the top. While they are super valuable, pre-employment tests do not paint the entire picture of a candidate’s abilities, knowledge, and motivations. Multiple easy questions are more predictive of a candidate's ability than fewer hard questions. Harder questions are often "trick" based questions, which do not provide any meaningful signal about the candidate's skillset.

Science behind Adaface tests

Reason #6

1 click candidate invites

Email invites: You can send candidates an email invite to the Teste do Docker from your dashboard by entering their email address.

Public link: You can create a public link for each test that you can share with candidates.

API or integrations: You can invite candidates directly from your ATS by using our pre-built integrations with popular ATS systems or building a custom integration with your in-house ATS.

Reason #7

Detailed scorecards & benchmarks

Ver Scorecard de amostra

Preview this test

Ver Scorecard de amostra

Reason #8

High completion rate

Adaface tests are conversational, low-stress, and take just 25-40 mins to complete.

This is why Adaface has the highest test-completion rate (86%), which is more than 2x better than traditional assessments.

Reason #9

Advanced Proctoring

Learn more

Preview this test

Ver Scorecard de amostra

About the Docker Assessment Test

Why you should use Pre-employment Docker Online Test?

The Teste do Docker makes use of scenario-based questions to test for on-the-job skills as opposed to theoretical knowledge, ensuring that candidates who do well on this screening test have the relavant skills. The questions are designed to covered following on-the-job aspects:

Entendendo o básico e os conceitos do Docker
Criando, gerenciando e implantando imagens do Docker
Trabalhando com contêineres do Docker e seu ciclo de vida
Compreendendo a rede do Docker e a comunicação entre recipientes
Gerenciando volumes do docker e dados persistentes
Trabalhando com o Docker compor para definir e gerenciar aplicativos multi-containers
Implantando e gerenciando serviços usando o Docker Swarm
Implementando práticas e políticas de segurança do Docker
Orquestrando recipientes do Docker para implantações em larga escala

Once the test is sent to a candidate, the candidate receives a link in email to take the test. For each candidate, you will receive a detailed report with skills breakdown and benchmarks to shortlist the top candidates from your pool.

What topics are covered in the Docker Online Test?

Docker Swarm
Docker Swarm é uma solução nativa de agrupamento e orquestração para o Docker. O teste dessa habilidade avalia o entendimento do candidato do modo enxame, incluindo a criação e o gerenciamento de clusters de enxames, a implantação de serviços e a dimensionamento de aplicativos em vários nós do Docker para alta disponibilidade. Concentra -se na implementação das melhores práticas e recursos para proteger ambientes do Docker e aplicativos de contêiner. Medir essa habilidade ajuda a avaliar o conhecimento do candidato sobre mecanismos de segurança do docker, como namespaces de usuário, varredura de imagens, isolamento de contêineres, segurança de rede e gerenciamento de vulnerabilidade. Gerenciando e coordenando vários contêineres e serviços do Docker em um ambiente distribuído. Avaliar essa habilidade permite que os recrutadores determinem a familiaridade do candidato com ferramentas de orquestração do Docker como Kubernetes ou enxame de docker, bem como sua capacidade de configurar e monitorar aplicativos de contêiner em escala. A solução de problemas do Docker implica identificar e resolver problemas que possam surgir em ambientes do Docker, como incorretas incorretas do contêiner, problemas de rede ou gargalos de desempenho. Medir essa habilidade ajuda a avaliar a capacidade do candidato de diagnosticar e solucionar problemas em aplicações de contêiner, garantindo operações suaves e confiáveis.
Full list of covered topics
The actual topics of the questions in the final test will depend on your job description and requirements. However, here's a list of topics you can expect the questions for Teste do Docker to be based on.
Instalação do Docker
Arquitetura do Docker
Dockerfile
Camadas de imagem do docker
Ciclo de vida do contêiner do docker
Modos de rede do Docker
Gerenciamento de volume do Docker
Docker compõe a sintaxe YAML
Configuração e configuração do enxame do Docker
Docker Service Scaling
Práticas recomendadas de segurança do Docker
Ferramentas de orquestração do docker
Técnicas de solução de problemas do Docker
Docker CLI Comandos
Docker Registry
Docker Logs de contêiner
Variáveis de ambiente de contêineres do docker
Docker Container Health Checks
Docker Container Resource Management
Docker Container Intercomunication
Docker Image Tagging and Versioning
Técnicas de otimização de imagem do docker
Configurações de rede Docker
Docker Backup de volume e restauração
Variáveis de ambiente de composição do docker
Docker Swarm Service Discovery
Gerenciamento de nó de enxame do Docker
Docker Security Diganning
Padrões de orquestração do docker
Ferramentas de solução de problemas do Docker
Opções de linha de comando do docker
Cache de imagem do docker
Opções de inicialização do contêiner do docker
Isolamento do ambiente de contêineres do docker
Autenticação de registro de imagem do docker
Roteamento de rede do docker
Permissões de volume do Docker
Docker compõe estratégias de implantação
Balanceamento de carga de enxame de enxame do docker
Auditoria de segurança do Docker
Monitoramento de recursos de contêiner do docker
Otimização de camadas de imagem do docker
Docker Network sobreposições
Drivers de volume do docker
Docker compor escala
Atualizações de serviço do Swarm Docker
Políticas de segurança do Docker
Docker Orquestration Rollback
Docker Container Log Management
Docker Recainer Retworking Solução de problemas
Docker Image Vulnerability Scanning
Docker Compõe configuração de rede
Cheques de saúde do enxame do Docker
Docker Security endurecendo
Monitoramento do processo de contêiner do docker
Redução do tamanho da imagem do docker
Configurações de firewall de rede do docker
Estratégias de backup de volume do Docker
Docker Compose Service Discovery
Docker Swarm Service Restries
Conformidade de segurança do Docker
Otimização de desempenho do contêiner do docker
Cache de camada de imagem do docker
Balanceamento de carga de rede do docker
Criptografia de volume do docker
Docker Compose Management de volume
Docker Swarm Secret Management
Vulnerabilidades de segurança do Docker
Docker Container Alta disponibilidade
Estratégias de versão de imagem do Docker
Controle de tráfego de rede do docker
Replicação do volume do docker
Substituição variável do ambiente de composição do docker
Implantação de pilha de enxames do Docker
Ferramentas de auditoria de segurança do Docker
Isolamento do recurso de contêiner do docker
Otimização de armazenamento de imagem do Docker
Resolução DNS da Rede Docker
Gerenciamento de tamanho de volume do Docker
Docker compor escalabilidade de serviço
Configuração de vários gerentes do Docker Swarm
Resposta do Incidente de Segurança do Docker
Docker Recainer Log Rotação
Integração de controle de origem da imagem do docker
Otimização de latência da rede do docker
Ajuste de desempenho de volume do Docker
Docker Compose Gerenciamento de dependência
Docker Swarm Service Rolling Atualizações
Docker Security Compliance Scanning
Docker Container Debug Logging
Suporte de múltiplos arco da imagem do docker
Configuração do gateway de rede do docker
Docker Volume Snapshotting
Docker compor contêiner ligando
Configuração de multi-cluster do Docker Swarm
Controle de acesso à segurança do docker
Agregação de log de contêineres do Docker
Gestão de artefato de imagem do docker

Preview this test

Ver Scorecard de amostra

What roles can I use the Docker Online Test for?

Desenvolvedor do Docker
Engenheiro DevOps
Engenheiro de confiabilidade do local
Engenheiro de Infraestrutura
Especialista em contêiner
Desenvolvedor de back -end

How is the Docker Online Test customized for senior candidates?

For intermediate/ experienced candidates, we customize the assessment questions to include advanced topics and increase the difficulty level of the questions. This might include adding questions on topics like

Projetando e implementando a infraestrutura do Docker
Construindo arquitetura resiliente e escalável do Docker
Implementando orquestração de contêineres com Kubernetes e Docker
Integração do Docker com pipelines CI/CD
Gerenciando o Docker em ambientes em nuvem
Monitoramento e registro de registros de registro e aplicativos
Implementando alta disponibilidade e tolerância a falhas em implantações do Docker
Automatando tarefas do docker usando ferramentas de script e automação
Executando otimização de imagem do docker e redução de tamanho
Configurando e gerenciando redes avançadas do Docker

Preview this test

Ver Scorecard de amostra

Os gerentes de contratação sentiram que, por meio das perguntas técnicas feitas durante as entrevistas do painel, foram capazes de dizer quais candidatos tiveram melhores pontuações e diferenciaram aqueles que não tiveram pontuações tão boas. Eles são altamente satisfeito com a qualidade dos candidatos selecionados na triagem Adaface.

85%

Redução no tempo de triagem

Veja o estudo de caso completo

Docker Hiring Test Perguntas frequentes

Posso combinar várias habilidades em uma avaliação personalizada?

Sim absolutamente. As avaliações personalizadas são configuradas com base na descrição do seu trabalho e incluirão perguntas sobre todas as habilidades obrigatórias que você especificar.

Você tem algum recurso anti-trapaça ou procurador?

Temos os seguintes recursos anti-trapaça:

Perguntas não-goleadas
IP Proctoring
Web Proctoring
Proctoring da webcam
Detecção de plágio
navegador seguro

Leia mais sobre os Recursos de Proctoring.

Como interpreto as pontuações dos testes?

O principal a ter em mente é que uma avaliação é uma ferramenta de eliminação, não uma ferramenta de seleção. Uma avaliação de habilidades é otimizada para ajudá -lo a eliminar os candidatos que não são tecnicamente qualificados para o papel, não é otimizado para ajudá -lo a encontrar o melhor candidato para o papel. Portanto, a maneira ideal de usar uma avaliação é decidir uma pontuação limite (normalmente 55%, ajudamos você a comparar) e convidar todos os candidatos que pontuam acima do limiar para as próximas rodadas da entrevista.

Para que nível de experiência posso usar este teste?

Cada avaliação do Adaface é personalizada para a descrição do seu trabalho/ persona do candidato ideal (nossos especialistas no assunto escolherão as perguntas certas para sua avaliação de nossa biblioteca de mais de 10000 perguntas). Esta avaliação pode ser personalizada para qualquer nível de experiência.

Todo candidato recebe as mesmas perguntas?

Sim, facilita muito a comparação de candidatos. As opções para perguntas do MCQ e a ordem das perguntas são randomizadas. Recursos anti-traking/proctoring no local. Em nosso plano corporativo, também temos a opção de criar várias versões da mesma avaliação com questões de níveis de dificuldade semelhantes.